openspec-update-change

Revise OpenSpec change planning artifacts and reconcile them for coherence.

1|Updated Aug 13, 2026
One-click install
npx skills add https://github.com/Miftah-Fentaw/GymPulse --skill openspec-update-change-miftah-fentaw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-update-change
Source: https://github.com/Miftah-Fentaw/GymPulse/tree/main/.qwen/skills/openspec-update-change
Command: npx skills add https://github.com/Miftah-Fentaw/GymPulse --skill openspec-update-change-miftah-fentaw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an OpenSpec change's plan evolves, its existing artifacts (proposal, design, tasks, specs) drift out of sync. This Skill revises those artifacts and keeps them mutually consistent without touching implementation code. ## Core Features & Use Cases - Coherence Review: Reads all existing artifacts of a change and detects contradictions, gaps, and duplication across them. - Guided Revision: Proposes edits one artifact at a time and writes only after user confirmation, using artifact ids and paths reported by the openspec CLI. - Store-Aware Workflow: Supports registered OpenSpec stores via --store <id> and works with custom schemas without hardcoded artifact names. - Use Case: After deciding the design now uses a different approach, ask the Skill to fold that decision into the change; it updates the design artifact and reconciles the proposal and tasks accordingly. ## Quick Start Ask the assistant to update the OpenSpec change named my-change so its 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?▼

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

How to keep OpenSpec planning artifacts consistent with each other?▼

Invoke the Skill with a generic update request to trigger a coherence review. It reads all existing artifacts of the change, identifies inconsistencies, gaps, and duplication, and proposes fixes one artifact at a time before writing.

Does openspec-update-change edit implementation code?▼

No, it only edits planning artifacts that already exist on disk. If a revised plan implies code changes, it stops and points you to the /opsx-apply workflow to carry the delta into code.

Can I use this Skill with OpenSpec stores and custom schemas?▼

Yes. It discovers registered stores with openspec store list --json and passes --store <id> to scoped commands. Artifact ids and paths come from the active schema, so custom schemas work without hardcoded names.

What are the limitations of updating an OpenSpec change this way?▼

It cannot create new artifacts or new files under glob artifacts; those are deferred to /opsx-continue. If the request changes the change's intent rather than refining it, it recommends starting a fresh change instead.