speckit-implement

To automate spec-kit project implementation, you need a tasks.md file and plan.md to guide the AI through phased execution across setup, tests, core development, integration, and polish, applying validation checkpoints to produce completed repository changes.

Task-driven implementation works by reading an ordered task list and executing work in phases. Validation checkpoints verify prerequisites, checklist status, and supporting project files before making changes to ensure deterministic and accurate repository updates.

Before starting phased execution, you need a tasks.md file, a plan.md file, validation checkpoints, and ignore-file verification. These files support task marking and ensure the implementation plan is followed systematically.

Yes, task marking tracks progress across setup, tests, core development, integration, and polish phases. It updates completed tasks in the tasks.md file to keep repository changes aligned with the established implementation plan.

Ignore-file verification is required to prevent unintended repository changes. It checks supporting project files and prerequisites before executing tasks, ensuring the implementation workflow respects existing configurations and maintains deterministic execution.

The best way to execute a written implementation plan is through task-driven delivery that processes an ordered task list. It handles setup, testing, core development, integration, and polish while applying validation checkpoints to produce completed repository work.