Prompt library
Outline a user flow with its failure paths
Demanding failure-path parity with the happy path is where this prompt earns its keep: most flow documents die at the first error state, and users do not. The state inventory for mid-flow returns covers the resume experience that separates polished products from prototypes.
Last reviewed July 17, 2026
The prompt
Outline the user flow for {{feature}}.
Entry context: {{entry}}
Produce:
1. The spine: the happy path as numbered steps. Per step: what the user sees, the decision or input they make, what the system does, and what they see next. One screen or state per step.
2. The exits: at each step, why a user would abandon here (confusion, fear, missing info, effort), and what the design does about the top one.
3. The failure paths: for every step with input or a system call, the error and edge cases (invalid input, timeout, permission denied, empty state, partial completion) and where each path rejoins the spine or exits cleanly.
4. State inventory: everything that must persist if the user leaves mid-flow and returns (a draft, a cart, a step marker), and what greets them on return.
5. The metrics map: the 2-3 points in the flow where instrumentation would locate drop-off precisely.
Rule: the failure paths section must be at least as detailed as the spine. Happy paths are easy; products are judged on the other paths.Run in idaptOpens a new chat with the prompt prefilled. Nothing sends until you press send.
Fill in the variables
| Variable | What it is | Example |
|---|---|---|
| {{feature}} | The flow to design | inviting a teammate to a shared workspace |
| {{entry}} | Where users come from | an empty-state banner and a settings page |