what-if
Skill2 starsChanged 51 days agoMITView on GitHub
Simulate priority changes without modifying real data
6 other projects use a version of this.
Adopted by
Most recently taken up by
- Sach1ng/PM-operating-OStheir own version, first seen Nov 1, 2026
- teachskillofskills-ai/DigitalMarketingPro-techshutheir own version, first seen Oct 11, 2026
- GrannoDev/skillstheir own version, first seen Oct 5, 2026
- pourmirzai/What-Iftheir own version, first seen Oct 2, 2026
- ianklassen/ai-pm-systemtheir own version, first seen Apr 12, 2026
- indranilbanerjee/digital-marketing-protheir own version, first seen Feb 12, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- indranilbanerjee/digital-marketing-pro★ 934same name
- pourmirzai/What-If★ 4same name
- Sach1ng/PM-operating-OS★ 3same name
- ianklassen/ai-pm-system★ 1same name
- GrannoDev/skills★ 0same name
- teachskillofskills-ai/DigitalMarketingPro-techshu★ 0same 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.
In this repository8 other files it gives its agents.
- flow-metricsSkill
- intakeSkill
- plan-sprintSkill
- portfolioSkill
- reprioritizeSkill
- retro-accuracySkill
- sliceSkill
- standupSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 2 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Call simulate with no changes for the current ranking of the open tickets: it is the baseline each scenario is compared with.
- Very specific: line 15
Use ticket_list for the tickets' scores, to name them in scenarios (ticket_list returns 100 tickets per call: page with offset until you …
- Distinctive: line 19
Ask the user: "What scenario do you want to explore?"
- Very specific: line 29
Call simulate with the hypothetical change: changes for new scores of existing tickets, add for new tickets, remove for dropped ones, …
- Very specific: line 30
Don't recalculate priorities yourself: simulate returns the ranks and priorities before and after, and rankChange for every ticket that …
- Distinctive: line 52
After showing results, ask:
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
What-If Scenario Simulation
Explore prioritization scenarios for project $0 without changing real data.
Setup
- Call
simulatewith no changes for the current ranking of the open tickets: it is the baseline each scenario is compared with. Don't take it fromcalc_priority, which ranks done tickets too, whilesimulateranks the open ones (notstate:done) - Use
ticket_listfor the tickets' scores, to name them in scenarios (ticket_listreturns 100 tickets per call: page withoffsetuntil you havetotalof them)
Interactive loop
Ask the user: "What scenario do you want to explore?"
Examples:
- "What if we drop the estimate on ticket X from 8 to 3?"
- "What if the penalty on compliance doubles?"
- "What if we remove ticket Y entirely?"
- "What if we add a new ticket with B=13, P=8, E=5, R=3?"
For each scenario
- Call
simulatewith the hypothetical change:changesfor new scores of existing tickets,addfor new tickets,removefor dropped ones,weightsfor other weights. It writes nothing (do NOT callticket_update). - Don't recalculate priorities yourself:
simulatereturns the ranks and priorities before and after, andrankChangefor every ticket that moved. - For "what would it take for X to reach the top N?", call
explain_prioritywithtitleandtop: it shows the formula and the smallest single score change that gets there.
Output
Ranking diff
| Ticket | Baseline Rank | Scenario Rank | Change | Priority Delta |
Highlight:
- Tickets that moved up or down by 2+ positions
- The ticket(s) directly affected by the scenario
- Any ticket that changed from "in sprint" to "out" or vice versa
Impact summary
- "Reducing estimate on X from 8 to 3 moves it from #7 to #2, displacing Y and Z"
- "Doubling penalty on compliance tickets reshuffles the top 5"
Continue or apply
After showing results, ask:
- "Try another scenario?" → loop back
- "Apply this change for real?" → only then use
ticket_update - "Done" → show final baseline vs. all explored scenarios side by side
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.

