openspec-continue-change

To continue an OpenSpec change, select the target change and the system automatically generates the next artifact using the CLI. It evaluates status checks and dependencies to determine whether to create a proposal, specs, design, or tasks file next, writing to the specified output path.

OpenSpec artifacts must be created in a specific order: proposal, specs, design, and tasks. The workflow enforces these guardrails by validating prerequisites and reading completed artifacts before allowing the next one to be generated, preserving workflow integrity.

OpenSpec automates change management by using the CLI to apply templates and create the next artifact for a selected change. It excludes context and rules from the content while writing to the specified output path, keeping spec work moving forward.

Yes, the OpenSpec CLI is required to create specs and design artifacts. The automation uses the CLI to apply templates, enforce artifact order, and write the next file to the correct output path based on status checks and dependencies.

Your OpenSpec workflow prevents design artifact generation because it enforces artifact order and validates prerequisites. It checks status and dependencies to ensure prior artifacts like proposals and specs are completed first before proceeding.

No, you cannot skip the proposal step in OpenSpec. The workflow enforces guardrails that require creating artifacts in order, ensuring the proposal is completed before generating specs, design, or tasks files.