user-flow-analysislisted

# User Flow Analysis Analyze the flow: **$ARGUMENTS** (user persona defaults to general user) ## Steps 1. **Map the current flow** — Read the route structure and component hierarchy to reconstruct the user journey: - Entry point (how does the user arrive?) - Each step/screen in sequence - Decision points (branching paths) - Exit points (success, abandon, error) 2. **Count friction points per step**: - Form fields to fill - Decisions to make - Clicks required - External dependencies (email verification, payment provider) - Waiting time (loading, processing) 3. **Identify drop-off risks**: - Steps with too many required fields - Unclear calls to action - Missing progress indicators - Points where users might get confused about what to do next - Forced account creation before value delivery 4. **Analyze happy path efficiency**: - What's the minimum number of steps to complete the flow? - Are there unnecessary steps that could be deferred or removed? - Can steps be combined without overwhelming the user? - Is the default path the most common use case? 5. **Check error recovery**: - What happens when a step fails? - Can users resume after a failure, or do they restart? - Are error messages actionable? - Is form data preserved on back navigation? ## Output Format ```markdown ## User Flow Analysis: <flow-name> ### Flow Map ``` [Entry] → [Step 1: <name>] → [Step 2: <name>] → [Decision: <condition>]