pm-change
Skill2 starsChanged 41 days agoMITView on GitHub
The change valve. Any time an epic or story is added, cut or reshaped after its gate was approved, this computes the blast radius, shows it, and then updates the TRD, writes or supersedes an ADR, re-parents or cuts work items, and flags stale screen approvals. Use whenever scope changes mid-flight, when the user says "/pm-change", "actually let's also", "drop that feature", "change the flow", or when implementation contradicts the spec.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- konglong87/superPMtheir own version, first seen Mar 27, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- konglong87/superPM★ 84same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Run this the moment the shape of the product changes after its gate was approved.
- Distinctive: line 27
Do not guess it. Query it.
- Very specific: line 70
Work tree: Add, cut, or re-scope. A cut item is status=cut, never deleted, so the history of what we decided not to do survives.
- Distinctive: line 117
Commit with the change code in the message so the history ties together.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/pm-change: absorb the change, keep the docs true
The product will change during design and during implementation. That is the process working, not failing. What breaks a project is absorbing the change into the code while the docs quietly go stale.
Run this the moment the shape of the product changes after its gate was approved.
1. Open the change
./pm add change_request origin=<design|build|feedback|user> \
description="<what changes, in one sentence>"Origin matters. A change that comes from feedback is evidence, a change that comes from implementation is usually a spec bug, and a change that comes from the user mid-design is taste. They are handled the same way but they mean different things over time.
2. Compute the blast radius
Do not guess it. Query it.
./pm tree EPIC001
./pm q "WITH RECURSIVE t(code) AS (SELECT 'EPIC001' UNION ALL
SELECT w.code FROM work_item w JOIN t ON w.parent=t.code)
SELECT w.code,w.level,w.title,w.status,w.doc_path FROM work_item w JOIN t ON w.code=t.code"
./pm q "SELECT code,name,design_status,doc_path FROM screen WHERE item='EPIC001'"
./pm q "SELECT code,title,status,doc_path FROM adr WHERE status='accepted'"
./pm q "SELECT code,title FROM feedback WHERE item='EPIC001'"The recursive query is the point: a change to an epic reaches every story, task and sub-task under it. Walking the tree by hand is how a task gets left pointing at something that no longer exists.
Then read the docs that reference it: the feature PRD, the area TRD, any ADR whose decision assumed the old shape.
Assemble the impact as a list the user can actually check:
- Stories now wrong, newly needed, or no longer worth building
- Epics affected, added, or cut, and any task under them that is now pointless
- Screens whose approval no longer matches the product
- Tasks to reopen, cut, or add
- ADRs that are now wrong and need superseding
- TRD sections that describe something that is no longer true
3. Show it before touching anything
Present the impact, then ask with AskUserQuestion: apply all of it, apply part of it,
or reject the change. Include the cost honestly, especially the screens that lose their
approval. A user who learns after the fact that three approved screens went stale will
stop trusting the system, and then it is dead.
./pm set CR001 impact_json='{"epics":["EPIC001"],"stories":["STORY004"],"screens":["SCR003"],"adrs":["ADR0004"]}'4. Apply
In this order, so nothing is left dangling.
Work tree. Add, cut, or re-scope. A cut item is status=cut, never deleted, so the
history of what we decided not to do survives.
./pm story title="<new outcome>" parent=EPIC001 kind=functional source=CR001
./pm set STORY004 status=cut description="superseded by CR001"A story cannot change level. If a story turns out to be a whole epic, cut it and create the epic, and say so in the change request. Silent re-shaping is how a tree stops matching the product.
Epics. Status, milestone, scope. Update that epic's own doc, and the docs of the stories under it. Do not rewrite the product overview, that is exactly why these are separate files.
Screens. Any approved screen whose behaviour changed goes stale, not silently approved:
./pm set SCR003 design_status=stale./pm check will now fail until that screen is redesigned and reapproved. That is the point.
ADRs. A decision that is now wrong is never edited in place. Write a new one and supersede the old, so the history of why survives.
./pm add adr title="<new decision>" status=accepted supersedes=ADR0004 \
decision="<what>" why="<what changed>" alternatives="<what was reconsidered>" \
doc_path=docs/engineering/adr/0007-<slug>.md
./pm set ADR0004 status=supersededTRD. Edit the affected docs/engineering/trd/<area>.md in place. Area files exist so
this is a small honest edit rather than an intimidating rewrite that gets postponed.
Tasks. Reopen, cut, or add. Cut tasks are set to done only if they were actually
done, otherwise record the cut in the change request.
5. Close
./pm set CR001 status=applied applied_at=<iso date>
./pm checkCommit with the change code in the message so the history ties together.
The rule
A doc that no longer matches the product is worse than no doc, because someone will trust it. If you cannot update the docs in the same pass as the change, say so out loud rather than leaving them wrong.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

