# Openspec Update Change

Update an OpenSpec change by revising its existing planning artifacts and keeping them...

- Repository: https://github.com/MemeMeow-Studio/MemeMeow (1262 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-12
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add MemeMeow-Studio/MemeMeow --skill openspec-update-change -g -a claude-code -y`
Codex: `npx skills add MemeMeow-Studio/MemeMeow --skill openspec-update-change -g -a codex -y`
Cursor: `npx skills add MemeMeow-Studio/MemeMeow --skill openspec-update-change -g -a cursor -y`
Gemini CLI: `npx skills add MemeMeow-Studio/MemeMeow --skill openspec-update-change -g -a gemini-cli -y`

## Description

Update 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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

Revise a change's existing planning artifacts and keep them coherent. Never edit code.

**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`, `view`). Once selected, treat `--store <id>` as sticky for the rest of the workflow. Every unscoped example of those commands below is shorthand: before running it, append the flag. For example, run `openspec status --change "<name>" --json --store "<id>"`, not the unscoped form shown below. Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` 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, `openspec status --change "<name>" --json` shows the next artifact and `openspec instructions "<artifact-id>" --change "<name>" --json` explains how to create it.

**Steps**

1. **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 `openspec list --json` to get available changes sorted by most recently modified, and ask the user to select one

The rest: https://github.com/MemeMeow-Studio/MemeMeow/blob/HEAD/.agents/skills/openspec-update-change/SKILL.md