speckit-implement

To execute a phased implementation plan, the workflow validates prerequisites and checklists, then runs tasks from tasks.md and plan.md sequentially or in parallel while respecting file-level ordering constraints. Progress is tracked and tasks are marked complete as phases advance.

Checklist-driven gating scans markdown checklist files and builds a pass/fail table during spec-to-code conversion. When incomplete items are found, the workflow halts and prompts for user confirmation before continuing task execution.

Yes, you can orchestrate pre and post extension hooks by discovering registered Speckit hooks from extensions.yml. The workflow automatically runs before_implement and after_implement hooks, applying optional versus mandatory behavior rules during execution.

When a non-parallel task fails during plan execution, the workflow enforces operational safety by halting immediately. This prevents dependent tasks from running and ensures file-level coordination constraints are not violated before proceeding.

You need tasks.md and plan.md files to define the phased plan, while the .specify directory contains optional Speckit configuration. Optional context documents and extensions.yml hooks can also be loaded to provide tech and architecture context.

The best way to coordinate parallel and sequential tasks is by defining dependency and ordering rules in plan.md. The workflow reads these constraints and executes phases accordingly, halting on failures for non-parallel work to maintain operational safety.