speckit-implement

Automate implementation plan execution by parsing tasks.md and plan.md to orchestrate phased project work, running configured pre- and post-implementation hooks while enforcing sequential and parallel task rules. It processes task definitions phase-by-phase with progress and error reporting.

Pre-execution hooks in spec-kit are optional or automatic scripts detected from .specify/extensions.yml. They surface for user review or execute automatically before implementation begins, ensuring custom validation or setup scripts run reliably prior to task orchestration.

Checklist verification gates implementation by scanning project checklists within the .specify directory. It summarizes progress and blocks task execution until the user confirms continuation when checklist items remain incomplete, ensuring required steps are finished.

A .specify directory is required to manage tasks, checklists, scripts, and extension hooks for phased project work. The repository must contain tasks.md and plan.md, while optionally leveraging .specify/scripts and .specify/extensions.yml for full automation.

Task parsing handles dependencies and parallelism by loading tasks.md and plan.md to determine execution phases. It orchestrates tasks phase-by-phase, respecting dependency rules for sequential execution and allowing parallel tasks where specified, with built-in failure handling.

Implementation plans fail when project tooling is missing because this process validates repository setup and generates or updates ignore files based on detected technologies. Ensure tasks.md, plan.md, and the .specify directory structure are correctly configured.