speckit-implement

Automate task plan execution by running a specialized orchestrator that parses tasks.md to extract IDs, dependencies, and parallel markers, then sequentially executes setup, testing, core development, integration, and polishing phases automatically.

Test-first workflow enforcement runs validation tests before corresponding implementation tasks and checks checkpoints before progressing, ensuring code meets defined specifications before moving to subsequent dependent tasks in the plan.

Yes, the orchestrator parses parallel execution markers from tasks.md and executes independent tasks concurrently while strictly enforcing sequential execution for tasks with defined dependencies to maintain correct build order.

Track task progress and visualize execution flow by running the orchestrator, which provides continuous progress updates, manages extension hooks before and after implementation steps, and reports checkpoint validations during the lifecycle.

Yes, you need a predefined task plan described in a tasks.md file within a spec-kit project at the repository root, as the tool parses and validates this metadata to orchestrate the end-to-end execution lifecycle.

Task execution halts because the orchestrator enforces a test-first workflow and validates checkpoints before progressing, stopping the plan if preceding core development tasks fail their associated dependency or test validations.