speckit-implement

You can automate task execution by running speckit-implement to process sequential and parallel tasks defined in your tasks.md and plan.md files. The Skill reads these files to drive end-to-end implementation automatically.

A tests-first workflow enforces running tests before implementation begins. speckit-implement uses this approach to validate phase boundaries and ensure setup steps are completed before moving to core development tasks.

Yes, speckit-implement supports dependency-aware execution with explicit parallelism markers and sequential constraints. It reads task relationships from tasks.md and plan.md to orchestrate both parallel and sequential steps.

Yes, you need both plan.md and tasks.md files. speckit-implement reads data from these files to drive execution, using plan.md for phase boundaries and tasks.md for the actual task definitions and dependency relationships.

Execution tracking reports progress with explicit failure handling. speckit-implement validates completion against the plan and halts or reports when tasks fail, ensuring consistent delivery across complex projects.

The best way to enforce phase boundaries is using speckit-implement, which orchestrates setup, tests-first workflow, core development, integration, and polish phases based on your plan.md, preventing out-of-order execution.