task-breakdown

Task Breakdown

When to Use

• Stage 5 of the full-stack workflow: after program design is complete and before unit testing.
• When the user requests splitting the design into a manageable development rhythm.

Input

Read from the current iteration directory:

• Requirements document (requirements-{id}.md）
• Technical review document (technical-review-{id}.md）
• Program design document (program-design-{id}.md）

Execution Points

1. Breakdown granularity: Each task should be completable within 1–4 hours, including clear inputs and outputs.
2. Dependency ordering: Mark dependencies between tasks and generate an execution order (mark parallelizable ones as parallel).
3. Priority: P0 (core flow), P1 (important features), P2 (enhancement/optimization).
4. Acceptance criteria: Each task includes brief acceptance conditions (corresponding to subsequent unit tests).
5. Batching suggestions: Organize by development batch (Sprint/Batch), with 3–7 tasks recommended per batch.

Output

• Use templates/task-breakdown-template.md to produce the task breakdown document, for "Unit Testing" and "Code Development" to execute in order.

Document and Status

• Output is written to docs/{current_iteration_id}/task-breakdown-{task_breakdown_id}.md。
• Before starting: call the history-manager skill's get-phase task_breakdown and check-file to confirm whether it has been completed.
• After completion: call the history-manager skill's set-phase task_breakdown {task_breakdown_id} to record and advance the status.