openspec-continue-change

Automate OpenSpec change progression by using a status-aware workflow that generates the next templated artifact in the lifecycle. It inspects open changes, prompts for selection, and outputs the artifact file while validating progress with the openspec CLI.

Artifact generation in a multi-step OpenSpec workflow works by inspecting the current state and creating the next dependent artifact. It ensures artifacts are created in the correct order and validates progress with the openspec CLI throughout the process.

Yes, you can use the openspec CLI to validate progress when advancing a change. The workflow integrates directly with the CLI to read the current state, generate templated artifact files, and validate the output throughout the progression.

Yes, you need an existing OpenSpec project with a multi-artifact lifecycle. The process is designed for workflows where each step depends on the previous one, requiring user input to guide naming and scope before generating the next artifact.

The best way to handle dependencies when creating OpenSpec artifacts is to follow status-aware guidance. The workflow ensures artifacts are created in the correct order and outputs specific guidance for dependency handling during the automated progression.

OpenSpec changes may not advance correctly if artifacts are not created in the proper sequence. The workflow inspects open changes and validates progress with the openspec CLI to ensure the next artifact is generated in the correct order.