openspec-update-change

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

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/hongwt/dsplm-monitor --skill openspec-update-change-hongwt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-update-change
Source: https://github.com/hongwt/dsplm-monitor/tree/main/.pi/skills/openspec-update-change
Command: npx skills add https://github.com/hongwt/dsplm-monitor --skill openspec-update-change-hongwt

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 that confuse implementation. This Skill revises existing artifacts and reconciles them against one another without touching 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 schemas work without hardcoded assumptions. - Use Case: After deciding the design now uses a message queue instead of direct calls, 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 "add-caching" so its design reflects the new decision and all 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 OpenSpec change after a design decision changes?▼

Run the update workflow with the change name; it reads the change's existing artifacts via openspec status, applies your requested edit, then checks every other artifact for contradictions. Each revision is shown and confirmed before writing.

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

Invoke the update workflow without a specific edit to trigger a coherence review. It reads all existing artifacts, flags contradictions, gaps, and duplication, and proposes targeted revisions in any direction across the artifact set.

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

Yes, it works with custom schemas unchanged. It reads artifact ids and paths from openspec status JSON output rather than assuming hardcoded artifact names, so any active schema is supported.

Can this skill create new artifacts or edit code?▼

No, it only revises files that already exist in existingOutputPaths and never edits implementation code. Creating missing artifacts is deferred to /opsx-continue, and code changes are deferred to /opsx-apply.

What happens if the change name is ambiguous or missing?▼

It infers the change from conversation context or auto-selects when only one active change exists. Otherwise it lists the most recently modified changes with status and asks you to pick one.