Nested Subtask Lifecycle

Use this optional skill when a TODO is strongly related to its parent but is independently lifecycle-deliverable and does not fully overlap existing work.

Create

Create a real, first-class child with the task-framework manager:

python3 skills/task-framework/scripts/manage_task.py create <name> \
  --parent <parent-hash-or-directory> --desc "Bounded child goal"

The child is created only under <parent>/subtasks/ and receives its own TASK.md, MEMORY.md, CHANGELOG.md, metadata, input, and output. Children cannot create further children. Never hand-edit metadata or move child dirs.

A child may nest its own runtime/ execution-state directory (formats owned by compact-directory-memory). The child's runtime/INDEX.md is independent: the parent's INDEX records the child only at subtask granularity — one row for the child itself, never the child's internal runtime items.

Route and verify

Record the child path or hash in the parent's TODO outcome and mark that TODO routed with scope nested. The parent remains incomplete until its TODO is routed and the child follows its own checklist lifecycle. reindex and the stable task API expose parent/child relationships; root indexes list children under their parent, not as independent root rows.

A child is valid only when its real path is contained by the exact parent's subtasks/ directory. Symlinks and paths outside that directory are rejected. Reset clears only the selected child's generated output and preserves input.