agentleFS
cwhited26cwhited26/pocket-agent-starter-skills/skills/decisions/pre-mortem/SKILL.md

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

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.
  • skytiger6724Skill

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

  • skytiger6724Skill

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

  • 45ckSkill

    pestle-analysis

    Also in 7 projects that use this

  • About-IntelligenceSkill

    positioning-ideas

    Brainstorm product positioning ideas differentiated from competitors.

    Also in 7 projects that use this

  • About-IntelligenceSkill

    product-name

    Brainstorm 5 unique, memorable product names with rationale aligned to brand values and target audience.

    Also in 6 projects that use this

  • nandanosqlSkill

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

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

    Write the story of how it failed.

    line 21
  2. Distinctive:

    Keep the list. When something starts going sideways later, you've already named it and can act fast.

    line 24

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

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

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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.