po4yka/RIPDPI / .agents/skills/openspec-update-change
openspec-update-change
VerifiedUpdate an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.
RIPDPI policy: use only the local repository planning home. OpenSpec stores, global configuration changes, direct archive, and telemetry are out of scope; ./taskctl enforces the pinned tool and disables telemetry.
Revise a change's existing planning artifacts and keep them coherent. Never edit code.
Repository root: Work only in the current RIPDPI checkout. Do not select or register OpenSpec stores. Run every CLI lookup through ./taskctl openspec cli from the repository root.
Input: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
$openspec-continue-change (Codex) or /openspec-continue-change (other agents) is an expanded-profile workflow and may not be installed. Before suggesting it anywhere below, verify that it is available. If it is unavailable, ./taskctl openspec cli status --change "<name>" --json shows the next artifact and ./taskctl openspec cli instructions "<artifact-id>" --change "<name>" --json explains how to create it.
Steps
-
Select the change
If a name is provided, use it. Otherwise:
- Infer from conversation context if the user mentioned a change
- Auto-select if only one active change exists
- If ambiguous, run
./taskctl openspec cli list --jsonto get available changes sorted by most recently modified, and ask the user to select one
When prompting, present the top 3-4 most recently modified changes as options, showing:
- Change name
- Schema (from
schemafield if present, otherwise "spec-driven") - Status (e.g., "0/5 tasks", "complete", "no tasks")
- How recently it was modified (from
lastModifiedfield)
Mark the most recently modified change as "(Recommended)" since it's likely what the user wants to update.
Always announce: "Using change: " and how to override (e.g.,
$openspec-update-change (Codex) or /openspec-update-change (other agents) <other>). -
Get the change's artifacts
./taskctl openspec cli status --change "<name>" --jsonParse the JSON to understand current state. The response includes:
schemaName: The workflow schema being used (e.g., "spec-driven")artifacts: Array of artifacts with their status ("done", "skipped", "ready", "blocked")isPlanningComplete: Boolean indicating if all planning artifacts are complete. Older CLI versions expose the same value asisComplete.planningHome,changeRoot,artifactPaths, andactionContext: path and scope context. Use these instead of assuming repo-local paths.
The artifact ids and paths come from the active schema - do NOT assume them, and do NOT branch on hardcoded artifact names. Custom schemas must work unchanged.
The files to edit are
artifactPaths.<id>.existingOutputPaths- the concrete files that exist on disk, already glob-expanded for glob artifacts (e.g.specs/**/*.md). Do NOT write toresolvedOutputPath: for a glob artifact it is still the glob pattern, not a real file. -
Understand the request
- If the user asked for a specific revision ("the design now uses X"), that is the starting edit.
- If they only said "update" / "make this coherent", treat it as a coherence review: read the existing artifacts and check them against each other for contradictions, gaps, and duplication.
-
Read and reconcile
- Read the artifact(s) the request touches and the change's other existing artifacts.
- Apply the requested edit. Then check every other existing artifact against it - in ANY direction: an edit to a later artifact may require revising an earlier one, not only the other way around. Build order is a useful reading order, not a constraint on which artifacts may be revised.
- Note everything that is now inconsistent, missing, or contradictory.
- Revise only files that already exist (
existingOutputPaths). Do NOT create artifacts that don't exist yet, and do NOT invent new files under a glob artifact - note them and point the user to$openspec-continue-change (Codex) or /openspec-continue-change (other agents)to create them. - If the change is already coherent, say so and make no edits.
-
Confirm and apply, one artifact at a time
- Show each proposed revision and why. Write only after the user confirms.
- If the user rejects a revision, do not write it - leave that artifact unchanged.
- When a substantial rewrite is needed, get that artifact's rules and template first:
./taskctl openspec cli instructions "<artifact-id>" --change "<name>" --json
-
Point to the next step (guidance only - NEVER act on it)
- Artifacts still missing -> suggest
$openspec-continue-change (Codex) or /openspec-continue-change (other agents)to create them. - Change already implemented (tasks checked off / already applied) -> the code may no longer match the revised plan; suggest
$openspec-apply-change (Codex) or /openspec-apply-change (other agents)to carry the delta into code. - Everything done and implemented -> suggest
$openspec-archive-change (Codex) or /openspec-archive-change (other agents).
- Artifacts still missing -> suggest
Output
After each invocation, show:
- Which artifacts were revised (and which proposed revisions were rejected)
- Anything deferred to
$openspec-continue-change (Codex) or /openspec-continue-change (other agents)(not-yet-created artifacts or files) - Where the change stands and the recommended next command
Guardrails
- Planning artifacts only - NEVER edit implementation code. If the revised plan implies code changes, stop and point to
$openspec-apply-change (Codex) or /openspec-apply-change (other agents). - Use the artifact ids and paths reported by
./taskctl openspec cli status; never branch on hardcoded artifact names. - Edit only the concrete files in
existingOutputPaths; never write to a globresolvedOutputPath. - Do not advance the build frontier: no new artifacts, no new files under glob artifacts - that is
$openspec-continue-change (Codex) or /openspec-continue-change (other agents)'s job. - Confirm every edit with the user before writing.
- If the request changes the change's intent rather than refining it, first verify whether the expanded-profile
$openspec-new-change (Codex) or /openspec-new-change (other agents)workflow is available. If it is, recommend starting fresh with$openspec-new-change (Codex) or /openspec-new-change (other agents)(the "Update vs. Start Fresh" heuristic). If it is unavailable, ask for a distinct unused change name and recommend./taskctl openspec cli new change "<new-change-name>"instead.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |