premortem
Skill2 starsChanged yesterdayMITView on GitHub
Before significant work, assume it has already failed, write the most likely reasons as specific stories, and turn the top risks into checks built into the plan. Use before anything multi-step, expensive, irreversible or shipped to others (a migration, launch, big refactor, long document, research project), or when the user says "premortem", "what could go wrong" or "before we start".
44 other projects use a version of this.
Adopted by
Most recently taken up by
- keny4nn/claude-skillstheir own version, first seen Nov 16, 2026
- ronniepinnell/caspertheir own version, first seen Nov 8, 2026
- Adelie-Squad/solosquadtheir own version, first seen Nov 8, 2026
- whyashthakker/estacktheir own version, first seen Nov 8, 2026
- gustaferiksson/skillstheir own version, first seen Nov 7, 2026
- Rafaelrr5/agent-cortextheir own version, first seen Nov 1, 2026
Used with
Projects with it also use community-led-growth, ph-community-outreach 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.
nicepkgSkillcommunity-led-growth
Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.
Also in 5 projects that use this
nicepkgSkillph-community-outreach
Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.
Also in 5 projects that use this
xfstudioSkillmicro-saas-launcher
Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp.
Also in 5 projects that use this
mastepanoskiSkillux-audit-rethink
Comprehensive UX audit using IxDF's 7 factors, 5 usability characteristics, and 5 interaction dimensions. Holistic evaluation with redesign proposals based on user-centered design principles.
Also in 5 projects that use this
ncklrsSkillseo-content-strategist
Expert SEO content strategy for SaaS and B2B sites. Use when doing keyword research, planning content clusters, creating pillar pages, optimizing on-page SEO, fixing technical SEO issues, building links, refreshing content, implementing programmatic SEO, mapping search intent, optimizing for SERP features, or measuring content performance. Use for SEO audits, content gap analysis, and organic growth strategy.
Also in 5 projects that use this
parcadeiSkillagent-context-isolation
Agent Context Isolation
Also in 3 projects that use this
- +6 more from nicepkg
Other versions44 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 44
- parcadei/Continuous-Claude★ 3.9ksame name
- parcadei/Continuous-Claude-v2★ 3.9ksame name
- parcadei/Continuous-Claude-v3★ 3.9ksame name
- MaxMiksa/Auto-Company★ 3.2ksame name
- MaxMiksa/Autonomous-Company★ 3.2ksame name
- boshu2/agentops★ 454same name
- entropyvortex/meta-llm-charter★ 247same name
- nicepkg/auto-company★ 188same name
- joetawil7/first-pass★ 128same name
- neurofoo/agent-skills★ 111same name
34 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 repository17 other files it gives its agents.
- autopilotSkill
- autopsySkill
- confidence-mapSkill
- delegateSkill
- expert-askSkill
- failure-museumSkill
- ghost-usersSkill
- grill-dumpSkill
- intent-diffSkill
- md-to-mapSkill
- mind-mapSkill
- red-teamSkill
- shipitSkill
- stuck-detectorSkill
- taste-thiefSkill
- tournamentSkill
- workSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 39 edited versions we read keep these.
5
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 18
Write from the future, in the past tense, as a specific failure: "It is three weeks later.
- Distinctive: line 19
Every story is specific to THIS work.
- Distinctive: line 29
Write 5-7 failure stories, one line each.
- Distinctive: line 31
Write a tripwire for each.
- Distinctive: line 34
Start. When a tripwire's step arrives, check it and say so in one line ("Tripwire 2 checked: clear").
“Common” is measured: kept by at least 6 in 10 of the 39 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
Premortem
Risk lists come out generic; failure stories do not. Write the failure as history, then build the plan to prevent it.
Scale
- Skip for tasks under about 30 minutes or easily undone.
- Light: one sentence "most likely way this fails: ..." plus one tripwire.
- Full: the process below.
Hard rules
- Write from the future, in the past tense, as a specific failure: "It is three weeks later. The migration was rolled back because..."
- Every story is specific to THIS work. If it could be pasted into another project's premortem unchanged, delete it.
- Cover at least four of these sources: wrong problem (built the wrong thing), false assumption, dependency or integration, execution (order, time, skill), reception (user, reader or reviewer rejects it), irreversibility (could not undo).
- Rate each story likelihood x damage as H/M/L and keep the top 3.
- Each top risk becomes a tripwire in the plan: an observable signal, the step at which it is checked, and the action if it fires. "Be careful with X" is not a check.
- The riskiest unverified assumption gets the cheapest possible test, and that test becomes step 1 of the plan.
- Cap: at most 7 stories and 3 tripwires, then start the work.
Process
- State the work and what success looks like, in one line. If no plan exists, sketch it in one line of steps first.
- Write 5-7 failure stories, one line each.
- Rate them and pick the top 3. Mark them in the Top 3 column.
- Write a tripwire for each.
- Find the riskiest assumption and its cheapest test.
- Insert the test and the tripwires into the plan at named steps. Cheap fixes for lower-ranked risks go in as plain steps, with no tripwire.
- Start. When a tripwire's step arrives, check it and say so in one line ("Tripwire 2 checked: clear").
Output format
PREMORTEM: <work> fails if...
It is <when>. <the failure, in the past tense>
| # | Failure story | L | D | Top 3 |
|---|---------------|---|---|-------|
| 1 | <what happened> because <cause>. | H | H | yes |
Tripwires:
1. story #<n> · <signal> · checked at <step> · if it fires: <action>
First: <cheapest test of the riskiest assumption>Anti-patterns
- Generic risks ("scope creep", "bugs", "time").
- Risks with no check, or checks with no place in the plan.
- A premortem that is never looked at again.
- Fifteen risks.
- Tripwire signals nobody can observe ("if it feels risky").
- Stories of pure bad luck with no cause to act on.
- Using it to argue against doing the work at all.
- Running it after the work: attacking finished work is
red-team, and the after-the-fact review isautopsy.
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.

