speckit-implement

To execute implementation plans, you can use a task-driven execution process that reads tasks.md and plan.md files to enforce phase order, dependency rules, and TDD-style execution. This approach converts written checklists into concrete repository changes while verifying prerequisites before making modifications.

Automating task execution in a Spec Kit project involves parsing plan.md and tasks.md to enforce phase order and dependency rules. The process reads .specify directory configurations to handle pre/post extension hooks and automatically updates task completion markers during implementation.

Pre-execution verification checks project prerequisites, repository status, and checklists before making changes. Hook integration detects optional or mandatory pre/post implementation hooks from .specify/extensions.yml, surfacing them for automated execution flows during the task-driven implementation process.

Yes, a .specify directory is required for implementation plan execution. The process applies to Spec Kit projects containing this directory to verify checklists, parse plan.md and tasks.md, handle extension hooks, and perform final validation against the original specification.

Progress tracking during tasks.md execution reports task progress, halts on critical failures, and updates task completion markers. After executing implementation plans, the process performs final validation against the original specification to ensure all checklist items and dependencies are satisfied.

When critical failures occur during task-driven implementation, the execution process halts to prevent further repository changes. This disciplined approach ensures traceability and safety, allowing you to address failures before continuing with the remaining tasks.md execution plan.