openspec-continue-change

To continue an OpenSpec change, the workflow reads completed dependencies, applies the active schema, and generates the next artifact in the proposal to tasks sequence. It enforces guardrails to ensure proper sequencing and prevent skipping steps.

The spec-driven artifact sequence follows a staged workflow: proposal, then specs, then design, and finally tasks. The active schema determines which specific artifact to create next based on the current change status.

Spec-driven change management enforces guardrails by checking status and reading dependencies before generating the next artifact. This prevents skipping steps and surfaces missing information so you can make timely decisions.

No, you cannot skip the design phase. Workflow guardrails enforce proper sequencing by checking dependencies and status, preventing step skipping, and surfacing missing information required for timely decisions before moving forward.

Yes, an active schema is required to generate OpenSpec artifacts. The schema determines which artifact to create and when to surface decisions, applying structural rules to the staged proposal through tasks workflow.