Skip to content
Skills Library
Management & product · Analysis

pre-mortem

/pre-mortem

Runs a pre-mortem that sorts launch risks into evidenced tigers, paper tigers and unspoken elephants, each with an owner. Use when a big launch, build or migration is coming, or the team has a bad feeling it cannot name.

Licence
MIT
Last repository change
08.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
9
Scripts
1
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 08.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 1 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/risk_categorizer.py

What it does and when to use it

Runs a pre-mortem that sorts launch risks into evidenced tigers, paper tigers and unspoken elephants, each with an owner. Use when a big launch, build or migration is coming, or the team has a bad feeling it cannot name.

Original author description

Runs a pre-mortem that sorts launch risks into evidenced tigers, paper tigers and unspoken elephants, each with an owner. Use when a big launch, build or migration is coming, or the team has a bad feeling it cannot name.

How it works

  1. Overview
  2. Core Capabilities
  3. When to Use
  4. Clarify First
  5. Workflow
  6. Anti-Patterns
  7. References
  8. Scope & Limitations
  9. Files
Original SKILL.md headings · 91 lines, 998 words
SKILL.md preview
---
name: pre-mortem
description: >
  Runs a pre-mortem that sorts launch risks into evidenced tigers, paper tigers and
  unspoken elephants, each with an owner. Use when a big launch, build or migration is
  coming, or the team has a bad feeling it cannot name.
license: MIT + Commons Clause
metadata:
  version: 1.0.1
  author: borghei
  category: project-management
  domain: product-discovery
  updated: 2026-11-08
  python-tools: risk_categorizer.py
  tech-stack: pre-mortem, risk-analysis, gary-klein, prospective-hindsight
  tags:
    - pre-mortem
    - risk-analysis
    - launch-readiness
    - discovery
---
# Pre-Mortem Risk Analysis Expert

## Overview

A pre-mortem is a prospective hindsight exercise: imagine that your product has launched and failed, then work backward to identify why. This skill uses the Tiger / Paper Tiger / Elephant classification to categorize risks by type and urgency, ensuring launch-blocking issues are addressed before launch while avoiding wasted effort on unlikely risks.

## Core Capabilities

- **Prospective hindsight framing** — "It is 14 days after launch, and we failed. Why?" surfaces specific, honest risks.
- **Tiger / Paper Tiger / Elephant classification** — separate real evidenced risks (Tigers) from anxiety (Paper Tigers) and unspoken concerns (Elephants).
- **Urgency triage** — tag each Tiger Launch-Blocking, Fast-Follow, or Track with owner and decision date.
- **6-phase facilitation** — scene-setting, silent generation, cluster, classify, mitigate, address elephants in 60-90 minutes.
- **Automated categorization** — `risk_categorizer.py` summarizes distribution and flags elephants needing escalation.

## When to Use

- Before committing significant resources to build (post-ideation, post-validation).
- Before a major launch, migration, or architectural change.
- When the team has "a bad feeling" they cannot articulate.
- When stakeholder confidence is high and you need to stress-test it.

## Clarify First

Before running the pre-mortem, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.

- **The thing being stress-tested:** the specific launch/build/migration that "failed 14 days after launch" (anchors the prospective-hindsight framing).
- **Failure horizon:** the date/milestone you imagine looking back from (a vague horizon produces vague risks).
- **Who's in the room:** the 4-8 participants and whether psychological safety exists (elephants only surface with candor and the right people).

Ask about the two or three inputs that matter most for this request, not the whole list. If the user wants a result straight away, produce it and state your assumptions at the top.

## Workflow

1. Settle the Clarify First inputs and run the session from `references/methodology-and-tools.md` (scene-setting, silent generation, cluster, classify, mitigate, elephants).
2. Record each risk with `description`, `category` (`tiger`/`paper_tiger`/`elephant`) and `evidence`; tigers also need `urgency` (`launch_blocking`/`fast_follow`/`track`), and launch-blockers an `owner` and `decision_date`.
3. Run `risk_categorizer.py` and fix its findings before the session closes.
4. Done when the tool exits 0, every launch-blocker has an owner and a decision date, and each elephant has a person who will raise it.

```bash
python3 project-management/discovery/pre-mortem/scripts/risk_categorizer.py project-management/discovery/pre-mortem/assets/sample_risks.json          # exit 0
python3 project-management/discovery/pre-mortem/scripts/risk_categorizer.py project-management/discovery/pre-mortem/assets/sample_risks_flawed.json   # exit 1
python3 project-management/discovery/pre-mortem/scripts/risk_categorizer.py --demo --format json
```

The tool groups risks by category and urgency, flags elephants whose text carries escalation signals (no owner, blocked, security, compliance, legal and similar), and reports two findings a rushed session skips: a launch-blocking tiger with no `owner` or `decision_date`, and a tiger whose evidence is speculative ("might", "could", "we think"), which makes it a paper tiger until shown otherwise. Exit codes: 0 no findings, 1 findings, 2 bad input (missing file, invalid JSON, missing fields). Document the session with `assets/pre_mortem_template.md`.

## Anti-Patterns

### Mitigating Paper Tigers
**Mistake:** "AWS regional outage on launch day" is classed as a Tiger and gets weeks of redundancy work, with no evidence that it is likely.
**Why it happens:** A frightening consequence feels like a high probability.
**Instead:** For every Tiger, write the `evidence` that it could actually happen. A described consequence alone does not count. With no evidence, reclassify it as `paper_tiger` and cover it with a standard runbook.

### Risks too vague to act on
**Mistake:** The list holds "stakeholder issues", "scope creep" and "technical risk".
**Why it happens:** Generic labels are safe to say aloud and need no evidence.
**Instead:** Describe each risk as a concrete failure scenario in 1-2 sentences, such as "the CRO blocks launch on Day -7 because the enterprise SKU was cut". Translate worries ("the design feels weak") into a measurable consequence, or drop them.

### Running the pre-mortem too late
**Mistake:** The session happens a week before launch and surfaces a Tiger that needs four weeks of work. The team launches anyway.
**Why it happens:** Pre-mortems get scheduled as a launch-readiness check instead of a planning step.
**Instead:** Run the first pre-mortem at project kickoff and a second one around Day -30. For each risk, confirm it can still be mitigated in the time left.

Nine more, each with a bad and a good example: `references/red-flags.md`.

## References

Load the reference that matches the task — keep this file lean and pull detail on demand:

- **[references/methodology-and-tools.md](references/methodology-and-tools.md)** — the thought experiment, full Tiger/Paper Tiger/Elephant classification with examples, urgency table, the 6-phase facilitation script, `risk_categorizer.py` usage and flags, output formats, troubleshooting, success criteria, and bibliography. Read when running or scripting a session.
- **[references/pre-mortem-guide.md](references/pre-mortem-guide.md)** — Gary Klein's origin and why pre-mortems work, when (and when not) to run one, deep classification criteria across domains, the facilitation timeline, and a worked SaaS launch example. Read for the theory and a full example.
- **[references/red-flags.md](references/red-flags.md)** — 12 anti-patterns (mitigation theater, groupthink, vague risks, over-mitigated elephants, late pre-mortems, missing owners) with bad/good examples and one-line checks. Read before sharing pre-mortem output.

## Scope & Limitations

**In Scope:** prospective hindsight using the "14 days after launch failure" framing; Tiger / Paper Tiger / Elephant classification with urgency levels; automated elephant escalation detection; risk registry generation; facilitation methodology for in-person and remote teams.

**Out of Scope:** ongoing risk management and tracking (see `senior-pm/scripts/risk_matrix_analyzer.py`); quantitative probability/impact scoring (`senior-pm/`); product discovery and hypothesis validation (`brainstorm-experiments/`); technical architecture risk assessment (`engineering/` skills).

**Important Caveats:** most effective with 4-8 participants; the elephant escalation keyword check is a heuristic; pre-mortems complement, not replace, assumption mapping (`identify-assumptions/`); psychological safety is a prerequisite.

## Files

| File | Purpose |
|------|---------|
| `scripts/risk_categorizer.py` | Categorizes risks, flags elephants to escalate, gates on unowned launch-blockers and speculative tigers |
| `assets/sample_risks.json`, `assets/sample_risks_flawed.json` | Runnable inputs: sound (exit 0) and flawed (exit 1) |
| `assets/pre_mortem_template.md` | Session template |
| `examples/shared-dashboards-v1-pre-mortem.md` | Worked session |
| `references/*.md` | See References |
Files in this package (9)
  • SKILL.md 8 KB
  • assets/pre_mortem_template.md 3 KB
  • assets/sample_risks.json 2 KB
  • assets/sample_risks_flawed.json 2 KB
  • examples/shared-dashboards-v1-pre-mortem.md 18 KB
  • references/methodology-and-tools.md 10 KB
  • references/pre-mortem-guide.md 10 KB
  • references/red-flags.md 13 KB
  • scripts/risk_categorizer.py 15 KB

Versions

RepositoryScoreLicence
This page · borghei/Claude-Skills100MIT
rjmurillo/ai-agents100MIT
rjmurillo/ai-agents100MIT
ysskrishna/ai-agent-skills100MIT
fzfclee/consulting-skills100Apache-2.0
Sidsaladi9/persona-os100MIT
tarunccet/pm-skills100MIT
kaminoikari/product-playbook100MIT
phuryn/pm-skills95MIT

Database snapshot: 13.11.2026 · package version 028f0cee8658 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100aped-pre-mortem
    Use when user says "pre-mortem", "what could go wrong", "risk analysis", "failure modes", "anticipate problems", or invokes aped-pre-mortem. Structured pre-mortem before implementation starts. Not for post-incident (see aped-retro).
  • 100premortem
    Use for pre-mortem analysis of decisions, projects, or initiatives—solo or facilitated with a team before a launch or strategic commitment. Trigger when the user says "what could go wrong", "risk assessment", "pre-mortem this", "let's run a pre-mortem", or when evaluating risks…
  • 100sealmap-review
    Reviews a whole project or system from its diagrams-as-code corpus: risks, technical due diligence, a pre-mortem, or an outside opinion before running, shipping or taking it over. External mode sends the diagrams only, never code, to Gemini 3.8 Flash under critical and…
  • 90decision-architect
    Structures a hard decision with options, criteria, weighted scoring, reversibility and pre-mortem, then makes a recommendation. Use when the user is stuck between choices, says 'should I X or Y', or needs a decision memo.
  • 90arn-spark-stress-premortem
    This skill should be used when the user says "pre-mortem", "premortem", "risk analysis", "stress premortem", "failure analysis", "what could go wrong", "pre mortem", "investigate failure", "failure modes", or wants to stress-test a product concept by applying Gary Klein's…
  • 100autopilot-plan
    Adversarial planning before a Linear project exists. Takes the user's plan and expectations, refuses to continue without measurable KPIs, drafts the full plan, sends it to a pre-mortem by one Tier 1 model of another vendor ("we are at the deadline and we failed, why?"), shows…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.