Create intermediate Works with: Any AI

Edge Cases and Failure Modes Brainstorm

Table output

Think of what could go wrong.

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

Brainstorm edge cases for a feature. Feature description: [FEATURE]. Users and data: [USERS_DATA]. Integrations: [INTEGRATIONS].

List edge cases across data (empty, very long, special characters, duplicates), users (new, expired, many roles), timing (time zones, concurrency, retries), network and third-party failures, permissions, and regulations. Organise in a table with Case | What could happen | Likelihood | Impact | Proposed behaviour. Mark the five most important and suggest tests. Include accessibility and internationalisation cases. Avoid inventing technical details not given and list questions for engineering.

Add a technique for finding more cases: walk through the feature as five different users, and list what could go wrong at each step. Provide a prioritisation approach that identifies which cases to handle in the first release and which to defer, and a template for recording decisions with the reason so the team does not revisit them without cause.

Also add a short list of questions to ask support staff, who often know the edge cases that customers actually hit.

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.

• requirements