openspec-update-change
From the author
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.
Install
npx skills add MemeMeow-Studio/MemeMeow --skill openspec-update-change -a claude-code
Installs to .claude/skills/openspec-update-change/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 88
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- openspec-apply-changeMemeMeow-Studio/MemeMeowImplement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.Productivity★ 1.3K
- openspec-sync-specsMemeMeow-Studio/MemeMeowSync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.Planning★ 1.3K
- openspec-archive-changeMemeMeow-Studio/MemeMeowArchive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.Productivity★ 1.3K
- openspec-proposeMemeMeow-Studio/MemeMeowPropose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.Design★ 1.3K
- update-specificationgithub/awesome-copilotUpdate an existing specification file for the solution, optimized for Generative AI consumption based on new requirements or updates to any existing code.Planning★ 40.3K
- close-specdzhng/skillsWhen a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [write-spec](../write-spec/SKILL.md) (the plan this closes) and [review](../review/SKILL.md) (run before closing).Planning★ 1.4K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in