planning-and-task-breakdown

To break down an approved spec into verifiable tasks, you convert it into 2-4 related file batches that are dependency-ordered. This task breakdown process enforces explicit boundaries and generates a tasks/todo.md artifact to track progress.

The best way to plan multi-file implementations is using batch planning to create dependency-ordered work groups with explicit task boundaries. This method establishes clear acceptance criteria and generates checkpointed artifacts for traceability.

Task breakdown reduces scope drift and hidden coupling by splitting an approved spec into small, executable, dependency-ordered batches. Verifying each batch individually prevents fake progress and ensures strict adherence to the original requirements.

Yes, you can easily re-plan tasks when scope changes because the work is structured into explicit boundaries with dependencies. The generated tasks/todo.md artifact supports re-planning by maintaining traceability of the original spec requirements.

You need to generate a tasks/todo.md artifact after spec approval and before implementation in workflows requiring batch planning. It serves as a verifiable, checkpointed task plan that defines boundaries and dependencies for multi-file work.

No, task breakdown requires an approved spec as input to convert it into a structured, verifiable task plan. Applying it before spec approval bypasses the explicit checkpoints and dependency ordering needed to prevent scope drift.