Skip to content
UX Atlas
AI workflowCraft conventionIntermediate

PRD to User Flow

Turning a requirements document into a draft flow, which is most useful for the edge cases the document forgot.

Definition

Feed a requirements document to a model and ask for the user flow it implies, including states, decision points and error paths. The value is in surfacing what the document left undefined.

Craft convention. True because the industry converged on it. Breaking it costs familiarity, not correctness.

On this page
  1. Definition
  2. Prompt
  3. Always verify
  4. Continue from here

Prompt

text
From the requirements below, produce the user flow they imply.

Return:
1. The happy path, as numbered steps
2. Every decision point, with the branches
3. Every error and edge case implied but not specified
4. Every state the requirements do not define (empty, loading, partial, expired)
5. A list of open questions the requirements do not answer

Mark clearly which items are stated in the requirements and which
you inferred. Do not invent requirements to fill gaps.

Requirements:
[paste]

Always verify

  • Inferred steps that were never actually specified.
  • Regulatory or compliance steps the model does not know about.
  • Existing product conventions the model has no visibility of.
  • Technical constraints that rule out a branch entirely.

Continue from here

Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.

Often used with

These usually appear in the same screen or the same decision.

Related concept

Connected closely enough to change how you apply this.