openspec-update-change

Revises existing OpenSpec change planning artifacts and reconciles inconsistencies between them.

7|Updated Jun 5, 2026
One-click install
npx skills add https://github.com/Printaga/PiLot --skill openspec-update-change-printaga
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-update-change
Source: https://github.com/Printaga/PiLot/tree/main/.agents/skills/openspec-update-change
Command: npx skills add https://github.com/Printaga/PiLot --skill openspec-update-change-printaga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a plan changes mid-project, OpenSpec change artifacts (proposals, designs, specs, tasks) drift out of sync with each other. This Skill revises an existing change's planning artifacts and keeps them coherent, without ever 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 with rationale 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 should use a different database, 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-auth so its design and specs 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 after a design decision changes?▼

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

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

It reads all existing artifacts of the change and compares them in any direction, since an edit to a later artifact may require revising an earlier one. It notes contradictions, gaps, and duplication, then proposes targeted revisions.

Can it create new artifacts or edit implementation code?▼

No. It only revises files that already exist in the change's existingOutputPaths and never edits code. Missing artifacts are deferred to /openspec-continue-change, and code changes are deferred to /openspec-apply-change.

Does it work with custom OpenSpec schemas?▼

Yes. It never assumes artifact ids or paths; it parses them from openspec status --json output, so custom schemas work unchanged. Glob artifacts are handled via their concrete existingOutputPaths, not the glob pattern.

What happens if I don't specify which change to update?▼

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