agentleFS
Sign inStart free
neurofooneurofoo/agent-skills/premortem/SKILL.md

premortem

Skill111 starsChanged 10 months agoMITView on GitHub

Pre-mortem analysis that imagines a plan has failed, then works backward to identify causes and preventions. Use before launches, major decisions, or risky initiatives to surface hidden risks.

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 29 edited versions we read keep these.

  • 3

    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
  1. Distinctive:

    After this analysis, how confident are you in success?

    line 56
  2. Distinctive:

    Don't filter for "that won't happen"—the point is to surface hidden concerns

    line 62
  3. Distinctive:

    Look for single points of failure

    line 64

“Common” is measured: kept by at least 6 in 10 of the 29 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Pre-Mortem Analysis

Imagine the plan has completely failed, then work backward to identify what went wrong and how to prevent it.

Instructions

Set the scene: "It's [timeframe] in the future. This initiative was a complete disaster. Looking back, what happened?"

Generate failure scenarios without filtering for likelihood—get everything on the table first, then prioritize.

Output Format

The Plan Summarize what's being attempted and the success criteria.

Time Jump "It's [X months] later. This has failed completely. The outcome: [describe the disaster vividly]."

What Went Wrong

Generate 8-12 plausible failure causes across categories:

CategoryFailure ModeHow It Played Out
Execution[What failed][The story of how]
External[What failed][The story of how]
People[What failed][The story of how]
Technical[What failed][The story of how]
Assumptions[What failed][The story of how]

Risk Prioritization

Failure ModeLikelihoodImpactPriority
...High/Med/LowHigh/Med/Low1-5

Top 3 Risks & Mitigations

For each top risk:

  • Risk: [Description]
  • Early Warning Signs: What would indicate this is happening?
  • Prevention: How to reduce likelihood
  • Mitigation: How to reduce impact if it occurs
  • Owner: Who's responsible for watching this?

Pre-Mortem Insights What did this exercise reveal that wasn't obvious before?

Revised Confidence After this analysis, how confident are you in success? What would increase confidence?

Guidelines

  • Be vivid and specific—"the database corrupted" not "something went wrong"
  • Include uncomfortable possibilities (key person leaves, competitor moves, we were wrong)
  • Don't filter for "that won't happen"—the point is to surface hidden concerns
  • Assign real owners to mitigations
  • Look for single points of failure

$ARGUMENTS

Download now (ZIP)

  • Other versions39 projects use a version of this.

    Word for word · 7

    1. MaxMiksa/Auto-Company★ 3.2k100% same
    2. MaxMiksa/Autonomous-Company★ 3.2k100% same
    3. nicepkg/auto-company★ 188100% same
    4. NikitaDmitrieff/auto-co-meta★ 43100% same
    5. Hassaan146/claude-skills★ 18100% same
    6. DrifterXXX/auto-company★ 0100% same
    7. vansvost-arch/claude-skills★ 0100% same

    Edited · 0

    None found.

    Wrote their own version · 32

    1. parcadei/Continuous-Claude★ 3.9ksame name
    2. parcadei/Continuous-Claude-v2★ 3.9ksame name
    3. parcadei/Continuous-Claude-v3★ 3.9ksame name
    4. boshu2/agentops★ 452same name
    5. entropyvortex/meta-llm-charter★ 248same name
    6. joetawil7/first-pass★ 128same name
    7. songjiun10-collab/Senior-thinking-skills★ 87same name
    8. griffinhilly/claude-code-synthesis★ 67same name
    9. AndyShaman/premortem★ 56same name
    10. MADEVAL/Pre-Mortem-Skill★ 48same name

    22 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.

  • Used alongsideProjects 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.
    • nicepkgSkill

      community-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

    • nicepkgSkill

      ph-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

    • xfstudioSkill

      micro-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

    • mastepanoskiSkill

      ux-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

    • ncklrsSkill

      seo-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

    • parcadeiSkill

      agent-context-isolation

      Agent Context Isolation

      Also in 3 projects that use this

    • +6 more from nicepkg
  • In this repository22 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

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.

Check your setup, free