openspec-update-change

Invoke the update workflow with the change name; it reads the change's artifacts via openspec status, applies your requested edit, then checks every other existing artifact for contradictions and proposes confirmed revisions one at a time.

It reads all existing artifacts of the change and cross-checks them in any direction, since an edit to a later artifact may require revising an earlier one. It flags inconsistencies, gaps, and duplication, then proposes fixes only for files that already exist.

Yes. It takes artifact ids and paths directly from the openspec status JSON response rather than hardcoding artifact names, so custom schemas work unchanged. It edits only concrete files in existingOutputPaths, never glob patterns.

No. It only revises artifacts that already exist and never touches implementation code. Missing artifacts are deferred to the continue-change workflow, and code changes implied by a revised plan are deferred to the apply-change workflow.

Start fresh when the request changes the change's intent rather than refining it. The skill checks whether the new-change workflow is available and recommends it, or suggests running openspec new change with a distinct unused name.