openspec-update-change

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

Updated Sep 7, 2026
One-click install
npx skills add https://github.com/raphaelmans/spectralpointengineering --skill openspec-update-change-raphaelmans
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-update-change
Source: https://github.com/raphaelmans/spectralpointengineering/tree/main/.skillshare/skills/openspec-update-change
Command: npx skills add https://github.com/raphaelmans/spectralpointengineering --skill openspec-update-change-raphaelmans

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, leaving contradictions and gaps. This Skill revises existing artifacts of an OpenSpec change and reconciles them against one another without 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 so you can pick one. - Coherence Review: Reads all existing artifacts reported by openspec status and detects contradictions, gaps, and duplication in any direction, not just build order. - Confirmed Edits Only: Proposes each revision, writes only after your approval, and never creates new artifacts or edits code. - Use Case: After deciding the design now uses a different data model, ask the Skill to update the change; it revises the design artifact and reconciles the proposal and specs to match. ## Quick Start Ask the assistant to update the OpenSpec change named my-feature 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 runs openspec status to read existing artifacts, applies your requested edit, then checks every other artifact for contradictions. Each revision is shown for confirmation before being written.

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 lists the most recently modified changes via openspec list --json and asks you to pick one.

Can it edit implementation code when the plan changes?

No. It only revises planning artifacts and never touches code. If the revised plan implies code changes, it stops and points you to the /opsx:apply workflow to carry the delta into code.

Does it work with custom OpenSpec schemas and artifact names?

Yes. It reads artifact ids and paths from openspec status output rather than hardcoding names, so custom schemas work unchanged. It edits only concrete files in existingOutputPaths, never glob patterns.

What are the limitations of updating a change this way?

It cannot create new artifacts or add 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.