openspec-update-change

Revise OpenSpec change planning artifacts and reconcile them for coherence.

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/CoderCoco-Studios/Hyveon --skill openspec-update-change-codercoco-studios
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-update-change
Source: https://github.com/CoderCoco-Studios/Hyveon/tree/main/.claude/skills/openspec-update-change
Command: npx skills add https://github.com/CoderCoco-Studios/Hyveon --skill openspec-update-change-codercoco-studios

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 ever 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 --change <name> --json and reconciles 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 now uses a different storage approach, ask the Skill to update the change; it revises the design artifact and reconciles the proposal and tasks to match. ## Quick Start Ask the assistant to update the current OpenSpec change so its design reflects the new decision and the other artifacts 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 existing OpenSpec change plan?

Invoke the update workflow with a change name or let it infer one from context. It runs openspec status to read existing artifacts, applies your requested revision, and reconciles the other artifacts after you confirm each edit.

How does the skill choose which change to update?

It uses a provided name, infers from conversation context, or auto-selects when only one active change exists. If ambiguous, it runs openspec list --json and presents the most recently modified changes for you to pick.

Can it create new artifacts or edit implementation code?

No. It only revises files that already exist in the change's existingOutputPaths and never edits code. Missing artifacts are deferred to the continue workflow, and code changes are deferred to the apply workflow.

What happens if my request changes the change's intent entirely?

The skill treats intent changes as out of scope for an update and recommends starting fresh with a new change instead of rewriting the existing plan.

Does it work with custom OpenSpec schemas?

Yes. It reads artifact ids and paths from openspec status output rather than hardcoding artifact names, so custom schemas work unchanged.