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
- | Group | Case | Trigger | Expected behaviour | Owner (design, build, test) |
- States the design must show: empty, loading, error, success, no permission, each with one line of suggested copy.
- 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.






