openspec-update-change

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

Updated Aug 29, 2026
One-click install
npx skills add https://github.com/Joao-Camilo-Mallmann/ofurry-motion-graphics --skill openspec-update-change-joao-camilo-mallmann
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-update-change
Source: https://github.com/Joao-Camilo-Mallmann/ofurry-motion-graphics/tree/main/.agents/skills/openspec-update-change
Command: npx skills add https://github.com/Joao-Camilo-Mallmann/ofurry-motion-graphics --skill openspec-update-change-joao-camilo-mallmann

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a change plan evolves, its OpenSpec planning artifacts (proposals, designs, specs, tasks) drift out of sync. This Skill revises the existing artifacts of an OpenSpec change and reconciles them against one another, without ever touching implementation code. ## Core Features & Use Cases - Guided change selection: Lists available changes via openspec list --json and prompts the user to pick one, never guessing. - Schema-aware reconciliation: Reads artifact status and paths from openspec status --json, so custom schemas work without hardcoded artifact names. - Bidirectional coherence checks: An edit to a later artifact can trigger revisions to earlier ones, with every edit confirmed by the user before writing. - Use Case: After deciding the design now uses a different data model, ask the assistant to update the change; it revises the design artifact, detects contradictions in the proposal and tasks, and proposes confirmed fixes. ## Quick Start Ask the assistant to update the OpenSpec change named "add-auth" so its planning artifacts reflect the new design 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 OpenSpec change after a design decision changes?

Invoke the update workflow with the change name; it reads the change's artifacts via openspec status, applies your requested edit, then checks all other existing artifacts for contradictions and proposes confirmed revisions.

How does the skill know which artifacts a change has?

It runs openspec status --change <name> --json and uses the returned artifact ids and existingOutputPaths. It never assumes hardcoded artifact names, so custom schemas work unchanged.

Can it 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 are deferred to /opsx:apply.

What happens if I don't specify a change name?

It runs openspec list --json and prompts you to choose from the most recently modified changes, marking the latest as recommended. It never auto-selects a change on its own.

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

If the request changes the change's core intent rather than refining it, the skill recommends starting fresh with /opsx:new instead of rewriting the existing plan.