openspec-update-change

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

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/ssttkkl/finance-tracker --skill openspec-update-change-ssttkkl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-update-change
Source: https://github.com/ssttkkl/finance-tracker/tree/main/.agents/skills/openspec-update-change
Command: npx skills add https://github.com/ssttkkl/finance-tracker --skill openspec-update-change-ssttkkl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a plan changes mid-flight, the proposal, design, specs, and tasks inside an OpenSpec change drift out of sync. This Skill revises the existing planning artifacts of a change and reconciles them against each other, without ever 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 --change <name> --json and checks them for contradictions, gaps, and duplication in any direction. - Confirmed Edits Only: Proposes revisions one artifact at a time and writes only after user confirmation, editing only files in existingOutputPaths. - Use Case: After deciding to switch the design from REST to events, ask the Skill to update the change; it revises the design artifact, then reconciles the proposal and specs that referenced the old approach. ## Quick Start Ask the assistant to update the current OpenSpec change so the design uses the new approach and the other artifacts stay consistent.

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 update workflow with an optional change name; it runs openspec status --change <name> --json to find existing artifacts, applies your requested revision, and reconciles the other artifacts. Every edit is shown and confirmed before writing.

How does the skill choose which change to update?

It uses a provided name, infers from conversation context, or auto-selects when only one active change exists. If ambiguous, it runs openspec list --json and presents the most recently modified changes for you to pick.

Can it create new artifacts or edit implementation code?

No. It only edits files listed in existingOutputPaths and never creates new artifacts or touches code. Missing artifacts are deferred to the continue-change workflow, and code changes are deferred to apply-change.

Does it work with custom OpenSpec schemas and stores?

Yes. Artifact ids and paths come from the active schema reported by openspec status, never hardcoded. If a store is named, it discovers store ids via openspec store list --json and passes --store <id> to relevant commands.

What happens if the change is already coherent?

It reports that the artifacts are consistent and makes no edits. It then suggests the appropriate next step, such as continue-change for missing artifacts or archive-change when everything is complete.