sdd-tasks

TDD task breakdown converts approved design specs into a hierarchical set of implementable tasks. It produces a structured Tasks document with task groups, estimates, dependencies, and acceptance criteria to guide test-first development.

To generate a task breakdown from a design.md file, invoke the workflow with a feature name. It references design specs located in .spec/specs/{feature}/design.md to determine scope and produces a structured Task.md with hierarchical groups and dependencies.

The best way to plan test-first implementation is using an automated TDD task breakdown. This approach arranges hierarchical tasks according to Red-Green-Refactor cycles, ensuring each task has corresponding tests and clear acceptance criteria.

Yes, you need an approved design before generating TDD task breakdowns. The workflow specifically breaks down approved designs located in .spec/specs/{feature}/design.md into actionable, test-first tasks for consistent implementation planning.

Yes, task breakdown for SDD workflows provides estimates and dependencies. The generated Task.md includes hierarchical task groups, time estimates, and dependencies mapped directly from the approved design specifications for accurate implementation planning.