openspec-continue-change

To progress an OpenSpec change to the next artifact, you can use a guided workflow that interacts with the OpenSpec CLI to check status and automatically generate the required artifact in the correct sequence. This automates continuation without manual context switching.

Generating OpenSpec artifacts follows a strict sequence to ensure tasks are created in order and dependencies are respected. The process uses guided prompts to identify the required artifact and instructs the CLI to generate it, maintaining workflow alignment.

Yes, the OpenSpec CLI is required to automate your change workflow. The automation process relies on CLI commands to list changes, check current status, and generate the next artifact in the development sequence.

You can check the status of an OpenSpec change by using the OpenSpec CLI. The workflow integrates these status checks to accurately determine which artifact needs to be generated next in the sequence.

Your OpenSpec change workflow requires a strict artifact sequence to ensure tasks are created in order and dependencies are respected. This prevents coordination issues and keeps the development workflow properly aligned.