speckit-implement

Automating task execution from a markdown plan involves reading a tasks.md file and running each defined task sequentially or in parallel. This skill processes the plan, enforces dependency ordering, and updates the file with completed progress for repeatable workflows.

Yes, you can enforce a test-first development approach during pipeline orchestration. The execution flow verifies contracts and runs tests before writing core code, ensuring validation checkpoints are met before implementation phases proceed.

Yes, this automation tool supports both parallel task execution and dependency management. It orchestrates setup, tests, core development, integration, and polish phases while strictly adhering to dependency ordering defined in the task plan.

Before running automated implementation plans, you need an existing repository containing a detailed tasks.md file structured as a Speckit plan. No external dependencies are required, but the task plan must define phases, tasks, and validation checkpoints.

To track progress when executing a multi-phase development plan, the automation reads the tasks.md file, executes tasks in defined order, and automatically updates the file with completed items. This provides repeatable and auditable progress tracking throughout the workflow.

Yes, you can add custom hooks after completing an orchestrated task pipeline. The execution workflow supports optional extension hooks after completion, allowing you to tailor the post-execution workflow to specific project requirements.