openspec-continue-change

To create an OpenSpec change artifact, you use the openspec CLI to select a specific change, fetch its current status, read completed dependencies, and write a single output file following the enforced schema rules and templates.

The OpenSpec workflow selects the first ready artifact by inspecting the change status via the openspec CLI, ensuring dependency artifacts are completed and unlocking rules are validated before generating the next required document.

No, you cannot generate multiple spec documents at once. The workflow enforces a strict guardrail of creating exactly one artifact per invocation to maintain consistency and validate artifact ordering.

Yes, the openspec CLI is required to generate proposal and design documents. It is used to list changes, fetch status and instructions, read dependencies, and enforce schema rules when writing the output file.

If you do not specify a change name, the workflow will prompt you to choose one and will automatically recommend the most recently modified change to help you continue progressing without delay.

A key limitation is that automation creates only one artifact per invocation and strictly enforces artifact unlocking and ordering rules, meaning you cannot skip steps or bypass dependency validation when generating specs.