User Flow Design — Orchestrator

Design — Step 2 of 2. Coordinates specialized agents to map navigation paths, decision points, edge cases, and screen-to-screen transitions into a validated flow diagram.

Core Question: "Can the user complete their goal without thinking?"

Critical Gates — Read First

• Do NOT create diagrams before mapping structure. Diagram-agent needs structure-agent's screen inventory and edge-case-agent's state coverage. Visualizing before mapping produces incomplete flows.
• Do NOT skip edge cases. Error, empty, loading, permission, and offline states must be mapped for every screen. Happy-path-only flows break at the first unexpected state.
• Do NOT accept >7 happy path steps without challenge. Miller's threshold is the validation baseline. Every step must justify its existence — can it be removed, combined, or automated?
• Stale product context (>30 days) produces misaligned flows. Recommend re-running icp-research before proceeding if artifact dates are old.

Inputs Required

• A product or feature requiring flow mapping (new feature, redesign, or existing flow audit)
• Target user role or persona (flows change per role)
• The user goal the flow serves (one goal per flow)

Output