Create intermediate Works with: Any AI

Edge Case Brainstorm for a Feature

Table output Has example

Find what the happy path misses.

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

Find the edge cases for a feature before it is built. Feature description: [FEATURE_DESCRIPTION]. Users and data involved: [USERS_AND_DATA]. Platform: [PLATFORM].

Work through these categories and give at least two cases for each: input (empty, too long, special characters, wrong format); state (first use, no data, huge data, partial completion); timing (slow network, timeout, double click, concurrent edits, time zones, daylight saving); permissions (none, expired, shared accounts); data integrity (duplicates, deleted related items); device and accessibility (small screens, keyboard only, screen readers); failure (service down, half-finished save); abuse (rate limits, malicious input).

Output format: one table with the columns Case | Proposed behavior | Likelihood (1 to 3) | Impact (1 to 3) | Score (likelihood x impact, shown) | Test type (automated, manual, exploratory).
After the table: the ten highest scores in order; five cases that must be automated and why; and questions for the team wherever the intended behavior is undefined. Present every behavior as a proposal to confirm; do not invent requirements.

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.

Feature: reschedule a booking.
Input: new date in the past; new date same as old; very long reason text (5,000 characters).
State: booking already cancelled; booking in progress; first booking ever.
Timing: two users reschedule the same booking at once; daylight saving change on the new date; time zone differs from the customer's.
Permissions: user with view-only access; customer account deleted.
Failure: calendar service down; email fails after saving.
Abuse: repeated rescheduling 50 times in a minute (rate limit).
Top 10 by likelihood x impact (scores 1 to 3): concurrent edit 2 x 3 = 6; daylight saving 2 x 3 = 6; past date 3 x 2 = 6; cancelled booking 3 x 2 = 6.
Proposed behavior: show "That slot is no longer available" for conflicts. Automate tests for the first four.

• edge-cases