speckit-implement

Spec-driven software development is automated by parsing tasks.md and plan.md files, translating formal specifications into executable tasks, and coordinating phase execution. The orchestration enforces task dependencies while marking parallelizable steps to streamline implementation.

Spec-driven implementation orchestration coordinates end-to-end project execution by translating a formal plan into ordered tasks. It manages setup, tests, core development, integration, and polish phases while enforcing dependencies and reporting progress.

Task dependencies and parallel execution are enforced by parsing formal plan documents to identify sequential and parallelizable steps. The orchestrator coordinates phase execution, ensuring tests precede implementation and dependent tasks execute in correct order.

TDD-driven testing is supported before implementation by orchestrating phase execution from tasks.md. The workflow enforces test phases to run prior to core development, ensuring spec requirements are validated before functional code is written.

Spec-driven project orchestration works without external dependencies, relying solely on parsing tasks.md and plan.md files. It independently loads necessary context, enforces task ordering, and reports progress and errors.

Limitations include reliance on properly structured tasks.md and plan.md files for parsing. The orchestration requires clearly marked parallelizable steps and defined dependencies to function correctly, and errors halt progress if context loading fails.