sdd-tasks

Create a tasks checklist by deriving ordered, atomic implementation steps from the accepted plan. The process outputs a tasks.md file that details each step with expected output, verification criteria, touched files, and dependencies, ensuring verifiability and traceability before coding starts.

You need to generate a tasks.md file when a software change requires more than three implementation steps and the plan has been accepted. It serves as a stable contract for implementation, used after planning is accepted and before any code changes begin.

Track dependencies and verification criteria by creating an ordered task list where each atomic task includes specific fields for expected output, verification methods, touched files, and task dependencies, providing a structured contract for multi-step implementation coordination.

Yes, atomic task checklists enable multi-step implementation coordination by clarifying dependencies and verification criteria for each step. The generated tasks.md ensures each small, sequenced task is verifiable, maintaining a stable contract before any code changes occur.

Deriving implementation tasks requires an accepted plan as input and is only applicable when the change needs more than three implementation steps. Without an accepted plan, the task generation process cannot produce the structured tasks.md contract for verifiable implementation.

Generating a verifiable task list requires the docs/sdd/<change-name>/tasks.md format. This documentation structure serves as the implementation contract, containing ordered atomic steps with per-task fields for expected output, verification, touched files, and dependencies.