speckit-implement

Automate implementation plans by reading tasks.md to orchestrate stepwise phase execution. The system processes task-based plans sequentially or in parallel, respecting dependencies and phase separation to execute development tasks automatically.

Test-driven workflow automation handles phase dependencies by orchestrating task execution from tasks.md, respecting dependency order and phase separation. It enforces tests-before-code rules and supports pre- and post-execution extension hooks during sequential or parallel task processing.

Task-based planning suits complex multi-phase software projects by orchestrating execution across phase setup, testing, core development, integration, and polish. It requires a repository containing tasks.md and plan.md to begin orchestrating the automated implementation flow.

Execute implementation tasks sequentially or in parallel by orchestrating phase execution defined in tasks.md. The automation respects dependency order, applies tests-before-code workflows, and provides real-time progress reporting for each task within the plan.

Yes, you need a tasks.md file and a plan.md file in your repository to start automating implementation workflows. The automation reads these files to orchestrate stepwise execution, applying phase separation and dependency rules throughout the development lifecycle.

Automated phase execution stalls when dependencies in tasks.md are not satisfied or when preceding tests fail. The system strictly adheres to the plan's dependency order and tests-before-code rules, blocking progression until earlier phase tasks are completed successfully.