speckit-implement

You can automate end-to-end implementation execution by running this tool against your project's tasks.md and plan.md files to orchestrate setup, testing, core development, integration, and polish phases automatically.

Phase-driven execution organizes implementation into ordered stages: setup, test-first development, core development, integration, and polish. This approach enforces dependency handling and validation checkpoints between phases to ensure consistent progress reporting and structural integrity.

Enforce test-first development by configuring the execution to run tests before corresponding implementation tasks. The workflow validates prerequisites, applies TDD-first testing, and reports progress transparently, ensuring tests fail or pass before core logic is written.

Spec-kit style project execution works without a data-models file because data models are optional. The required inputs are tasks.md and plan.md, while the workflow automatically validates prerequisites and extension hook configurations during the setup phase.

You can extend task execution behavior using extension hooks before and after implementation. This allows you to inject custom logic and extend functionality without modifying the core phase-driven workflow or altering the defined tasks.md structure.

Automating implementation with a tasks.md file requires strict adherence to the spec-kit project structure and limits execution to the defined phases. If tasks lack proper dependency definitions or prerequisite validation fails, the execution halts at validation checkpoints until resolved.