openspec-update-change

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

Updated Sep 16, 2026
One-click install
npx skills add https://github.com/JoeShi/coding-agent-usage-montior --skill openspec-update-change-joeshi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-update-change
Source: https://github.com/JoeShi/coding-agent-usage-montior/tree/main/.kimi-code/skills/openspec-update-change
Command: npx skills add https://github.com/JoeShi/coding-agent-usage-montior --skill openspec-update-change-joeshi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an OpenSpec change plan evolves, its artifacts (proposal, design, specs, tasks) drift out of sync. This Skill revises existing planning artifacts so edits in one document are reconciled across all others, without touching implementation 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 different storage layer, ask the Skill to update the change; it revises the design doc and reconciles the proposal, specs, and tasks that referenced the old approach. ## Quick Start Ask the assistant to update the OpenSpec change named my-feature so its artifacts reflect the new design decision and stay consistent with each other.

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 list existing artifacts, reads them, applies your requested edit, and reconciles every other artifact for contradictions. Each revision is shown and confirmed before writing.

How to keep OpenSpec proposal, design, and tasks consistent?

Run a coherence review: the Skill reads all existing artifacts of the change and checks them against each other in any direction, flagging contradictions, gaps, and duplication, then proposes confirmed fixes per artifact.

Does openspec-update-change work with custom schemas?

Yes. It never hardcodes artifact names; it uses the artifact ids, statuses, and existingOutputPaths returned by openspec status --json, so custom schemas and glob artifacts work unchanged.

Can this Skill create new artifacts or edit code?

No. It only edits files that already exist in existingOutputPaths. Creating missing artifacts is delegated to openspec-continue-change, and code changes are delegated to openspec-apply-change.

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 runs openspec list --json and prompts with the most recently modified changes, marking the newest as recommended.