speckit-implement

You can automate multi-phase implementation plans by running a parser against your tasks.md file to coordinate setup, tests, core development, integration, and polish steps sequentially. This enforces phase order, dependencies, and test-first rules while reporting progress.

Test-first execution is an enforced rule that validates tests before proceeding to core development tasks. The automation parses tasks.md, runs setup and tests initially, and halts on critical failures to ensure validation checkpoints are met before integration.

Yes, this automation applies to projects adopting a speckit-like structure with .specify directories. It parses tasks within these directories and coordinates sequential or parallel task execution based on your defined implementation plan.

Handling critical failures during task execution involves automated halting. The automation stops the end-to-end implementation process immediately upon detecting a critical failure, preventing downstream integration or polish steps from running until resolved.

Yes, you can run extension hook checks after implementation. The automation includes post-implementation checks that evaluate extension hooks and report progress once setup, tests, core development, integration, and polish phases finish.

The best way to enforce dependencies across parallel task execution is using an automated coordinator. It parses tasks.md, validates phase order, and ensures that validation checkpoints and extension hooks are respected before allowing dependent sequential tasks to proceed.