Bug bash plan before a release with severity rules and roles
Plans a one or two hour bug bash where the whole team tries to break a feature before release: who tests what, test charters by area, devices to cover, a severity scale, a bug report template and how the go or no-go call is made afterwards. Use it a few days before a major release or a festival sale launch.
The output this prompt produced, unedited.
The prompt
What to give
Feature or release: [e.g. a new checkout with UPI and cash on delivery]
Release date: [paste]
People taking part and their roles: [e.g. 10 people: engineers, designers, support, sales]
Devices and browsers available: [e.g. low-end Android, iPhone, Chrome desktop]
Known risky areas: [e.g. coupons, slow networks, address forms]
Test accounts and data: [describe, without passwords]
Check while planning
Every risky area has at least two people and one written charter.
Charters name a goal, not steps, such as "try to pay twice for one order".
Low-end phones and slow networks are covered, not only new devices.
Non-engineers test the parts customers touch most.
One person sorts duplicates while the bash is running.
Severity is agreed before anyone starts.
Output format
An agenda: briefing, testing time, triage, wrap-up, with times.
| Tester | Area | Charter | Device and network |
A severity scale: blocker, major, minor, polish, each with an example from this feature.
A bug report template: title, steps, expected, actual, device, screenshot.
The go or no-go rule, such as no open blockers and majors fixed or accepted by the owner.
Guardrails
No real customer data in test accounts.
Polish items go to a later list, never into the release by default.
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.