openspec-update-change

Revises OpenSpec change planning artifacts and keeps them coherent with each other.

Updated Jul 1, 2025
One-click install
npx skills add https://github.com/mosakuzii0216/mosaku-v1 --skill openspec-update-change-mosakuzii0216
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-update-change
Source: https://github.com/mosakuzii0216/mosaku-v1/tree/main/.claude/skills/openspec-update-change
Command: npx skills add https://github.com/mosakuzii0216/mosaku-v1 --skill openspec-update-change-mosakuzii0216

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a change plan evolves, its OpenSpec planning artifacts (proposals, designs, specs, tasks) drift out of sync. This Skill revises existing artifacts of an OpenSpec change and reconciles them against one another 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 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 --json, so custom schemas work without hardcoded assumptions. - Use Case: After deciding the design now uses a message queue instead of direct API calls, ask the Skill to update the change; it revises the design artifact and reconciles the proposal, specs, and tasks to match. ## Quick Start Ask the assistant to update the OpenSpec change named "add-caching" so its planning artifacts reflect the new design decision and 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 OpenSpec change after a design decision changes?

Invoke the update workflow with the change name and describe the revision. The Skill reads the change's existing artifacts via openspec status, applies your edit, then checks every other artifact for contradictions and proposes confirmed fixes.

How to keep OpenSpec planning artifacts consistent with each other?

Run a coherence review: the Skill reads all existing artifacts of the change and checks them against each other for contradictions, gaps, and duplication in any direction, then proposes revisions one artifact at a time for your confirmation.

Does updating an OpenSpec change also modify the implementation code?

No. The Skill only edits planning artifacts and never touches implementation code. If the revised plan implies code changes, it stops and points you to the apply workflow to carry the delta into code.

Can it create new artifacts that don't exist yet in a change?

No. It only revises files that already exist in existingOutputPaths and never creates new artifacts or files under glob patterns. Missing artifacts are deferred to the continue workflow, which it suggests as the next step.

What happens if my change name is ambiguous or not provided?

The Skill infers the change from conversation context, auto-selects if only one active change exists, or lists the most recently modified changes via openspec list --json and asks you to pick, marking the most recent as recommended.