Spec-Driven Development
Combine OpenSpec specifications with SDLC execution — from proposals through delta specs to verified, reviewed implementations.
PLAN
REVIEW
Propose & Spec with OpenSpec
Start with /opsx:propose to create a change proposal capturing intent, scope, and capabilities. Then run /opsx:continue to develop delta specs with ADDED/MODIFIED/REMOVED sections, a technical design document, and a high-level task checklist.
These artifacts live in openspec/changes/<name>/ and become the authoritative requirements for SDLC skills. OpenSpec owns the spec workflow — SDLC skills consume the output read-only.
Plan with /plan-sdlc
Run /plan-sdlc --spec to load the OpenSpec artifacts as requirements. The skill reads the proposal for scope, delta specs for detailed requirements, and the design document for architecture constraints. Every ADDED and MODIFIED entry maps to at least one implementation task.
For functional changes, plan-sdlc also detects OpenSpec automatically — even without --spec. If you describe a new feature, it proposes switching to the spec-first workflow before planning begins.
Execute & Verify with /execute-plan-sdlc
Wave-based parallel execution dispatches agents per task. When the plan's Source field points to an OpenSpec change, the spec compliance reviewer checks implementations against the delta spec requirements — not just task acceptance criteria.
After execution, run /review-sdlc with the spec-compliance-review dimension installed to get a multi-dimensional review that includes spec adherence.
Ship & Archive
Package changes with /commit-sdlc (which uses the OpenSpec change name as a scope hint) and /pr-sdlc (which auto-detects OpenSpec and pre-fills Business Context from the proposal). The PR description traces back to the spec.
Close the loop with /opsx:verify to validate implementation completeness and /opsx:archive to merge delta specs into the project's main specifications.