speckit-implement

To execute a spec-kit implementation plan, run the implementation command in your project directory. It validates prerequisites, processes checklists, and executes tasks phase-by-phase from tasks.md while respecting dependency ordering.

Spec-kit extension hooks are optional scripts defined in .specify/extensions.yml. The workflow reads before_implement hooks to run pre-execution logic and after_implement hooks to run post-completion validation.

Yes, spec-kit execution enforces dependency ordering and processes [P] parallel markers. The workflow loads tasks.md and plan.md to execute tasks phase-by-phase while strictly respecting defined dependencies.

Prerequisite validation runs automatically by executing .specify/scripts/powershell/check-prerequisites.ps1. The workflow also scans the checklists/ directory to compute pass/fail status and can halt execution if required items are incomplete.

Yes, you can run spec-kit implementations without optional files. The workflow requires tasks.md and plan.md, but optionally loads data-model.md, contracts/, research.md, and quickstart.md if they exist in the repository.

Your spec-kit implementation stops because checklist-driven gating halts execution when required checklist items fail. The workflow scans checklists/ to compute pass/fail status and prevents task execution until required items pass.