openspec-continue-change

To generate the next OpenSpec artifact, run the openspec continue-change command. It inspects the current workflow status, reads dependency artifacts, and writes the next schema-defined artifact, enforcing one artifact per invocation.

OpenSpec workflow automation handles dependency-aware sequencing by inspecting current change status and reading prior artifacts before creating the next one. This ensures artifacts generate in the correct order, respecting dependencies from proposal to tasks.

Yes, you can automate OpenSpec change progression from proposal to tasks by running continue-change. It applies to ongoing changes, handling progression and artifact creation sequentially until the tasks artifact is generated.

Yes, you need the openspec CLI installed to continue creating change artifacts. The skill relies on the CLI to inspect current status, read dependency artifacts, and write the next schema-defined template while enforcing guardrails.

OpenSpec change workflows generate one artifact per invocation to enforce dependency-aware sequencing and guardrails. This prevents skipping required steps, ensuring each artifact properly builds upon the dependency artifacts read during status inspection.

The best way to resume an interrupted OpenSpec change workflow is running openspec continue-change. It inspects current status and generates the next artifact using the schema-defined template, providing structured prompts to guide progression until completion.