skills.rest
Jin1c-3
Jin1c-3COMMUNITY
Explore all skills by this author →
GitHub

openspec-update-change

Revise OpenSpec change planning artifacts and keep them coherent with each other.

4|Updated Aug 8, 2026
Search Tags:#spec-driven#change management#openspec#planning artifacts#cli workflow#coherence review
One-click install
npx skills add https://github.com/Jin1c-3/obsidian-advanced-maps --skill openspec-update-change-jin1c-3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-update-change
Source: https://github.com/Jin1c-3/obsidian-advanced-maps/tree/main/.agents/skills/openspec-update-change
Command: npx skills add https://github.com/Jin1c-3/obsidian-advanced-maps --skill openspec-update-change-jin1c-3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an OpenSpec change plan evolves, its artifacts (proposal, design, specs, tasks) drift out of sync. This Skill revises existing planning artifacts and reconciles them against one another so the change stays internally consistent, without touching implementation code. ## Core Features & Use Cases - Coherence Review: Reads all existing artifacts of a change and detects contradictions, gaps, and duplication in any direction, not just build order. - Guided Revision: Proposes edits one artifact at a time and writes only after user confirmation, using the artifact paths reported by openspec status. - Schema-Agnostic: Works with any OpenSpec workflow schema by reading artifact ids and paths from the CLI instead of hardcoding names. - Use Case: After deciding the design now uses a different storage approach, ask the agent to update the change; it revises the design doc, then reconciles the proposal, specs, and tasks to match. ## Quick Start Ask the agent to update the OpenSpec change named "add-dark-mode" so its design and specs reflect the new caching 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 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, reads them, proposes revisions one at a time, and writes only after you confirm each edit.

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

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

Does the OpenSpec update workflow edit implementation code?▼

No. It only edits planning artifacts listed in existingOutputPaths. If the revised plan implies code changes, it stops and points you to the apply-change workflow instead.

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

No. It only revises files that already exist and never creates new artifacts or files under glob artifacts. Creating missing artifacts is delegated to the continue-change workflow.

What happens if the update changes the change's intent entirely?▼

If the request alters intent rather than refining the plan, the skill recommends starting fresh with the new-change workflow or running openspec new change with a distinct unused name instead of rewriting the existing change.

Related Skills

Explore More Software Engineering Skills→
zdpkzdpk

openspec

Manage OpenSpec change artifacts and validate progress with the OpenSpec CLI.

Community
Intermediate
minhquan2904minhquan2904

review

Scan openspec/changes and source code to generate delta documentation artifacts.

Community
Advanced
soyrochussoyrochus

openspec-archive-change

Validate and archive completed OpenSpec changes with optional delta spec sync.

Community
Advanced
cwijayasundaracwijayasundara
3

sprouting-instead-of-editing

Generate new tested code units for legacy code changes.

Community
Advanced