Revise a change's existing planning artifacts and keep them coherent. Never edit code.

CLI compatibility: On Windows, use openspec.cmd in place of openspec if PowerShell execution policy blocks the .ps1 shim. This fork uses the nearest local openspec/ root; store/registry selection is not supported.

Input: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.

openspec-continue-change is an expanded-profile workflow and may not be installed. Before suggesting it anywhere below, verify that it is available. If it is unavailable, openspec status --change "<name>" --json shows the next artifact and openspec instructions "<artifact-id>" --change "<name>" --json explains how to create it.

Steps

Select the change

If a name is provided, use it. Otherwise:
- Infer from conversation context if the user mentioned a change
- Auto-select if only one active change exists
- If ambiguous, run openspec list --json to get available changes sorted by most recently modified, and ask the user to select one

openspec-update-change