sdd-orchestration

Spec-driven development orchestration coordinates the entire feature lifecycle from initial idea through review, delegating interactive and autonomous phases to specialized sub-skills to ensure coherent progression and artifact tracking.

You manage phase progression in spec-driven development by following a defined sequence: constitution, specification, clarification, planning, analysis, implementation, and review, letting specialized sub-skills execute each step.

Yes, you can resume an automated feature delivery workflow because the orchestrator maintains state tracking and auditability through shared artifacts like working-spec.json and phase_history, enabling reproducible workflows.

Spec-driven development requires separate sub-skills for each lifecycle phase, applying phase-aware delegation to named components like sdd-constitution, sdd-specification, sdd-clarify, sdd-planning, and sdd-analysis with explicit loading guidance.

The best way to track artifacts during spec-driven feature development is using shared .specify artifacts like working-spec.json, which provide state tracking and auditability across interactive and autonomous workflow phases.

You should not use an SDD orchestration workflow for feature development tasks that lack coherent phase progression requirements or do not need explicit artifact tracking, state management, and cross-phase delegation.