openspec-continue-change

To continue an OpenSpec change, the Skill assesses the current status and dependencies to automatically generate the next required artifact in the workflow sequence. It reads completed artifacts for context and writes the new artifact to the specified path, then shows unlocked artifacts and progress.

OpenSpec change management automation streamlines progressing a change by generating the next artifact in the workflow. It identifies the active schema, reads completed dependencies to inform the new artifact without duplicating constraints, and clearly communicates current progress after creation.

When multiple OpenSpec changes exist, the automation prompts you to select which specific change to continue. It identifies the most recently modified change as a default option and then determines the required artifact sequence according to the active schema.

Yes, the OpenSpec change manager creates the next artifact according to the active schema by reading completed dependencies for context. It ensures consistent progress and generates the new artifact file without duplicating constraints from previous steps.

After generating the new artifact and writing it to the path specified by the instruction, the system presents the unlocked artifacts and current progress. This ensures consistent workflow advancement and reduces manual context switching for development teams.

No specific dependencies are required to automate OpenSpec change generation. The Skill operates standalone to identify the current status, read completed artifacts, and write the next required artifact file according to the active schema.