openspec-continue-change

Creating the next OpenSpec change artifact is automated by querying the openspec CLI for status, reading dependencies, and generating exactly one artifact according to schema rules. It then reports updated progress and unlocked artifacts.

Continuing an OpenSpec change workflow involves selecting the correct change interactively if context is ambiguous, retrieving artifact instructions, and creating the next spec, design, or task artifact. This advances the proposal-driven change without manual orchestration.

Yes, interactive change selection is supported. When an OpenSpec change name is ambiguous or unspecified, the workflow lists recent changes and prompts the user to choose the correct one before generating the next artifact.

Generating OpenSpec artifacts requires access to the openspec CLI, repository file read and write permissions, and JSON parsing capabilities for CLI outputs. These prerequisites ensure the workflow can inspect status and update progress correctly.

Automating OpenSpec artifact creation is limited to generating exactly one artifact per run according to schema and dependency constraints. It cannot bypass dependency rules or create multiple artifacts simultaneously, ensuring strict workflow integrity.