openspec-update-change SKILL.md skillA

openspec-update-change from mememeow-studio/mememeow is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add mememeow-studio/mememeow/openspec-update-change@v1.0

Pins v1.0 in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

mememeow-studio/mememeow

Path

.opencode/skills/openspec-update-change/SKILL.md

Versions recorded

1

Latest version

v1.0, committed Aug 9, 2026

Size

6,832 bytes

Repository stars

1,264

License

AGPL-3.0

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.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

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

Read the whole file at its exact version.

How to install

mdr add mememeow-studio/mememeow/openspec-update-change@sha256:f4ffb89ece3be2a5

[![mdr](https://markdownregistry.com/badge/art_w7xla2mibzbj5n2g.svg)](https://markdownregistry.com/a/art_w7xla2mibzbj5n2g)

Versions

The registry has recorded 1 version of this file, committed on Aug 9, 2026.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_w7xla2mibzbj5n2g
GET https://markdownregistry.com/api/v1/resolve?ref=mememeow-studio/mememeow/openspec-update-change
GET https://markdownregistry.com/api/v1/blob/f4ffb89ece3be2a55a95a693ca0a1dbcd2139c17ab45edf796b14c99cb7d5a50

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from mememeow-studio/mememeow

Every file in mememeow-studio/mememeow

Other files named openspec-update-change

Browse by kind, by grade A, or by owner.