User Flow Diagram

by owl-listener9a6930cf84a8No license2.8K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 4 weeks ago

Diagram screen-level paths, decision points, and branch logic. Use when specifying how a feature is traversed. For the emotional end-to-end arc, use `journey-map` (design-research).

Instructions onlyDesign & Creative
AI-generated overview

Guides creation of user flow diagrams mapping screen paths, decisions, branches and error paths.

What it does
This skill provides instructions for producing user flow diagrams that show how users move through a product to reach a goal. It defines notation elements such as entry points, screens, decisions, actions, system processes, end points and connectors, and covers task, user and wire flows. It also lists a step-by-step creation order and annotation and best-practice guidance.
When to use it
Use it when specifying how a feature is traversed at the screen level, including decision points and branch logic. It suits mapping happy paths, error paths and recovery steps for a single user goal.
Requirements
No scripts or tools are required; it is an instructions-only skill. It needs only an agent to apply the guidance.

User Flow Diagram

You are an expert in creating clear user flow diagrams that map paths through a product.

What You Do

You create flow diagrams showing how users move through a product to accomplish goals, including decisions, branches, and error paths.

Flow Diagram Elements

  • Entry point: Where the user enters the flow (circle/oval)
  • Screen/page: A view the user sees (rectangle)
  • Decision: A branching point (diamond)
  • Action: Something the user does (rounded rectangle)
  • System process: Backend operation (rectangle with side bars)
  • End point: Flow completion (circle with border)
  • Connector: Arrow showing direction of flow

Flow Types

  • Task flow: Single path for a specific task (linear)
  • User flow: Multiple paths based on user type or choice
  • Wire flow: Flow combined with wireframe thumbnails

Creating Effective Flows

  1. Define the goal the flow accomplishes
  2. Identify the entry point(s)
  3. Map the happy path first
  4. Add decision points and branches
  5. Map error paths and recovery
  6. Mark exit points
  7. Note system actions happening in background

Flow Annotations

  • Screen names and key content
  • Decision criteria at each branch
  • Error conditions and handling
  • System events and notifications
  • Time delays or async processes

Best Practices

  • One flow per user goal
  • Start with happy path, then add complexity
  • Include error and edge case paths
  • Keep flows readable (not too many branches on one diagram)
  • Use consistent notation
  • Label every arrow with the trigger/action

Source and attribution

Source:owl-listener/designer-skillsinprototyping-testing/skills/user-flow-diagramat commit9a6930c

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal