speckit-implement

Automate task execution by processing tasks.md and plan.md to orchestrate sequential phases including setup, tests, core, integration, and polish. It enforces dependencies and a TDD-first approach to transform planning into tangible progress.

A spec-kit style workflow uses .specify extensions, checklists, and plan.md/docs to define project tasks. Orchestration parses these files to validate progress, enforce sequential dependencies, and handle post-implementation hooks checks.

Execute tasks defined in tasks.md by parsing the file alongside plan.md and optional data-model/docs. The automation enforces sequential and parallel execution rules across setup, tests, core, integration, and polish phases using a TDD approach.

Yes, task automation enforces a TDD-first approach when executing the implementation plan. It coordinates execution across phases, handles extension hooks checks, and validates progress to ensure tests are prioritized during implementation.

No, this orchestration applies specifically to projects following a spec-kit style workflow with .specify extensions, checklists, and plan.md/docs. It relies on these structures to parse tasks, enforce dependencies, and handle post-implementation hooks.

Handle post-implementation hooks and ignore-file creation through automated orchestration of tasks.md. The workflow validates progress, enforces sequential dependencies, and automatically manages extension hooks checks and ignore-file creation during execution.