split-plan-tasks

# Split plan into tasks Append a task breakdown to a plan so the work lands in small increments — one task, then a review, a correction pass, a commit — instead of one sweep. Authoring only: executing the tasks is a later, separate session. Invocation: `/split-plan-tasks <plan-path>` ## Read the plan Ambiguous or missing path → ask. A plan with numbered steps and an acceptance-criteria checklist splits best; any plan markdown works — reference tasks to headings when steps aren't numbered, and drop the AC line when there is no such checklist. A plan already carrying a task section → **stop and ask** which the user wants: replace it, add a second one beside it, or carry the ticked tasks forward and reformulate only the remaining work. Done when the plan is read and, where a section already existed, the user has chosen. ## Work out the split - **Task** — the smallest chunk that leaves the project building and its tests passing, so it can be reviewed and committed on its own. Steps that only make sense together are one task, never two — building alone isn't the test: a step that only re-runs a generator (API clients, specs, snapshots) lands with the change it regenerates. - **Group** — one PR: independently mergeable, delivering something coherent. Order the groups and state each one's dependency on earlier groups. - Respect the plan's ordering: a task never precedes what it depends on. - **Front-load a hands-on slice.** Among dependency-legal orderings, prefer th...