openspec-continue-change

To generate the next artifact for an OpenSpec change workflow, the skill checks the current status via the CLI and creates the next required file, such as a proposal, spec, design, or task, based on defined schema instructions.

The OpenSpec change workflow process involves creating artifacts sequentially. The skill checks the current change status, determines the next required artifact in the dependency chain, and generates exactly one artifact per invocation.

You can check which OpenSpec artifact to create next by running the status check command. The skill uses the CLI to list available changes, evaluate the current progress, and determine the next required file in the sequence.

No, you cannot generate multiple OpenSpec artifacts at once. The skill strictly follows artifact sequences and dependency requirements, ensuring exactly one artifact is created per invocation to maintain workflow integrity.

To start generating OpenSpec specifications and proposals, you need the OpenSpec CLI installed and an existing change workflow. If a change name is not provided, the skill prompts you to select from available changes.

An OpenSpec workflow may fail to create the next design or task file if dependency requirements are not met. The skill strictly follows artifact sequences, requiring the previous artifact to exist before generating the next one.