spec-driven-coding

Use when a development request must be routed through the SDC lifecycle.

Use when a project needs an SDC workspace, project cognition, or standards import.

Use when an approved SDC plan is ready for implementation and evidence capture.

Use when a completed SDC change is ready for archival and durable knowledge compaction.

Use when starting or clarifying a focused requirement change under SDC governance.

Use when an SDC change needs validation, review, testing, quality, impact, or repository checks.

Use when project-level AI guardrails must be generated from SDC standards.

Use when a confirmed SDC change needs detailed implementation control beyond the normal apply workflow.

Use when a confirmed SDC change needs an executable design, task plan, and context handoff.

Use when an SDC change needs its final cross-cutting delivery quality gate.

Use when implemented code or a complete SDC change needs an independent engineering review.

Use when requirements must be refined into a structured SDC specification after discovery.

Use when an SDC change needs test execution, failure analysis, or acceptance-coverage assessment.

Use when current or active SDC artifacts need structural and traceability validation.