spec_driven_development.tasks

To break down a software specification into actionable development tasks, provide a validated implementation plan to generate a phased, ordered list of testable tasks with defined dependencies, milestones, and acceptance criteria.

Sequencing task dependencies for feature implementation is handled by translating a validated plan into an ordered task list, specifying target files, dependency chains, parallelization, and milestone checkpoints across infrastructure, backend, frontend, and testing.

You generate a tasks.md file by providing a validated implementation plan and clarifications, which produces a ready-to-run specs/[feature-name]/tasks.md file structured with phased, testable development tasks.

Task breakdown for software engineering supports parallelization and milestones by ensuring every generated task explicitly specifies target files, acceptance criteria, dependencies, and milestone checkpoints across infrastructure, backend, frontend, and testing.

Development task specifications for testable execution should include an ordered list of concrete tasks, target files, acceptance criteria, dependency sequencing, parallelization, and milestone checkpoints to enable structured implementation.

You need to convert an implementation plan into phased development tasks when moving from specification to execution for features requiring structured task breakdown, dependency sequencing, and milestone checkpoints across infrastructure, backend, frontend, and testing.