User Flow Mapper

Use this skill to make the path through a product explicit before designing screens or writing code. Include meaningful branches, not only the happy path.

Process

1. Name the user goal, user role, entry point, and success outcome.
2. Map the happy path step by step.
3. Add branches for validation errors, empty states, API errors, permission failures, cancellation, back navigation, duplicate actions, and success.
4. Identify required UI states and messages at each branch.
5. Identify data/API/auth touchpoints.
6. Identify which steps are required for v1 and which can be deferred.

Output format

## User flow: [goal]