moonspec-orchestrate

To automate an end-to-end TDD workflow, you coordinate downstream skills to produce a cohesive spec lifecycle from a feature request. This enforces one-story-per-spec discipline and generates TDD tasks through validated artifact gates for final verification.

A spec lifecycle orchestration pipeline coordinates downstream phases including specify, breakdown, plan, tasks, align, implement, and verify. It ensures artifacts flow through gates like spec.md and plan.md to maintain coherence across the workflow.

Yes, you can resume a stalled workflow pipeline from existing spec, plan, or task artifacts. The orchestration validates current artifact gates before progression, ensuring resumable state without losing previous design progress.

To enforce artifact alignment across workflow stages, apply policy-driven orchestration that validates gates between spec.md, plan.md, and tasks.md. This maintains coherence by using conservative edits and checking alignment before implementation.

The best way to coordinate TDD task generation from declarative designs is to use an orchestration layer that enforces TDD as a default. It routes designs through planning and breakdown gates to generate aligned tasks before implementation begins.

You should avoid policy-driven orchestration pipelines for feature requests that do not require strict one-story-per-spec discipline or TDD. If your project lacks formal artifact gates, this orchestration overhead will impede rapid development.