skills.rest
javakishore-veleti
javakishore-veletiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-update-change

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

Updated Aug 7, 2026
Search Tags:#workflow#spec-driven#cli#change management#openspec#planning artifacts#coherence review
One-click install
npx skills add https://github.com/javakishore-veleti/lifting-diary-app --skill openspec-update-change-javakishore-veleti
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-update-change
Source: https://github.com/javakishore-veleti/lifting-diary-app/tree/main/.qwen/skills/openspec-update-change
Command: npx skills add https://github.com/javakishore-veleti/lifting-diary-app --skill openspec-update-change-javakishore-veleti

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a plan changes mid-project, the proposal, design, specs, and tasks inside an OpenSpec change drift out of sync. This Skill revises the existing planning artifacts of a change and reconciles them against one another so the plan stays internally consistent, without touching any 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. - 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 workflow schemas work unchanged. - Use Case: After deciding the design should use a different database approach, ask the Skill to update the change; it revises the design doc, then checks the proposal and specs for statements that now conflict and proposes fixes. ## Quick Start Ask the assistant to update the OpenSpec change named "add-auth" 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 after a design decision changes?▼

Invoke this Skill with the change name and describe the revision. It reads the change's existing artifacts via openspec status, applies the requested edit, then checks every other artifact for contradictions and proposes fixes for your confirmation.

How does the Skill keep OpenSpec artifacts consistent with each other?▼

It reads all existing artifacts of the change and compares them in any direction, since an edit to a later artifact may require revising an earlier one. It flags inconsistencies, gaps, and duplication, then proposes one confirmed revision at a time.

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

No. It only revises files that already exist in existingOutputPaths and never edits code. Missing artifacts are deferred to /opsx-continue, and code changes implied by a revised plan are deferred to /opsx-apply.

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

Yes. It takes artifact ids and paths from the openspec status JSON response rather than hardcoding artifact names, so custom schemas work unchanged. It also supports registered stores via the --store flag.

When should I start a fresh change instead of updating an existing one?▼

If the request changes the change's intent rather than refining it, the Skill recommends starting fresh with /opsx-new when available, or running openspec new change with a distinct unused name otherwise.

Related Skills

Explore More Software Engineering Skills→
CoderCoco-StudiosCoderCoco-Studios
1

openspec-update-change

Revise OpenSpec change planning artifacts and reconcile them for coherence.

Official
Intermediate
LudoBermejoESLudoBermejoES

openspec-archive-change

Archive completed OpenSpec changes with date-prefixed directory moves.

Community
Advanced
farmountainfarmountain

openspec-bulk-archive-change

Archive multiple completed OpenSpec changes while preserving metadata.

Community
Advanced
cwijayasundaracwijayasundara
3

sprouting-instead-of-editing

Generate new tested code units for legacy code changes.

Community
Advanced