openspec-update-change

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

1|Updated Oct 27, 2025
One-click install
npx skills add https://github.com/WndDnz/modelo-relatorio-unifei-ict --skill openspec-update-change-wnddnz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-update-change
Source: https://github.com/WndDnz/modelo-relatorio-unifei-ict/tree/main/.opencode/skills/openspec-update-change
Command: npx skills add https://github.com/WndDnz/modelo-relatorio-unifei-ict --skill openspec-update-change-wnddnz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a decision changes mid-project, an OpenSpec change's planning artifacts (proposal, design, specs, tasks) drift out of sync with each other. This Skill revises the existing artifacts of a change and reconciles them in every direction so the plan stays internally consistent, without touching implementation code. ## Core Features & Use Cases - Coherence Review: Reads all existing artifacts of a change and checks them against each other for contradictions, gaps, and duplication, even when no specific edit was requested. - Cross-Artifact Reconciliation: Applies a requested revision and propagates its consequences to every other existing artifact, in any direction along the build order. - Confirmed, Scoped Edits: Edits only files reported by openspec status as existing outputs, confirms each revision with the user before writing, and never creates new artifacts or edits code. - Use Case: After deciding to switch the design from REST to gRPC, ask the Skill to update the change; it revises the design document, then adjusts the proposal, specs, and tasks that referenced the old approach. ## Quick Start Ask the assistant to update the OpenSpec change named add-auth so its artifacts reflect the new decision to use token-based sessions.

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 your edit, then reconciles every other artifact against it, confirming each change before writing.

How does the Skill keep OpenSpec artifacts consistent with each other?

It reads all existing artifacts of the change and checks them in any direction, not just build order. An edit to a later artifact like design can trigger revisions to earlier ones like the proposal, and contradictions or gaps are reported and fixed with your approval.

Can it create new artifacts or edit implementation code?

No. It only revises files that already exist according to openspec status. Creating missing artifacts is deferred to the /opsx-continue workflow, and code changes implied by a revised plan are handed off to /opsx-apply.

What happens if I don't specify which change to update?

The Skill infers the change from conversation context or auto-selects when only one active change exists. If ambiguous, it lists the most recently modified changes with their schema, task status, and modification time, and asks you to pick one.

Does it work with custom OpenSpec schemas and stores?

Yes. Artifact ids and paths come from the active schema reported by the CLI, never hardcoded, so custom schemas work unchanged. If the work lives in a registered store, it discovers store ids with openspec store list and passes --store on subsequent commands.