openspec-continue-change

Spec-driven development artifact generation is automated by creating the next logical file, such as proposals, specifications, designs, or tasks, based on the current status of your OpenSpec change. The workflow checks existing context to infer the required output.

The OpenSpec change workflow process moves a feature proposal to implementation tasks by sequentially generating specifications, design documents, and task files. It tracks artifact status to ensure each phase is completed before generating the next required document.

Yes, you need the OpenSpec CLI to manage change status and artifact instructions. The CLI is required for checking artifact status, listing active changes, and retrieving the specific instructions needed to generate the next artifact in the schema-driven workflow.

Yes, you can use conversation context to select which OpenSpec change to continue. The workflow infers the active change from your current conversation context, and if the target change is ambiguous, it prompts you to select the correct one.

Limitations of automating change management artifact creation include its strict dependency on the OpenSpec CLI for status checks and its inability to operate outside the defined schema-driven workflow. It requires existing changes and cannot generate artifacts without contextual status data.