What problem does it solve? Most Risks sections in PRDs and roadmaps are generic worry lists ("technical complexity", "timeline risk") that no team can plan against. This Skill turns vague unease into decision-useful risks by enforcing a three-part structure: a concrete scenario, an observable early indicator, and a pre-decided response. ## Core Features & Use Cases - Three-part risk template: Every risk names the specific failure scenario, the early signal that it is starting, and the planned response with rough cost and timing. - Premortem procedure: A four-step method (assume failure, enumerate causes independently, convert causes to three-part risks, rank by likelihood and impact) for generating risks that optimism hides. - Risk vs. assumption routing: Distinguishes known risks from untested assumptions, routing the latter to assumption testing instead of writing speculative responses. - Use Case: When writing a PRD for a bulk-import feature, run a premortem to surface that users may abandon after one bad import, then record the indicator (first-import error rate) and response (add a dry-run preview) in the Risks section. ## Quick Start Ask the AI to write the Risks section of your PRD using the scenario, indicator, and response format, or to run a premortem on a committed roadmap bet.
