openspec-update-change

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

1|Updated Jun 30, 2026
One-click install
npx skills add https://github.com/trutoman/Conjuros --skill openspec-update-change-trutoman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-update-change
Source: https://github.com/trutoman/Conjuros/tree/main/.opencode/skills/openspec-update-change
Command: npx skills add https://github.com/trutoman/Conjuros --skill openspec-update-change-trutoman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an OpenSpec change plan evolves, its artifacts (proposals, designs, specs, tasks) drift out of sync. This Skill revises existing planning artifacts and reconciles them against one another so the change stays internally consistent, without ever touching implementation code. ## Core Features & Use Cases - Coherence Review: Reads all existing artifacts of a change and detects contradictions, gaps, and duplication across them. - Targeted Revision: Applies a requested edit (e.g., a design decision change) and propagates its impact to every other affected artifact, in either direction of the build order. - Schema-Agnostic Operation: Uses artifact ids and paths reported by openspec status --json, so custom workflow schemas work without hardcoded assumptions. - Use Case: After deciding to switch a change's design 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 token-based 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 plan?

Invoke the update workflow with the change name, or let it infer the change from context. It runs openspec status to list existing artifacts, applies your requested revision, reconciles the other artifacts, and confirms each edit before writing.

How does the skill keep OpenSpec artifacts consistent?

It reads every existing artifact of the change and checks them against each other for contradictions, gaps, and duplication. An edit to a later artifact can trigger revisions to earlier ones, since build order is only a reading order, not a constraint.

Can it create new artifacts or spec files for a change?

No. It only edits files that already exist in existingOutputPaths and never creates new artifacts or files under glob patterns. Missing artifacts are deferred to the continue workflow or the openspec instructions CLI command.

Does it work with custom OpenSpec workflow schemas?

Yes. Artifact ids and paths come from the active schema reported by openspec status --json, never from hardcoded names, so custom schemas work unchanged.

Will it modify my implementation code?

No. It edits planning artifacts only and never touches code. If a revised plan implies code changes, it stops and points you to the apply workflow instead.

What happens if the change name is ambiguous?

It runs openspec list --json and prompts you with the top 3-4 most recently modified changes, showing schema, task status, and modification time, marking the most recent one as recommended.