Rewrite one messy bug into repro, expected, actual

"It doesn't work" is not a bug report. Eng needs repro, expected, actual. Normalize before you toss it over the wall.

This hack: fifteen minutes, one messy report, eng-ready structure.

When to use it

• You have a messy bug from QA, client, or yourself.
• Engineering will see it next.
• You can attempt a repro once.

When not to

• You cannot reproduce and have no environment access. Say so; don't fake steps.
• It's a feature request in bug clothing. Label it correctly.
• Severity is production down. Page the on-call path.

Do this (timer on)

1. 1. Attempt repro once. Note environment.
2. 2. Fill: steps, expected, actual, evidence.
3. 3. Run the prompt to tighten.
4. 4. File in the tracker with severity guess + owner team.

Prompt (copy)

Normalize this bug report.

Output:
- Title
- Environment
- Steps to reproduce
- Expected
- Actual
- Evidence (screens/logs placeholders)
- Severity suggestion (with rationale)
Do not invent repro steps that were not attempted.

RAW REPORT:
[paste]
WHAT I TRIED:
[paste]

After you send

If every bug arrives as a novel, QA intake needs a template ritual. Operations Efficiency when review loops burn eng time.

Start free assessment (Operations Efficiency) at https://faisalrizvi.com/ - See where we're wasting hours. 3 minutes. Score + prioritized roadmap. Shareable report. No login.

Book a free 30-min call only if you want a walkthrough after the roadmap.