openspec-update-change

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

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/pvtvv/climber-app --skill openspec-update-change-pvtvv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-update-change
Source: https://github.com/pvtvv/climber-app/tree/main/.cursor/skills/openspec-update-change
Command: npx skills add https://github.com/pvtvv/climber-app --skill openspec-update-change-pvtvv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a spec-driven change plan evolves, its proposal, design, specs, and task artifacts drift out of sync. This Skill revises an existing OpenSpec change's planning artifacts and reconciles them against each other, without touching implementation code. ## Core Features & Use Cases - Change Selection: Infers the target change from context or lists the most recently modified changes via openspec list --json when ambiguous. - Coherence Review: Reads all existing artifacts reported by openspec status and detects contradictions, gaps, and duplication in any direction across the build order. - Confirmed Edits Only: Proposes each revision, waits for user confirmation, and edits only files in existingOutputPaths — never creating new artifacts or writing to glob patterns. - Use Case: After deciding the design now uses a different storage approach, ask the assistant to update the change; it revises the design doc, reconciles the proposal and specs, and points you to /opsx-apply for the code delta. ## Quick Start Ask the assistant to update the OpenSpec change named "add-auth" so its design and specs 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 existing OpenSpec change plan?▼

Invoke this Skill with the change name, or let it infer the change from context. It runs openspec status to list existing artifacts, reads them, proposes revisions, and writes each edit only after you confirm.

How to keep OpenSpec artifacts consistent after a design decision changes?▼

The Skill performs a coherence review: it reads all existing artifacts of the change, checks them against each other in any direction for contradictions or gaps, and revises only the files that already exist on disk.

Does this Skill 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 /opsx-apply workflow instead.

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

No. It edits only files listed in existingOutputPaths and never creates new artifacts or files under glob patterns. Creating missing artifacts is deferred to the /opsx-continue workflow.

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

It runs openspec list --json and presents the top 3-4 most recently modified changes with schema, task status, and modification time, marking the most recent as recommended, then asks you to select one.

When should I start a new change instead of updating one?▼

If the request changes the change's intent rather than refining it, the Skill recommends starting fresh with /opsx-new when available, or openspec new change with a distinct unused name otherwise.