openspec-continue-change

To generate the next artifact for an OpenSpec change workflow, you need a Skill that checks artifact status and automatically creates the next required file like a proposal, spec, design, or tasks.

OpenSpec artifact generation creates required workflow files for spec-driven schemas, ensuring structured project progress by systematically producing proposals, specifications, designs, and tasks.

Yes, you need the OpenSpec CLI to manage and track artifact status, as the workflow requires CLI commands for checking current progress and retrieving instructions for the next artifact.

To create a specification from a proposal in a spec-driven workflow, use a status-tracking Skill that identifies the proposal as complete and automatically generates the corresponding specification file.

A key limitation of automating artifact generation for OpenSpec changes is its strict dependency on the OpenSpec CLI for status checks, meaning the workflow cannot function without the CLI environment properly configured.

You can use scripts to continue an OpenSpec change workflow across platforms as long as the environment supports the required OpenSpec CLI for executing status checks and retrieving generation instructions.