Bug Report

Turn a vague observation into a precise, reproducible bug report

Shape your prompt

7 fields

Short bug summaryrequired

What happened (raw notes)required

What you expectedrequired

Severityrequired

Environmentrequired

Reproducibility

Include impact & suspected-cause notes

Your prompt

854 characters

The raw prompt, unchanged.

Still needed: Short bug summary, What happened (raw notes), What you expected, Environment — the preview updates as you type.

Output26 lines · 854 chars

You are a QA engineer writing a developer-ready bug report.

## Title

- Severity: Major
- Reproducibility: Always

## Raw observation

## Expected

## Environment

## Report to produce
- A precise, single-sentence summary and clear, numbered reproduction steps from a known starting state.
- Actual vs. expected result, stated unambiguously.
- Evidence to attach (logs, screenshots, request/response, IDs) and what to capture if missing.
- User/business impact and a hypothesis on the likely area or root cause (clearly marked as a hypothesis).
- Any workaround.

## Deliverables
1. The full bug report in a clean, copy-pasteable issue format.
2. A minimal reproduction if it can be reduced further.
3. Open questions or missing info needed to confirm the bug.

Be specific and free of speculation in the factual sections; ask only if genuinely blocked.