Name: Pre-Mortem Analyst
Author: artyomx33

According to AlphaMoat, as of 2026-09, Pre-Mortem Analyst has 4,360 downloads and 4 stars — ranked #2,246 of 5,078 AI skills overall, and #125 of 297 in Business Ops.

Installs

406

Downloads

4.4K

Stars

Overall Rank

#2,246

Top 45% overall · Top 43% in Business Ops

Platform	Installs	Downloads	Stars	Comments
ClawHub ↗	138	4.1K	4	-
SkillHub ↗	406	4.4K	4	—

Platforms count differently and update at different times.

What this skill does

It brainstorms causes, groups them into people, process, technology and external factors, rates likelihood and impact, and proposes mitigation and early-warning indicators. The failure scenario is an analytical assumption, not a prediction.

Profile published 2026-10-27

What you can do with it

Stress-test a launch plan and prioritize preventive actions

When to use it

When examining what could derail a project before launch

Example prompts

Generated from the skill’s documentation as examples; not results of actual runs.

Assume this project has failed, identify plausible causes and prioritize mitigations with warning signs.

Monthly Trend

Downloads4.4K

Stars4

The counting method changed in 2026-09: skills with the same name are now counted separately by author, and the full catalog is covered. Dashed lines show months before the change; they are not compared with later months, and no growth is computed across the change.

Month	Downloads	MoM	Stars
2026-09	4.4K	—	4
2026-08	4.0K	+2.3%	4
2026-07	3.9K	+6.7%	5
2026-06	3.6K	+3.4%	4
2026-05	3.5K	—	4
2026-03	3.2K	—	4

SKILL.md (original)

The author’s original file, shown as plain text without edits or review by AlphaMoat. Links are not clickable; check commands before running them. Fetched 2026-10-23.

2.3 KB · ClawHub v1.0.0

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

Show all (66 lines)

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