What problem does it solve? Product requirements describe system capabilities, not user paths, so teams ship features where edge cases, failure states, and alternate entry points were never designed. This Skill turns a PRD or brief into a complete interaction pathway — happy path, every branch, and every failure with a named cause and recovery — before any high-fidelity screen work begins. ## Core Features & Use Cases - Artifact decision tree: Chooses between task flow, user flow, and wireflow based on whether the path branches and whether screens exist yet, and routes research-time journey mapping elsewhere. - PRD-to-scenario translation: Converts every requirement sentence into scenarios, branches, and open questions, with a rule that PRD silence becomes a question for the PM rather than an invented assumption. - Eight-probe branch enumeration: Systematically surfaces user decisions, input variance, system failures, state variance, interruptions, concurrency, reversal, and slips vs mistakes at every step. - Use Case: Given a PRD line like "users can book an appointment with a stylist at an available slot," produce a flow spec with the happy path, a branch inventory, a failure-path table (e.g., "that 2:00 slot was just booked" with re-entry to slot selection), and a Mermaid diagram. ## Quick Start Ask the AI to map the end-to-end user flow for your feature from its PRD, including all edge cases and failure paths, and output a flow spec with a Mermaid diagram.
