openspec-update-change

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

Updated Mar 7, 2024
One-click install
npx skills add https://github.com/girlguidingstaplehurst/booking --skill openspec-update-change-girlguidingstaplehurst
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-update-change
Source: https://github.com/girlguidingstaplehurst/booking/tree/main/.opencode/skills/openspec-update-change
Command: npx skills add https://github.com/girlguidingstaplehurst/booking --skill openspec-update-change-girlguidingstaplehurst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a plan changes mid-project, OpenSpec change artifacts (proposals, designs, specs, tasks) drift out of sync with each other. This Skill revises the existing artifacts of an OpenSpec change and reconciles them so the plan stays internally consistent, without ever touching implementation code. ## Core Features & Use Cases - Coherence Review: Reads all existing artifacts of a change and detects contradictions, gaps, and duplication between them. - Targeted Revision: Applies a requested edit (e.g., "the design now uses X") and propagates its implications across every other existing artifact, in either direction. - Store-Aware Operation: Supports registered OpenSpec stores via openspec store list --json and a sticky --store <id> flag for all read/write commands. - Use Case: After deciding to switch your booking system's calendar backend, ask the Skill to update the change's design artifact; it will also flag and revise the proposal and tasks that referenced the old backend. ## Quick Start Ask the assistant to update the OpenSpec change named "booking-calendar" so its design reflects the new decision, and confirm each proposed revision before it is written.

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?▼

Run the update workflow with the change name and describe the new decision. The Skill reads the change's existing artifacts via openspec status, applies the edit, then checks every other artifact for contradictions and proposes revisions for your confirmation.

How do I keep OpenSpec planning artifacts consistent with each other?▼

Invoke the update workflow without a specific edit to trigger a coherence review. It reads all existing artifacts of the change, identifies contradictions, gaps, and duplication, and proposes reconciling revisions one artifact at a time.

Does openspec-update-change modify 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 /opsx-apply workflow to carry the delta into code.

Can I use this with a registered OpenSpec store instead of a local repo?▼

Yes. It runs openspec store list --json to discover registered store ids, then appends --store <id> to all commands that read or write specs and changes. Without a store, commands act on the nearest local openspec/ root.

What are the limitations of updating an OpenSpec change this way?▼

It only edits files that already exist in the change's existingOutputPaths and never creates new artifacts or files under glob patterns. Creating missing artifacts requires /opsx-continue, and a change of intent should start fresh with a new change instead.