pre-mortem-analyst
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's 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
More from fimoklei/pm-ai-playbook
first-principles-decomposer
Break any problem down to fundamental truths, then rebuild solutions from atoms up. Use when user says "firstp", "first principles", "from scratch", "what are we assuming", "break this down", "atomic", "fundamental truth", "physics thinking", "Elon method", "bedrock", "ground up", "core problem", "strip away", or challenges assumptions about how things are done.
22idea-challenger
Pre-launch red team analysis that identifies failure modes and validates assumptions before resource commitment. Use when evaluating new products/features/strategies, before significant resource allocation, when stakeholders seem overly optimistic, or when cost of failure would be high (reputation, budget, market position).
21optimize-docs
Condense markdown documentation for token efficiency while preserving all semantic meaning. Use when rules, documentation, or config files need optimization. Target 25-40% reduction through systematic condensation patterns.
20inversion-strategist
Flip problems upside down - instead of "how to succeed", ask "how to definitely fail" then avoid those paths. Use when user says "invert", "inversion", "flip it", "opposite approach", "how would this fail", "avoid failure", "what NOT to do", "Munger", "anti-goals", "guarantee failure".
20security-threat-model
Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats/abuse paths, or perform AppSec threat modeling.
18simplification-cascades
Find one insight that eliminates multiple components - "if this is true, we don't need X, Y, or Z
17