openspec-continue-change

To resume OpenSpec work, provide a change name to automatically determine the current state, apply status checks, and generate the next required artifact using a template-driven structure to guarantee correct sequencing.

Advancing an OpenSpec change involves executing a controlled workflow that enforces status checks, reads dependency artifacts to inform the next step, and writes the output to a specified path using a template-driven structure to maintain correct artifact sequencing.

Creating the next artifact requires reading completed dependencies to understand the current context, then generating the subsequent proposal, specs, design, or tasks file via a template-driven structure to ensure proper spec-driven progression.

Yes, if a change name is omitted, the workflow will prompt you to select a recent change and automatically create the next artifact, applying guardrails and status checks to keep work moving when context is incomplete.

Yes, the workflow enforces status checks and dependency reads before generating the next artifact, ensuring that completed dependencies inform the output and maintaining correct artifact sequencing across the spec-driven process.

When multiple changes exist, the workflow provides guardrails by prompting you to select a specific recent change, ensuring the next artifact is generated for the correct context and preventing incorrect sequencing.