speckit-implement

To automate tasks.md execution, you need a spec-kit style project with a plan.md and tasks.md. The Skill coordinates and validates all tasks sequentially, marking them complete after successful execution.

Test-driven development execution runs tests before corresponding implementation tasks. This TDD-first coordination ensures correctness by validating tests initially and monitoring completion across Setup, Tests, Core, Integration, and Polish phases.

Phase-driven workflow automation requires structuring work into Setup, Tests, Core, Integration, and Polish phases. You must organize your repository with a tasks.md file and plan.md to enable mandatory sequential steps and parallel task support.

Yes, you can customize automated task execution using extension hooks. The Skill checks and executes pre/post hooks defined in a .specify/extensions.yml file when present, allowing you to inject custom logic into the workflow.

Automated implementation workflows fail when errors occur during task execution or validation. The Skill handles failures by monitoring completion, providing clear guidance for next steps, and ensuring tasks are only marked complete after successful execution.

Yes, a plan.md file is required to run automated spec-kit implementation tasks. You must have a properly organized repository containing both tasks.md and plan.md to execute the end-to-end implementation workflow successfully.