speckit-implement

Automating end-to-end software implementation requires executing tasks defined in tasks.md through a phase-driven workflow. The process coordinates Setup, Tests, Core, Integration, and Polish phases with explicit dependency and parallel-task handling, validating each phase before proceeding.

Phase-driven workflow validation enforces task order and supports parallel tasks where specified, checking phase completion before moving forward. It reads tests before implementation steps and records progress, outcomes, and checkpoints to ensure structured software delivery.

Yes, a valid SpeckKit project structure is required to run automated implementation tasks. You must load tasks.md and plan.md, and optionally include data-models or contracts, to enable the system to interpret the plan and orchestrate phase execution.

Yes, you can execute TDD validation automatically by reading tests before implementation steps within a phased workflow. The system enforces this sequence during the Tests phase, ensuring core development follows validated test specifications.

Parallel-task handling allows specified tasks within a phase to execute concurrently while maintaining explicit dependencies. The workflow validates phase completion across all parallel branches before proceeding to the next development stage.

Limitations include strict reliance on a valid SpeckKit project structure with tasks.md and plan.md, and inability to operate outside the defined Setup, Tests, Core, Integration, and Polish phases or handle tasks lacking explicit dependency specifications.