openspec-update-change

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

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/neuthos/ldx-monorepo --skill openspec-update-change-neuthos
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-update-change
Source: https://github.com/neuthos/ldx-monorepo/tree/main/.agents/skills/openspec-update-change
Command: npx skills add https://github.com/neuthos/ldx-monorepo --skill openspec-update-change-neuthos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a plan changes mid-stream, OpenSpec change artifacts (proposals, designs, 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 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. - Confirmed Revisions: Proposes each edit, explains why, and writes only after user confirmation, one artifact at a time. - Schema-Agnostic Operation: Uses artifact ids and paths reported by openspec status rather than hardcoded names, so custom schemas work unchanged. - Use Case: After deciding the design will use a different data store, ask the Skill to update the change; it revises the design artifact and reconciles the proposal, specs, and tasks against the new decision. ## Quick Start Ask the assistant to update the OpenSpec change named add-caching so its artifacts reflect the new decision to use Redis.

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 a change name, or let it infer one from context. It runs openspec status to list existing artifacts, reads them, proposes revisions, and writes each edit only after you confirm.

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

Request a coherence review of the change. The Skill reads all existing artifacts, checks them against each other in any direction for contradictions or gaps, and proposes reconciling edits one artifact at a time.

Can this Skill edit implementation code or create new artifacts?▼

No. It only revises files listed in existingOutputPaths of already-created artifacts. Creating new artifacts is delegated to the continue-change workflow, and code changes are delegated to the apply-change workflow.

Does openspec-update-change work with custom schemas?▼

Yes. It never assumes artifact names or paths; it uses the artifact ids, schema name, and concrete file paths reported by openspec status, so custom schemas work unchanged.

How do I update a change in a registered OpenSpec store?▼

Run openspec store list --json to find the store id, then the Skill appends --store <id> to every read and write command. The flag stays sticky for the rest of the workflow.