User Flow Design — Orchestrator

Design — Step 2 of 2. Maps navigation paths, decisions, edge cases, platform-native touchpoints, and screen transitions into a validated flow diagram.

Core Question: "Can the user complete their goal without thinking — on every surface of every platform it ships on?"

Critical Gates — Read First

• No Layer 1 before platforms + surfaces enumerated. See references/platform-touchpoints.md. Wireframe size, entries, edge states all depend on it.
• Reject "cross-platform" as a platform. Enumerate: macOS, iOS, iPadOS, Android, Windows, web-desktop, web-mobile, watchOS, tvOS, visionOS, CarPlay, Android Auto, Linux.
• No diagrams before structure. Diagram-agent needs structure + edge-case outputs first.
• No skipping edge cases. Error/empty/loading/permission/offline + per-surface edge states for every screen and surface.
• Challenge >7 happy-path steps. Miller's threshold. Every step must justify itself.
• One flow = one file. No pooling. Each run writes skills-resources/product/flow/<flow-name>.md.
• Stale product context (>30 days) misaligns flows. Recommend re-running icp-research.