openspec-update-change

Revise OpenSpec change planning artifacts and reconcile them for coherence.

3|1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/firstsun-dev/skills --skill openspec-update-change-firstsun-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-update-change
Source: https://github.com/firstsun-dev/skills/tree/main/plugins/spec-driven-development/skills/openspec-update-change
Command: npx skills add https://github.com/firstsun-dev/skills --skill openspec-update-change-firstsun-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an OpenSpec change's plan evolves, its existing artifacts (proposal, design, specs, tasks) drift out of sync. This Skill revises those artifacts and keeps them mutually consistent without touching implementation code. ## Core Features & Use Cases - Targeted Revision: Apply a specific requested edit (e.g., "the design now uses X") to the relevant artifact and propagate consequences across all other existing artifacts. - Coherence Review: Read all existing artifacts of a change and detect contradictions, gaps, and duplication in any direction, not just build order. - Schema-Agnostic Operation: Uses artifact ids and paths reported by openspec status and openspec instructions, so custom schemas work without hardcoded assumptions. - Use Case: After a design review changes an API approach, run this Skill to update the design artifact, reconcile the proposal and tasks, and get pointed to /openspec-apply-change to carry the delta into code. ## Quick Start Ask the agent to update the OpenSpec change named "add-auth" so its design reflects the new token-based approach and keep the other artifacts 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's plan?▼

Invoke this Skill with the change name, and it runs openspec status to load existing artifacts, applies your requested revision, then checks every other artifact for inconsistencies. Each edit is shown and confirmed before writing.

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

The Skill reads all existing artifacts of the change and reconciles them in any direction, since an edit to a later artifact may require revising an earlier one. It reports contradictions, gaps, and duplication before proposing fixes.

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

Yes. It never hardcodes artifact names; it uses the artifact ids and paths returned by openspec status and openspec instructions from the active schema, so custom schemas work unchanged.

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

No. It only edits files listed in existingOutputPaths of already-created artifacts. Creating new artifacts is deferred to /openspec-continue-change, and code changes are deferred to /openspec-apply-change.

What happens if I don't specify a change name?▼

It infers the change from conversation context, auto-selects if only one active change exists, or lists the most recently modified changes via openspec list and asks you to pick one.