reversibility-check
Skill0 starsChanged 4 months agoMITView on GitHub
Decide how much to deliberate by whether the decision can be undone — move fast on reversible calls, slow down on the one-way doors. Any decision where you're unsure how much time it deserves. The check tells you whether to just decide or to slow down.
In this repository29 other files it gives its agents.
- devils-advocate-first-passSkill
- load-bearing-assumptionSkill
- pre-mortemSkill
- three-option-framingSkill
- boundary-setting-declineSkill
- cold-intro-structureSkill
- customer-reply-tone-matchSkill
- quote-follow-upSkill
- subject-line-not-filteredSkill
- end-of-day-reflectionSkill
- inbox-triageSkill
- project-scaffoldingSkill
- quote-drafting-from-notesSkill
- vendor-invoice-categorizationSkill
- competitor-pricing-extractSkill
- customer-voice-extractSkill
- source-verificationSkill
- tactic-extractionSkill
- vertical-landscape-scanSkill
- discovery-call-note-captureSkill
- lead-qualificationSkill
- objection-handlingSkill
- proposal-drafting-frameworkSkill
- stack-the-deck-closeSkill
- dont-be-a-chatbotSkill
- honest-hedgingSkill
- lead-with-the-actionSkill
- specific-over-genericSkill
- write-like-the-userSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Not every decision deserves the same care.
- Distinctive: line 20
Ask: if this is wrong, how hard is it to reverse?
- Distinctive: line 23
Don't treat every decision as permanent.
- Distinctive: line 24
Don't treat a permanent one as casual either.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Check Whether It's Reversible
Not every decision deserves the same care. Ask whether you can undo it cheaply. If yes, decide fast and move. If no — a one-way door — slow down, because the cost of being wrong is permanent.
The technique
- Ask: if this is wrong, how hard is it to reverse? Cheap-to-undo and costly-to-undo are different decisions.
- Reversible calls: decide fast, with less information. Over-deliberating a thing you can take back is its own kind of waste.
- One-way doors — a fire, a contract you can't exit, money you can't get back, a public move: slow down and gather more before committing.
- Don't treat every decision as permanent. Most aren't, and acting like they are grinds the business to a halt.
- Don't treat a permanent one as casual either. The whole skill is matching the deliberation to the reversibility.
Do this, not that
Do: "Switching email tools? Reversible — try it, switch back if it's worse, decide in an afternoon. Signing the two-year lease on the second location? One-way door — that one gets the slow, careful look."
Don't: Spend two weeks agonizing over which $20 software to use (reversible, just pick one) while signing a major lease on a gut feeling because it felt exciting in the moment (irreversible, deserved the agonizing).
Why this works
People burn their deliberation budget backwards — they over-think the small reversible stuff and under-think the big permanent stuff, because urgency and stakes don't line up with reversibility. Sorting by whether a decision can be undone fixes that: fast on the two-way doors, slow on the one-way doors. It's the single best filter for how much a decision is worth worrying about.
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.

