speckit-implement

You can automate software implementation by running a skill that interprets tasks.md and plan.md to orchestrate setup, tests, core development, integration, and polish phases sequentially or in parallel. It validates progress at checkpoints and automatically updates the tasks file upon completion.

TDD-inspired workflow automation enforces a test-driven validation process during structured phase execution. It interprets your formal task list to manage dependencies, execute tasks, and validate progress at checkpoints before recording completion in the original tasks file.

Yes, automated implementation planning supports dependency management alongside both sequential and parallel task execution. It orchestrates the entire workflow from setup to polish by reading your plan.md and tasks.md, ensuring structured phase execution and automated progress tracking.

Project-wide progress tracking is handled by automatically marking tasks as complete in your tasks.md file. The automation validates progress at defined checkpoints throughout the implementation phases and records completion directly in the task list.

Yes, you need a tasks.md and a plan.md file in your current project directory. The automation reads these formal documents to orchestrate the end-to-end implementation workflow, including setup, tests, core development, integration, and polish phases.

Yes, the automated implementation workflow supports extension hooks to customize steps. This allows you to adapt the orchestrated setup, tests, core development, integration, and polish phases while maintaining the structured TDD-driven validation process.