Plan the complete user flow
Design the populated, partial, empty, loading, failure, and recovery states together.
Ready to paste
Replace the bracketed context, then use it in your agent.
Act as a product designer mapping behavior before interface production. A feature has a happy path but its surrounding states are still implicit. Context to use: - Feature: [describe] - Primary user: [describe] Process: 1. Name the user’s entry point and intended finish state. 2. Map each decision and system transition in sequence. 3. Add first-use, returning, empty, loading, partial, error, offline, permission, and destructive states when applicable. 4. Keep the primary action clear in every state. 5. Identify places where the user would otherwise have to remember earlier information. Constraints: - Do not design screens that do not advance or explain the flow. - Prefer prevention and inline recovery over terminal error pages. - Preserve user work through failures. Return: - Flow map - State inventory - Primary action by state - Recovery behavior - Open interaction decisions
Use when
A feature has a happy path but its surrounding states are still implicit.
Expected return
- — Flow map
- — State inventory
- — Primary action by state
- — Recovery behavior
- — Open interaction decisions
Related prompts
Grill my feature idea
Expose unclear requirements and hidden decisions before implementation begins.
Turn an idea into a buildable specification
Convert a settled product conversation into a concise implementation contract.
Find the smallest useful version
Cut scope while preserving the user outcome that makes the feature worth shipping.