Name: Pre-Mortem Analyst
Author: artyomx33

據 AlphaMoat 統計,截至 2026-09,Pre-Mortem Analyst 累計下載 4,360 次、獲 4 個星標,在全部 5,078 個 AI 技能中排名第 2,246 位,在「商業營運」分類(297 個)中排名第 125 位。

累計安裝

406

累計下載

4360

星標

全站排名

#2,246

全站前 45% · 「商業營運」前 43%

平台	累計安裝	累計下載	星標	評論
ClawHub ↗	138	4062	4	-
SkillHub ↗	406	4360	4	—

各平台的計數口徑不同,統計時間不一致。

這個技能是做什麼的

先發散原因，再按人員、流程、技術和外部因素分類，評估可能性與影響，提出緩解行動及早期預警。失敗情景是分析假設，不是預測。

資料釋出於 2026-10-27

可以用來做什麼

壓力測試上線方案並安排預防優先順序

什麼時候用

上線前需要分析專案可能如何偏離目標時

示例提示詞

以下是根據技能文件生成的示例,不代表實際執行結果。

假設專案已失敗，列出合理原因，按優先順序給出緩解措施和預警訊號。

月度資料趨勢

累計下載4360

星標4

2026-09 起統計方法調整:同名技能按作者分別統計,並覆蓋全部技能。圖中虛線為調整前的月份,與之後的資料不直接比較,也不計算跨越調整的增長。

月份	累計下載	環比	星標
2026-09	4360	—	4
2026-08	3972	+2.3%	4
2026-07	3884	+6.7%	5
2026-06	3641	+3.4%	4
2026-05	3521	—	4
2026-03	3227	—	4

SKILL.md 原文

以下是作者釋出的原始檔案,按純文字顯示,本站未做修改或稽核;其中的連結不可點選,命令請核實後再執行。抓取於 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

展開全部(共 66 行)

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