openspec-continue-change

To continue an OpenSpec workflow, this Skill programmatically identifies the current change status and generates the next required artifact, such as a proposal, spec, design, or task list. It leverages schema-driven processes to ensure sequential progress.

Automatically creating specification files from an OpenSpec proposal is handled by checking the change status via the OpenSpec CLI. The Skill then retrieves artifact instructions to generate the corresponding specification based on your defined capabilities.

Yes, the OpenSpec CLI is required to manage artifact generation. The Skill depends on the CLI to perform status checks and retrieve the necessary artifact instructions for your current development changes.

Yes, you can use conversation history to specify the OpenSpec change. The Skill features contextual awareness that automatically infers the specific change to work on, or it will prompt you based on the `openspec list` output.

When advancing your spec management workflow, you can generate progressive artifacts including proposals, specifications, designs, and task lists. The Skill guides you through creating the exact next artifact required by the schema-driven process.

An OpenSpec change workflow stops progressing if the next sequential artifact is missing. This Skill resolves the stall by querying the current status and programmatically creating the next required specification, design, or task list.