speckit-implement

To implement features from a task breakdown using test-driven development, execute tasks systematically through Setup, Tests, Core, Integration, and Polish phases. This enforces dependency-aware sequencing and automated test-first development to build the complete feature.

Automating task breakdown execution requires a phase-driven workflow that validates progress before advancing phases. Applying dependency-aware sequencing and parallelism where allowed ensures tasks transform into concrete code and tests efficiently.

Enforcing phase-driven execution involves applying progress validation and guardrails to ensure tasks are completed before advancing. This structured workflow covers Setup, Tests, Core, Integration, and Polish phases to build features reliably.

Yes, you can customize the implementation process using extension hooks. By configuring .specify/extensions.yml, you can define optional and mandatory pre/post hooks to tailor the feature execution workflow across its phases.

You need phase-driven workflows for task breakdowns when transforming plans into concrete code and tests requires strict dependency-aware sequencing. This approach prevents advancing phases prematurely by enforcing progress validation guardrails.

Test-first development matters in phased feature implementation because it provides automated validation guardrails. It ensures core, integration, and setup tasks are properly tested before advancing through the workflow phases.