Divide Task

divide-task

Harness conventions: _dev/docs/harness.md. Requires: task spec written, task [WIP], feature branch checked out.

Workflow

1. Derive sub-tasks from the spec. Each sub-task is one implementation step, sized for a single overnight session. Number them N.1, N.2, … where N is the task's TODO number.

1. Analyze each sub-task:

• Autonomy — purely mechanical, mergeable without human judgment → autonomous-ready; otherwise → decision-needed. When in doubt, decision-needed.
• Dependencies — which sub-tasks must land first. Independent sub-tasks that touch disjoint files/logic may run in parallel; note the execution order.

1. Review with the user before creating anything: list sub-tasks, labels, and dependency order. Adjust until approved.

1. Create child issues. For each sub-task:

• Title [N.x] ; body: one-paragraph scope + pointer to the spec path; same milestone as the parent; autonomy label.
• For blocked ones: create blocked-by- labels on demand (gh label create) and apply them. Blockers must be created first so their issue numbers exist.
• Link each as a sub-issue of the parent (GitHub sub-issue, or a task-list in the parent body if unavailable).

1. Mirror into _dev/TODO.md. Under the task line, add an indented checklist: - [ ] **N.x** (#).

1. Update the parent issue. Add the sub-issue links and the spec reference.

Label lifecycle (for whoever completes a sub-task)

When a blocking sub-task closes, remove its blocked-by- label from every issue carrying it, and tick the sub-task checkbox in TODO.md.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: retz8
• Source: retz8/pastiche
• License: MIT

Install and usage instructions live in the source repository linked above.