speckit-implement

To execute a spec-kit implementation plan, validate prerequisites using check-prerequisites.ps1, enforce checklist completion, and process tasks phase-by-phase from tasks.md while respecting dependency rules. The workflow tracks progress by marking completed tasks directly in tasks.md.

Checklist gating validates that all items under FEATURE_DIR/checklists/ are completed before task execution begins. If incomplete checklists are detected, the implementation process stops to confirm whether you want to proceed with executing the repository plan.

Phase-ordered task execution reads tasks.md and plan.md to understand the architecture, then executes tasks sequentially or in parallel based on defined dependency rules. It validates completion against the spec before finishing the implementation.

Yes, you can execute optional before_implement and after_implement extension hooks defined in .specify/extensions.yml. These hooks run automatically during the implementation workflow when the extensions file is present in the repository.

Yes, plan.md and tasks.md are required files for repository validation and plan-driven execution. Optional files include data-model.md, contracts/, research.md, governance constitution, and quickstart.md to provide additional architecture context.

Your implementation workflow stops because the checklist gatekeeping mechanism detected incomplete checklists under FEATURE_DIR/checklists/. This validation ensures safe coordination by confirming your intent to proceed before executing the plan.