openspec-continue-change

To continue an OpenSpec change workflow, use the skill to automatically generate the next required artifact. It infers the current change status and sequentially creates the corresponding specification, design, or tasks document based on schema definitions.

Spec-driven development artifact generation is the process of sequentially creating workflow documents like proposals, specs, designs, and tasks. It ensures dependency management and adherence to the defined development lifecycle by using existing artifacts as context.

You generate the next specification document by invoking the continue change process on your target change. The skill dynamically creates the spec artifact by using existing proposals as contextual reference and enforcing sequential dependency management.

Yes, the artifact generation process supports automatically inferring the specific change name to work on. If inference is not possible, it will dynamically prompt you to select or enter the change name before generating the next workflow artifact.

Yes, OpenSpec change management enforces sequential artifact creation to maintain workflow integrity. It ensures dependencies are managed correctly by only generating the next required artifact, such as a design document, after the prerequisite specification is complete.

The primary limitation is that artifact generation is strictly sequential and depends on the current change status. You cannot skip ahead to create tasks or designs without first completing the prerequisite proposal and specification documents in the defined workflow.