skills.rest
hpelaez73
hpelaez73COMMUNITY
Explore all skills by this author →
GitHub

openspec-update-change

Revises existing OpenSpec change planning artifacts and keeps them mutually coherent.

Updated Sep 2, 2026
Search Tags:#spec-driven#change management#openspec#planning artifacts#cli workflow#coherence review
One-click install
npx skills add https://github.com/hpelaez73/elprado-backend --skill openspec-update-change-hpelaez73
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-update-change
Source: https://github.com/hpelaez73/elprado-backend/tree/main/.trae/skills/openspec-update-change
Command: npx skills add https://github.com/hpelaez73/elprado-backend --skill openspec-update-change-hpelaez73

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a plan changes mid-work, OpenSpec change artifacts (proposals, designs, specs, tasks) drift out of sync with each other. This Skill revises the existing artifacts of a change and reconciles them 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 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 rather than hardcoded names, so custom schemas work unchanged. - Use Case: After deciding the design should use 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 design and specs reflect the new decision to use Redis.

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 the update workflow with the change name, and it reads the change's artifacts via openspec status, applies your requested edit, then checks every other existing artifact for contradictions. Each revision is shown and confirmed before writing.

How does the skill keep OpenSpec artifacts coherent with each other?▼

It reads all existing artifacts of the change and cross-checks them in any direction, since an edit to a later artifact may require revising an earlier one. It notes inconsistencies, gaps, and duplication, then proposes targeted revisions.

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

No. It only edits files listed in existingOutputPaths and never creates new artifacts or files under glob patterns. Missing artifacts are deferred to the openspec-continue-change workflow.

Does updating a change also modify the implementation code?▼

No, it never edits code. If the revised plan implies code changes, it stops and points you to the openspec-apply-change workflow to carry the delta into the implementation.

What happens if the change name is ambiguous or not provided?▼

It infers the change from conversation context or auto-selects when only one active change exists. Otherwise it runs openspec list and prompts you with the most recently modified changes, marking the latest as recommended.

Related Skills

Explore More Software Engineering Skills→
ondataondata
9

openspec-new-change

Initialize a new OpenSpec change with an artifact-driven workflow scaffold.

Official
Advanced
wishx127wishx127

openspec-archive-change

Archive completed OpenSpec changes after verifying artifacts and task status.

Community
Advanced
nfenfe
139

openspec-verify-change

Verify code implementation against OpenSpec change artifacts and task completion.

Official
Advanced
AskTinNguyenAskTinNguyen

code-simplifier

Refine recently modified code to improve readability and maintainability.

Community
Intermediate