What problem does it solve? Positive requirement analysis often overlooks what happens when users make mistakes, abandon flows midway, or encounter abnormal system states, leaving products fragile in real-world usage. This Skill systematically derives negative scenarios from confirmed positive requirements and designs concrete program behaviors for each one. ## Core Features & Use Cases - Negative Scenario Derivation: Analyzes seven scenario categories including user misoperation, parameter input errors, mid-flow abandonment, state anomalies, permission issues, data anomalies, and external dependency failures. - Risk Assessment and Prioritization: Scores each scenario by probability and impact, assigning P0-P3 priority levels so teams know what must be handled first. - Strategy Design with Structured Output: Produces prevention, detection, recovery, guidance, and fault-tolerance strategies plus UX copy for each scenario, delivered as a structured negative requirement report linked back to positive requirements. - Use Case: After requirement mining for a checkout flow, run this Skill to uncover scenarios like payment timeout, duplicate submission, and session expiry, each with defined program behavior and user-facing prompts. ## Quick Start Analyze the negative scenarios for my confirmed requirement list and design the detection, recovery, and user guidance strategies for each one.
