openspec-continue-change

You can continue an OpenSpec change by selecting the target change through the CLI, which checks artifact status and dependencies before generating the next artifact in the workflow sequence.

The OpenSpec change workflow is a sequential artifact creation process that queries status in JSON format, checks dependencies, and uses template-guided instructions to produce artifacts in strict order.

Yes, OpenSpec checks artifact status and dependencies before creation to prevent out-of-order work, applying guardrails and prompts to stop users from bypassing required workflow steps.

No, you cannot skip artifacts as the workflow applies guardrails and prompts to prevent bypassing steps, ensuring all sequential artifact dependencies are satisfied before creation.

Your OpenSpec workflow likely blocks artifact creation because status checks indicate unresolved dependencies, triggering guardrails that prevent out-of-order progression until prior artifacts are complete.