openspec-update-change

Revise OpenSpec change planning artifacts and reconcile them for coherence.

1|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/creevey/rprtr --skill openspec-update-change-creevey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-update-change
Source: https://github.com/creevey/rprtr/tree/main/.opencode/skills/openspec-update-change
Command: npx skills add https://github.com/creevey/rprtr --skill openspec-update-change-creevey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a change plan evolves, its existing planning artifacts (proposals, designs, specs, tasks) drift out of sync with each other. This Skill revises an OpenSpec change's existing artifacts and keeps them mutually consistent without touching implementation code. ## Core Features & Use Cases - Coherence Review: Reads all existing artifacts of a change and detects contradictions, gaps, and duplication across them in any direction. - 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 now uses a different approach, ask the Skill to update the change; it revises the design artifact and reconciles the proposal, specs, and tasks against it. ## Quick Start Ask the assistant to update the OpenSpec change named "add-auth" so its planning artifacts reflect the new design decision.

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?

Provide the change name or let the Skill infer it from context; it runs openspec status to list artifacts, reads the relevant files, proposes revisions, and writes them only after you confirm each edit.

How to keep OpenSpec planning artifacts consistent after a design change?

The Skill performs a coherence review: it reads all existing artifacts of the change, checks them against the requested edit in any direction, and revises whichever artifacts are now inconsistent, missing, or contradictory.

Does this Skill work with custom OpenSpec schemas?

Yes. It never assumes artifact names or paths; it uses the artifact ids and existingOutputPaths reported by openspec status --json, so custom schemas work unchanged.

Can it create new artifacts or edit implementation code?

No. It only revises files that already exist and never edits code. Missing artifacts are deferred to /opsx-continue, and code changes implied by a revised plan are deferred to /opsx-apply.

What happens if the change name is ambiguous?

It runs openspec list --json and prompts you with the top 3-4 most recently modified changes, showing schema, task status, and last-modified time, marking the most recent as recommended.