swing-mortemlisted

# Pre-Mortem Prospective failure analysis that defeats optimism bias by assuming failure first, then working backward to surface risks, early warnings, and escape hatches. **Based on Gary Klein's swing-mortem technique:** Instead of asking "will this work?" (which triggers optimism bias), this skill forces the question: "It's 6 months from now and this has completely failed. What went wrong?" **Key distinction from swing-review:** - `swing-review` examines the **CURRENT** state — "what's wrong NOW?" - `swing-mortem` examines the **FUTURE** — "what will go wrong LATER?" - Adversarial review finds existing flaws. Pre-mortem anticipates flaws that don't exist yet. ## Rules (Absolute) 1. **Never produce generic risks.** Every failure scenario must name specific technologies, quantities, timelines, or conditions. "The database might not scale" is banned. "PostgreSQL connection pool exhaustion at >2,000 concurrent users due to long-running analytical queries holding connections for 30s+" is acceptable. 2. **Exactly 5 scenarios across 5 categories.** One Technical, one Organizational, one External, one Temporal, one Assumption. No category may be skipped, no category may have more than one scenario. 3. **Leading indicators must be observable and measurable.** "Watch out for problems" is banned. Every indicator must specify what to measure, what threshold signals danger, and where to observe it. 4. **Circuit breakers must include a specific trigger condition.** "If things go wr