wowprompt

Edge case and error state inventory for a feature spec

Reads a feature description and lists the edge cases, empty, loading, error and permission states the design and build must handle, each with the expected behaviour. Use it before design review or sprint planning, so the missing states are found on paper rather than in production.

A table of edge cases grouped by data, network, permissions and timing, each with the trigger, expected behaviour and owner, plus open questions for the product owner
The output this prompt produced, unedited.

The prompt

Goal

A complete list of the states and edge cases a feature must handle, written so designers, developers and testers can each act on it.

Inputs

  • Feature description or spec: [paste]
  • Platforms: [web, Android, iOS]
  • User roles: [e.g. owner, member, guest]
  • Data limits known: [e.g. names up to 80 characters, files up to 10 MB]
  • Related features it touches: [e.g. notifications, billing]

Checklist to work through

  • Data: empty, one item, very many items, very long text, special characters, duplicates, deleted items still referenced.
  • Network: slow load, offline, timeout, request sent twice, partial save.
  • Permissions: role without access, access removed mid-session, shared links opened by someone signed out.
  • Timing: two people editing at once, expired session, time zones, date boundaries.
  • Input: invalid formats, pasted content, copy with leading spaces, unsupported files.
  • Recovery: undo, retry, what is kept after an error.

Output format

  1. | Group | Case | Trigger | Expected behaviour | Owner (design, build, test) |
  2. States the design must show: empty, loading, error, success, no permission, each with one line of suggested copy.
  3. Open questions: decisions the spec does not answer, written as yes or no questions.

Rules

  • Only list cases that can happen with this feature as described.
  • Where the spec is silent, mark the behaviour "decision needed" instead of choosing one.
  • Keep each expected behaviour to one sentence.
edge cases product specerror states designempty state loading statefeature spec reviewqa scenariosproduct requirements gaps

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity