openspec-update-change

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

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/74th/test-llm-agent --skill openspec-update-change-74th
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-update-change
Source: https://github.com/74th/test-llm-agent/tree/main/20260922-openai-agentapi-selfhosted-sandbox/.agents/skills/openspec-update-change
Command: npx skills add https://github.com/74th/test-llm-agent --skill openspec-update-change-74th

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 existing artifacts for a change, reconciles contradictions and gaps across them, and applies confirmed edits without ever touching implementation code. ## Core Features & Use Cases - Coherence Review: Reads all existing artifacts of a change and checks them against each other for contradictions, gaps, and duplication. - Guided Revision: Drafts each proposed edit in conversation, confirms with the user, then writes one artifact at a time using paths reported by openspec status. - Store and Schema Awareness: Supports registered OpenSpec stores via --store <id> and works with custom schemas by using artifact ids from the CLI instead of hardcoded names. - Use Case: After deciding the design now uses a message queue, ask the Skill to update the change; it revises the design artifact, detects the affected spec and task entries, and proposes consistent edits for your approval. ## Quick Start Ask the AI to update the OpenSpec change named add-auth so its design and specs reflect the new decision to use JWT tokens.

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?▼

Invoke this Skill with a change name, or let it infer one from context. It runs openspec status to list existing artifacts, drafts revisions in conversation, and writes each confirmed edit one artifact at a time.

How to keep OpenSpec planning artifacts consistent after a design decision changes?▼

Describe the new decision and the Skill performs a coherence review: it reads all existing artifacts, identifies contradictions and gaps in any direction, and proposes reconciling edits for your confirmation before writing.

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

Yes. It reads artifact ids and paths from openspec status JSON output rather than hardcoding names, so custom schemas work unchanged. Registered stores are supported by passing --store <id> to CLI commands.

Can this Skill create missing artifacts or edit code?▼

No. It only revises files listed in existingOutputPaths and never creates new artifacts, new files under glob artifacts, or implementation code. Missing artifacts are deferred to openspec instructions, and code changes are handed to openspec-apply-change.

What happens if the project has no OpenSpec root?▼

The Skill checks openspec list --json for a root before any write. If none exists and OpenSpec was explicitly requested, it asks whether to run openspec init, target a store, or continue without OpenSpec; it never creates the root as a side effect.