openspec-update-change

Invoke the update workflow with the change name, and it reads the change's artifacts via openspec status, applies your requested edit, then checks every other existing artifact for contradictions. Each revision is shown and confirmed before writing.

It reads all existing artifacts of the change and compares them in any direction, since an edit to a later artifact may require revising an earlier one. It notes inconsistencies, gaps, and duplication, then proposes fixes one artifact at a time.

No, it only edits planning artifacts and never touches implementation code. If the revised plan implies code changes, it stops and points you to the apply-change workflow to carry the delta into code.

Yes, it uses the artifact ids and concrete file paths reported by openspec status rather than hardcoded names, so custom schemas work unchanged. It edits only existing output paths and never writes to glob patterns.

It does not create new artifacts or new files under glob artifacts, since that belongs to the continue-change workflow. Missing artifacts are noted and deferred, with a suggestion to run the continue-change command next.

If the request changes the change's intent rather than refining it, starting fresh is recommended. The skill suggests the new-change workflow when available, or asks for a distinct unused name to create a new change via the openspec CLI.