openspec-update-change

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

Updated Aug 25, 2026
One-click install
npx skills add https://github.com/KevMendesDev/mercadinho-sao-francisco --skill openspec-update-change-kevmendesdev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-update-change
Source: https://github.com/KevMendesDev/mercadinho-sao-francisco/tree/main/.agents/skills/openspec-update-change
Command: npx skills add https://github.com/KevMendesDev/mercadinho-sao-francisco --skill openspec-update-change-kevmendesdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a plan changes mid-work, OpenSpec change artifacts (proposals, designs, specs, tasks) drift out of sync with each other. This Skill revises the existing planning artifacts of an OpenSpec change so they stay consistent, without ever touching implementation code. ## Core Features & Use Cases - Targeted revision: Apply a specific user-requested edit (e.g., "the design now uses X") to the relevant artifact and propagate consequences across all other existing artifacts. - Coherence review: When asked only to "update" or "make coherent", read all existing artifacts and detect contradictions, gaps, and duplication in any direction. - Schema-agnostic operation: Uses openspec status and openspec instructions to discover artifact ids and paths dynamically, so custom schemas work unchanged. - Use Case: After deciding to switch a change's data layer from REST to GraphQL, ask the Skill to update the change; it revises the design artifact, reconciles the proposal and specs, and confirms each edit before writing. ## Quick Start Ask the assistant to update the OpenSpec change named "add-user-auth" so its artifacts reflect the new decision to use JWT sessions.

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 existing OpenSpec change after a design decision changes?▼

Invoke the update workflow with the change name and describe the revision. The Skill reads the change's artifacts via openspec status, applies the edit, checks every other existing artifact for contradictions, and confirms each revision with you before writing.

How does the Skill keep OpenSpec artifacts coherent with each other?▼

It reads all existing artifacts of the change, applies the requested edit, then cross-checks every artifact in any direction for inconsistencies, gaps, or duplication. Build order guides reading but does not restrict which artifacts may be revised.

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

Yes. It never assumes hardcoded artifact names; artifact ids and file paths come from openspec status and openspec instructions output. Custom schemas work unchanged because all paths are resolved dynamically from the active schema.

Can this Skill edit implementation code or create new artifacts?▼

No. It only revises files listed in existingOutputPaths of already-created artifacts. Creating new artifacts is delegated to the continue-change workflow, and code changes are delegated to the apply-change workflow.

What happens if the requested update changes the change's original intent?▼

The Skill recommends starting fresh instead of rewriting. If the new-change workflow is available it suggests that; otherwise it asks for a distinct unused change name and recommends running openspec new change.