pre-mortem
Skill0 starsChanged 4 months agoMITView on GitHub
Before committing, assume the plan already failed and write down why — so you fix the likely failures before they happen. Before launching something real — a service, a campaign, a big spend. When the plan feels solid and that confidence needs a stress test.
30 other projects use a version of this.
Adopted by
Most recently taken up by
- rahul-kulkarni105/skillstheir own version, first seen Nov 8, 2026
- yuusakuri/agent-skillstheir own version, first seen Nov 1, 2026
- Big-LAORE/Biblioth-que-de-skillstheir own version, first seen Nov 1, 2026
- daviszhen/agent-skillstheir own version, first seen Oct 25, 2026
- takayoshitoyoda05/claude-ml-templatetheir own version, first seen Oct 20, 2026
- phant0um/claude-skillstheir own version, first seen Oct 15, 2026
Used with
Projects with it also use brainstorm-experiments-existing, prioritize-assumptions and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
skytiger6724Skillbrainstorm-experiments-existing
Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
Also in 7 projects that use this
skytiger6724Skillprioritize-assumptions
Prioritize assumptions using an Impact × Risk matrix and suggest experiments for each. Use when triaging a list of assumptions, deciding what to test first, or applying the assumption prioritization canvas.
Also in 7 projects that use this
45ckSkillpestle-analysis
Also in 7 projects that use this
About-IntelligenceSkillpositioning-ideas
Brainstorm product positioning ideas differentiated from competitors.
Also in 7 projects that use this
About-IntelligenceSkillproduct-name
Brainstorm 5 unique, memorable product names with rationale aligned to brand values and target audience.
Also in 6 projects that use this
nandanosqlSkillswot-analysis
Conduct a structured SWOT analysis — Strengths, Weaknesses, Opportunities, Threats — that connects internal capabilities to external forces for strategic decision-making.
Also in 9 projects that use this
- +5 more from skytiger6724
- +1 more from About-Intelligence
Other versions30 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 30
- avelikiy/great_cto★ 112same name
- ysskrishna/ai-agent-skills★ 20same name
- MbappeWU/murder-board★ 15same name
- jackjin1997/ClawForge★ 12same name
- sergeeey/Claude-cod-top-2026★ 9same name
- carlkibler/agent-skills★ 6same name
- fzfclee/consulting-skills★ 6same name
- broomva/skills★ 4same name
- Adhamxon/claude-code-skills★ 2same name
- skytiger6724/qwen-skills★ 2same name
20 more not listed
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 repository29 other files it gives its agents.
- devils-advocate-first-passSkill
- load-bearing-assumptionSkill
- reversibility-checkSkill
- 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
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 23 edited versions we read keep these.
2
Distinctive
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 21
Write the story of how it failed.
- Distinctive: line 24
Keep the list. When something starts going sideways later, you've already named it and can act fast.
“Common” is measured: kept by at least 6 in 10 of the 23 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
Run a Pre-Mortem
A pre-mortem is a post-mortem you run before the failure. Assume the plan has already failed, six months out, then write the story of how — and use that story to fix the weak points now.
The technique
- Imagine it's six months later and this clearly failed. Don't ask if — assume it did.
- Write the story of how it failed. The specific causes, not "it didn't work": the demand wasn't there, the crew burned out, the price was wrong, a competitor moved first.
- Rank the failure modes by likelihood and damage — which of these stories is most plausible and most costly.
- Fix the top one or two now, while it's cheap. A pre-mortem that doesn't change the plan was just theater.
- Keep the list. When something starts going sideways later, you've already named it and can act fast.
Do this, not that
Do: "Pre-mortem on the maintenance plan: it failed because (1) only 5 of 40 customers signed up — demand was thin; (2) the recurring work ate crew time we needed for storm jobs; (3) churn after month two because the value wasn't visible. Fix now: test demand with 10 calls first, cap enrollment to protect crew capacity, build in a monthly 'here's what we did' touch."
Don't: Launch on pure optimism — "this is going to be great" — and run the actual post-mortem in six months after the avoidable failures have already cost real money.
Why this works
Confidence makes you blind to a plan's weak points right when you most need to see them. A pre-mortem gets around that by giving everyone permission to imagine failure — it's easier to spot what could go wrong when you start from "it did" instead of defending "it will work." The failures you name in advance are the ones you can still prevent cheaply; the ones you don't name, you pay for later at full price.
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.

