🎁 Get the FREE AI Skills Starter Guide β€” Subscribe β†’
BytesAgainBytesAgain
BytesAgain β€Ί Skills β€Ί Pre-Mortem Analyst
πŸ¦€ ClawHub

Pre-Mortem Analyst

by @artyomx33

Imagine the project already failed, then work backward to find why. More powerful than risk assessment because it assumes failure is certain. Use when user says "pre-mortem", "premortem", "imagine this failed", "what could go wrong", "risk analysis", "before we launch", "stress test", "what would kill this", "project risks".

Versionv1.0.0
Downloads3,526
Installs19
Stars⭐ 4
#legal
TERMINAL
clawhub install pre-mortem-analyst

πŸ“– About This Skill

name: pre-mortem-analyst description: Imagine the project already failed, then work backward to find why. More powerful than risk assessment because it assumes failure is certain. Use when user says "pre-mortem", "premortem", "imagine this failed", "what could go wrong", "risk analysis", "before we launch", "stress test", "what would kill this", "project risks".

Pre-Mortem Analyst

Why Pre-Mortem > Risk Assessment

Risk Assessment: "What MIGHT go wrong?" β†’ Optimism bias filters answers Pre-Mortem: "It's 6 months later. It FAILED. Why?" β†’ Liberates honest analysis

Research: Pre-mortems increase problem identification by 30%.

The Process

1. Set the scene: "It's [date]. This has failed completely." 2. Brainstorm causes: List 10+ failure reasons (no filtering) 3. Categorize: People, Process, Technology, External 4. Rate: Likelihood Γ— Impact (H/M/L) 5. Prevent: Top 3 get specific mitigation actions 6. Monitor: Define early warning signs

Output Format

PROJECT: [Name]
FAILURE SCENARIO: "It's [date]. [Project] has completely failed."
WHY IT FAILED:
πŸ‘₯ PEOPLE: [Cause] - LΓ—I: H/H | Prevent: [x] | Warning: [y]
βš™οΈ PROCESS: [Cause] - LΓ—I: M/H | Prevent: [x] | Warning: [y]
πŸ’» TECHNOLOGY: [Cause] - LΓ—I: L/H | Prevent: [x] | Warning: [y]
🌍 EXTERNAL: [Cause] - LΓ—I: M/M | Prevent: [x] | Warning: [y]
TOP 3 PRIORITIES:
1. [Risk] β†’ [Specific action]
2. [Risk] β†’ [Specific action]
3. [Risk] β†’ [Specific action]
WARNING SIGNS TO MONITOR:
β–‘ [Early indicator 1]
β–‘ [Early indicator 2]

Common Failure Categories

| Category | Common Causes | |----------|---------------| | People | Key person leaves, skill gaps, misalignment, low buy-in | | Process | Aggressive timeline, scope creep, dependency issues | | Tech | Doesn't scale, integration fails, security breach | | External | Market shift, competitor move, regulation change |

Integration

Compounds with:

  • inversion-strategist β†’ Create systematic avoidance strategies
  • second-order-consequences β†’ Project impact of prevented failures
  • first-principles-decomposer β†’ Question hidden assumptions
  • mspot-generator β†’ Validate MSPOT projects before committing

    • See references/examples.md for Artem-specific pre-mortems