speckit-implement

Executing a spec-kit implementation plan requires reading the task list, validating repository prerequisites like ignore files and checklists, and applying repository changes in correct phase order. This Skill follows dependencies and file-level constraints to reduce drift from the original specification.

Task-driven implementation follows planned phases, dependencies, and file-level constraints from a spec-kit breakdown to reduce drift. It requires executing tasks in order, verifying governance documents, and safely handling hooks and validation steps throughout the project workflow.

Yes, task execution depends on a spec-kit repository structure containing .specify task breakdowns, checklist gates, and governance documents. The Skill verifies these prerequisites, ignore files, and supporting documents before applying any repository changes during implementation.

Prerequisite validation checks repo setup, ignore files, checklists, and supporting spec-kit documents before implementation. The Skill verifies these governance documents and repository constraints to ensure safe handling of dependencies and hooks before applying changes in phase order.

When validation steps or checklist gates fail during task execution, the Skill stops safely and reports the blocker status. It marks completed tasks, pausing progress-aware execution to ensure no repository changes skip required checks or violate governance documents.

Yes, progress-aware execution marks completed tasks in tasks.md and reports status as implementation proceeds. The Skill tracks task execution discipline by updating the task list, allowing team members to monitor which spec-kit phases and validation steps are finished.