openspec-update-change

Revises existing OpenSpec change planning artifacts and reconciles them for coherence.

Updated Jun 13, 2026
One-click install
npx skills add https://github.com/anionDevelopment/Epew --skill openspec-update-change-aniondevelopment
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-update-change
Source: https://github.com/anionDevelopment/Epew/tree/main/.opencode/skills/openspec-update-change
Command: npx skills add https://github.com/anionDevelopment/Epew --skill openspec-update-change-aniondevelopment

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 - 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 and detects contradictions, gaps, and duplication in any direction. - Confirmed Edits Only: Proposes each revision, writes only after user confirmation, and never creates new artifacts or edits code. - Use Case: After deciding the design should use a different storage layer, ask the Skill to update the change so the design, specs, and tasks 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 token-based sessions.

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 plan?▼

Invoke the update workflow with the change name, or let it infer the change from context. It runs openspec status to list existing artifacts, applies your requested revision, and reconciles the other artifacts for consistency after your confirmation.

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

Describe the new decision and the Skill performs a coherence review across all existing artifacts in any direction, flagging contradictions and gaps. Each proposed revision is shown and written only after you confirm it.

Does the OpenSpec update workflow edit implementation code?▼

No, it only edits planning artifact files reported by openspec status as existingOutputPaths. If the revised plan implies code changes, it stops and points you to the apply workflow instead.

Can it create new artifacts that do not exist yet?▼

No, it never creates new artifacts or new files under glob artifacts. Missing artifacts are deferred to the continue workflow, which is responsible for advancing the build frontier.

What happens if the change name is ambiguous or missing?▼

It runs openspec list --json and presents the top 3-4 most recently modified changes with schema, task status, and modification time, marking the most recent as recommended so you can select one.