speckit-implement

Automating spec-driven implementation requires loading tasks.md and plan.md to parse task phases and dependencies, executing tasks in sequence while honoring parallel markers, and validating completion. This approach ensures deterministic task orchestration with clear progress tracking.

Yes, checklist status validation scans checklists to ensure required work is complete and actively blocks progress when incomplete. Pre-implementation safety checks also run prerequisite validations and optionally execute extension hooks before implementation begins.

The spec-kit structure requires tasks.md and plan.md files for core execution, plus optional data-model, contracts, and research files. Optional checklists and extension hooks can be included to add prerequisite validation and post-implementation automation.

Executing tasks in correct phase and dependency order involves parsing plan.md to map task dependencies and phases, then executing tasks in sequence while honoring parallel markers. This plan-driven execution orchestration ensures deterministic task completion and verification.

Extension hooks are needed when you require custom pre-implementation safety checks or post-implementation completion validation. The system optionally executes registered before-implement hooks before starting and after-implement hooks after completion validation.

Spec-kit implementation is limited to repositories strictly following its structure with tasks.md and plan.md. It cannot orchestrate tasks if prerequisite checklists remain incomplete, and relies on deterministic phase order rather than dynamic task generation.