speckit-implement

Automating feature implementation from a task breakdown plan requires orchestrating phase-based execution across setup, testing, core development, integration, and polishing steps. This skill interprets structured tasks.md files and coordinates sequential and parallel task dependencies end-to-end.

Test-driven development workflow orchestration for structured project plans coordinates task execution while enforcing a test-first approach. It parses task dependencies from plan files, ensures tests precede core implementation, and validates progress with clear error reporting.

You need a structured Speckit project containing a tasks.md file, plan.md, contracts, and data directories to run task-driven implementation pipelines. These inputs provide the task breakdown and dependency information required for phase-based orchestration.

You can execute tasks in parallel when implementing features from a plan, as the orchestration pipeline respects both sequential and parallel task dependencies defined in the task breakdown. It coordinates setup, tests, core development, and integration phases accordingly.

The best way to enforce TDD compliance during automated feature implementation is using an orchestration pipeline that applies a test-first workflow across all phases. This ensures tests precede implementation, validates progress, and reports errors clearly.

Task breakdown implementation fails when dependencies are not parsed correctly because the orchestrator cannot determine proper sequential or parallel execution order. This disrupts the test-first workflow and prevents valid phase progression from setup through integration and polishing.