openspec-continue-change

To generate the next artifact for an OpenSpec change, you continue the workflow by checking the current status and creating the required proposal, specification, design, or tasks file based on that status.

The OpenSpec development workflow progresses changes through a defined lifecycle, generating structured artifacts sequentially from initial proposals to detailed specifications, designs, and tasks.

You create specifications from an OpenSpec proposal by continuing the active change, which evaluates the current workflow status and automatically generates the corresponding specification file as the next required step.

Yes, you need the OpenSpec CLI installed to generate design and task artifacts, because the CLI is required to perform status checks and retrieve artifact instructions for the workflow.

Yes, you can use OpenSpec to manage task generation for software development by progressing a change through its schema-driven lifecycle to automatically produce the required task artifacts.

An OpenSpec change workflow stops progressing if the current status does not map to a recognized schema for proposals, specifications, designs, or tasks, preventing the next artifact from being generated.