openspec-update-change

Revise existing OpenSpec change planning artifacts and keep them coherent with each other.

747|30|Updated Jul 28, 2020
One-click install
npx skills add https://github.com/godot-go/godot-go --skill openspec-update-change-godot-go
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-update-change
Source: https://github.com/godot-go/godot-go/tree/main/.opencode/skills/openspec-update-change
Command: npx skills add https://github.com/godot-go/godot-go --skill openspec-update-change-godot-go

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a change plan evolves, its proposal, design, specs, and tasks drift out of sync. This Skill revises an existing OpenSpec change's planning artifacts so they stay consistent with one another 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. - Guided Revision: Drafts edits in conversation, confirms each one with the user, then applies revisions one artifact at a time using paths reported by the openspec CLI. - Store and Schema Awareness: Supports registered OpenSpec stores via --store <id> and works with custom schemas by reading artifact ids from openspec status instead of hardcoding names. - Use Case: After deciding the design should use a different approach, ask the assistant to update the change; it revises the design artifact and reconciles the proposal and specs to match. ## Quick Start Ask the assistant to update the OpenSpec change named "add-auth" so its design and specs reflect the new decision.

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 existing OpenSpec change?▼

Provide the change name or let the assistant infer it from context; it runs openspec status to list artifacts, drafts revisions, and applies them after your confirmation. If the name is ambiguous, it prompts with the most recently modified changes.

How to keep OpenSpec planning artifacts consistent after an edit?▼

Request a coherence review: the skill reads all existing artifacts of the change, checks them against each other in any direction for contradictions and gaps, then proposes revisions only to files that already exist.

Does openspec-update-change edit implementation code?▼

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

Can it create missing artifacts or new spec files?▼

No, it never creates artifacts that do not exist yet or new files under glob artifacts. It points you to openspec instructions for the missing artifact id so creation happens in a separate step.

What happens if the project has no openspec root?▼

The skill checks openspec list for a root before writing anything. If none exists and you explicitly requested OpenSpec, it asks whether to run openspec init, target a registered store, or continue without OpenSpec.