openspec-continue-change

To create the next artifact for an OpenSpec change, you select the change, check its status, and generate the next required proposal, spec, design, or task artifact based on CLI-provided instructions and dependency context.

Spec-driven change management is a workflow that progresses software changes by creating sequential artifacts like proposals, specs, designs, and tasks. It uses a CLI to track status and determine which artifact is ready to be created next.

Yes, you need the openspec CLI to generate artifacts. The Skill requires the CLI to list recent changes, retrieve status and artifact instructions, read dependency artifacts, and write the created artifact to the output path.

No, you cannot generate multiple artifacts at once. The workflow applies strict guardrails by creating only one artifact per invocation and never auto-selecting a change, requiring manual selection to continue the workflow.

The workflow determines the next artifact by retrieving and parsing the change status from the CLI. It identifies which artifacts are ready, blocked, or complete, then fetches instructions and reads completed dependency artifacts to generate the next ready file.

Completed dependency artifacts are required because the workflow always reads them to gather context. It uses this context to fill the provided template while respecting rules, ensuring the new artifact builds accurately on prior outputs without copying context into files.