217★by artyomx33
pre-mortem-analyst – OpenClaw Skill
pre-mortem-analyst is an OpenClaw Skills integration for coding workflows. 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".
Skill Snapshot
| 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". OpenClaw Skills integration. |
| owner | artyomx33 |
| repository | artyomx33/pre-mortem-analyst |
| language | Markdown |
| license | MIT |
| topics | |
| security | L1 |
| install | openclaw add @artyomx33/pre-mortem-analyst |
| last updated | Feb 7, 2026 |
Maintainer

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
- Set the scene: "It's [date]. This has failed completely."
- Brainstorm causes: List 10+ failure reasons (no filtering)
- Categorize: People, Process, Technology, External
- Rate: Likelihood × Impact (H/M/L)
- Prevent: Top 3 get specific mitigation actions
- 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
No README available.
Permissions & Security
Security level L1: Low-risk skills with minimal permissions. Review inputs and outputs before running in production.
Requirements
- OpenClaw CLI installed and configured.
- Language: Markdown
- License: MIT
- Topics:
FAQ
How do I install pre-mortem-analyst?
Run openclaw add @artyomx33/pre-mortem-analyst in your terminal. This installs pre-mortem-analyst into your OpenClaw Skills catalog.
Does this skill run locally or in the cloud?
OpenClaw Skills execute locally by default. Review the SKILL.md and permissions before running any skill.
Where can I verify the source code?
The source repository is available at https://github.com/openclaw/skills/tree/main/skills/artyomx33/pre-mortem-analyst. Review commits and README documentation before installing.
