openspec-update-change

Revises OpenSpec change planning artifacts and reconciles them for coherence.

5.7k|321|Updated Feb 10, 2025
One-click install
npx skills add https://github.com/AmanVarshney01/create-better-t-stack --skill openspec-update-change
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-update-change
Source: https://github.com/AmanVarshney01/create-better-t-stack/tree/main/.codex/skills/openspec-update-change
Command: npx skills add https://github.com/AmanVarshney01/create-better-t-stack --skill openspec-update-change

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a project's plan changes mid-stream, the existing OpenSpec planning artifacts (proposals, designs, specs, tasks) drift out of sync with each other. This Skill updates an existing change's artifacts and keeps them mutually consistent without touching implementation code.

Core Features & Use Cases

  • Guided change selection: Lists available changes via openspec list --json and prompts the user to pick one, never guessing.
  • Coherence review: Reads all existing artifacts of a change, detects contradictions, gaps, and duplication, and proposes revisions in any direction across the artifact chain.
  • Confirmed, artifact-by-artifact edits: Shows each proposed revision and writes only after user confirmation, using schema-reported paths from openspec status.
  • Use Case: After deciding to switch the design from REST to tRPC, ask the assistant to update the change so the proposal, design, and specs all reflect the new decision consistently.

Quick Start

Ask the assistant to update the OpenSpec change named add-auth so its design and specs reflect the new decision to use tRPC.

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?

Invoke the skill with a change name, or let it list available changes via openspec list --json so you can pick one. It reads the change's artifacts with openspec status, proposes revisions, and writes each edit only after you confirm.

How to keep OpenSpec planning 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 for contradictions, gaps, and duplication, then revises affected files in any direction, not just build order.

Does openspec-update-change edit implementation code?

No. It only edits planning artifacts that already exist on disk. If the revised plan implies code changes, it stops and points you to /opsx:apply to carry the delta into code.

Can it create new artifacts or files for a change?

No. It only revises files listed in existingOutputPaths reported by openspec status. Creating missing artifacts or new files under glob artifacts is deferred to /opsx:continue.

What are the requirements for using this skill?

It requires the openspec CLI installed and an OpenSpec change with existing planning artifacts, either in a local openspec/ root or a registered store selected with the --store flag.