premortemlisted

# Pre-Mortem Identify failure modes before they occur by systematically questioning plans, designs, and implementations. Based on Gary Klein's technique, popularized by Shreyas Doshi (Stripe). ## Usage ``` /premortem # Auto-detect context, choose depth /premortem quick # Force quick analysis (plans, PRs) /premortem deep # Force deep analysis (before implementation) /premortem <file> # Analyze specific plan or code ``` ## Core Concept > "Imagine it's 3 months from now and this project has failed spectacularly. Why did it fail?" ## Risk Categories (Shreyas Framework) | Category | Symbol | Meaning | |----------|--------|---------| | **Tiger** | `[TIGER]` | Clear threat that will hurt us if not addressed | | **Paper Tiger** | `[PAPER]` | Looks threatening but probably fine | | **Elephant** | `[ELEPHANT]` | Thing nobody wants to talk about | ## CRITICAL: Verify Before Flagging **Do NOT flag risks based on pattern-matching alone.** Every potential tiger MUST go through verification. ### The False Positive Problem Common mistakes that create false tigers: - Seeing a hardcoded path without checking for `if exists():` fallback - Finding missing feature X without asking "is X in scope?" - Flagging code at line N without reading lines N±20 for context - Assuming error case isn't handled without tracing the code ### Verification Checklist (REQUIRED) Before flagging ANY tiger, verify: ```yaml potential_finding: what: "Hardcoded path at lin