openspec-update-change

Revises existing OpenSpec change planning artifacts and keeps them mutually coherent.

4|Updated May 13, 2026
One-click install
npx skills add https://github.com/RuixeWolf/modbus-simulator --skill openspec-update-change-ruixewolf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-update-change
Source: https://github.com/RuixeWolf/modbus-simulator/tree/main/.opencode/skills/openspec-update-change
Command: npx skills add https://github.com/RuixeWolf/modbus-simulator --skill openspec-update-change-ruixewolf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a spec-driven change plan evolves, its proposal, design, specs, and task files drift out of sync. This Skill revises an existing OpenSpec change's planning artifacts so they stay consistent with each other after new decisions or edits, without touching implementation code. ## Core Features & Use Cases - Coherence Review: Reads all existing artifacts of a change and detects contradictions, gaps, and duplication across them in any direction. - Guided Revision: Proposes edits one artifact at a time, confirms with the user before writing, and only modifies files that already exist on disk. - Schema-Agnostic Operation: Uses artifact ids and paths reported by the openspec CLI rather than hardcoded names, so custom schemas work unchanged. - Use Case: After deciding the design should use a different data store, ask the Skill to update the change; it revises the design artifact and reconciles the proposal, specs, and tasks to match. ## Quick Start Ask the assistant to update the OpenSpec change named "add-auth" so its design reflects the new caching decision and keep the other artifacts consistent.

Frequently Asked Questions about openspec-update-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update an OpenSpec change after a design decision changes?▼

Invoke the update workflow with the change name and describe the revision. The Skill reads the change's existing artifacts via openspec status, applies the edit, then reconciles every other artifact against it, confirming each change before writing.

How to keep OpenSpec planning artifacts consistent with each other?▼

Run a coherence review by asking to update the change without a specific edit. The Skill reads all existing artifacts, checks them for contradictions, gaps, and duplication in any direction, and proposes targeted revisions.

Does openspec-update-change edit implementation code?▼

No, it only edits planning artifacts such as proposals, designs, specs, and task files. If a revised plan implies code changes, it stops and points you to the apply workflow instead.

Can it create new artifacts or files for a change?▼

No, it only revises files that already exist in the change's existingOutputPaths. Creating missing artifacts or new files under glob artifacts is deferred to the continue workflow.

What happens if the change name is ambiguous or missing?▼

The Skill infers the change from conversation context or auto-selects when only one active change exists. Otherwise it lists the most recently modified changes with status and asks you to pick one.