
openspec-update-change
Update an OpenSpec change by revising its existing planning artifacts
by fission-aiFree
Description
openspec-update-change is an agent skill from the OpenSpec project for revising a change's existing planning artifacts and keeping them consistent with one another. When the scope of a feature moves or a decision changes, the proposal, the spec deltas, the design and the tasks can drift apart, and this skill revises them together so they still agree. It is strictly about the planning documents: the skill never edits code. It is useful when a review finds a gap in the design, when the requirements change after a proposal is written, or when a task list no longer matches the spec. The skill keeps the usual OpenSpec guards. If the work lives in a registered store, it selects the store and passes the store id to the commands it runs, and it keeps that id for the whole workflow. Before any write, it confirms that the project has an OpenSpec root. If the project has no root, the skill follows the path that matches how it was reached: it answers normally when the workflow was chosen automatically, and it stops and asks how to proceed when you asked for OpenSpec by name. Install it with npx skills add https://github.com/fission-ai/openspec --skill openspec-update-change.…
Highlights
- Revises a change's proposal, specs, design and tasks together
- Keeps planning artifacts consistent with one another
- Never edits code
- Store selection and project root checks before writing
Ratings & Reviews
No ratings yet
Be the first to rate openspec-update-change.
People also visit

openspec-continue-change
Continue working on an OpenSpec change by creating the next artifact

openspec-propose
Propose a new OpenSpec change with all artifacts generated in one step

agent-swarm-memory-manager
Agent skill for swarm-memory-manager - invoke with $agent-swarm-memory-manager

sparc-methodology
SPARC development workflow: Specification, Pseudocode, Architecture, Refinement
openspec-update-change FAQ
When should I use it?
When requirements change, a review finds a gap in the design, or the task list no longer matches the spec.
Does it change code?
No. It revises the planning artifacts only.
What if the project is not set up for OpenSpec?
If you asked for OpenSpec by name, it stops and asks how to proceed. If it was chosen automatically, it answers the request without mentioning OpenSpec setup.
How do I install it?
Run npx skills add https://github.com/fission-ai/openspec --skill openspec-update-change.
What are the best openspec-update-change alternatives?
Popular alternatives to openspec-update-change include openspec-continue-change, openspec-ff-change and openspec-propose. See all openspec-update-change alternatives


