Builds a well-formed bug (defect) report from raw observation notes - fills in summary, environment, steps to reproduce, expected vs actual, and severity rationale - and validates that each field has the load-bearing content reviewers and engineers need to triage. Also converts a single test-failure record (JUnit XML, Allure JSON, pytest log, Playwright report) into a classified, ready-to-file bug spec, and provides the adversarial review checklist that gates a report before it enters the tracker (required fields, single-description title test, severity-priority independence, reproduction quality). Use when a stakeholder reports a problem informally, when a CI failure artefact needs to become a triageable report, or when a drafted report needs a pre-filing quality audit.
81
95%
Does it follow best practices?
Impact
80%
0.88xAverage score across 10 eval scenarios
High
Do not use without reviewing
Tier 1 support escalated a payments complaint to us this morning. The customer moved money between two of her own accounts and says the amount that landed is not the amount she sent, and that her balance no longer adds up. The agent took the call, typed some notes, and pushed the ticket to the Payments queue.
Nobody on the payments team has seen this behaviour before, and the ticket is the only record we have. There is no transfer reference, the screenshot she sent is cropped to the page header, and the agent's notes disagree with the ticket header in at least one place.
The customer leaves for a two-week holiday tomorrow, so we get exactly one reply back to her today. Whatever we still need from her has to go out in that reply.
reports/transfer-amount-mismatch.md — the single document the on-call
payments engineer picks up cold, with no access to the ticket thread and no
ability to phone the agent.Out of scope: diagnosing the cause, reading any payments code, proposing a fix, or contacting the customer yourself.
Extract the following files before beginning.
=============== FILE: inbox/ticket-4471.md =============== Ticket: SUP-4471 Queue: Payments (escalated from Tier 1) Opened: 2026-08-11 09:14 (agent local time) Reporter: Sofia R. — identity verified by phone Product: Northfield personal banking Occurrences reported: 1
--- customer message, pasted from the chat window ---
hi, i moved money from my everyday account over to my savings this morning and the amount that showed up afterwards is not the amount i sent. the number on the confirmation screen looked right i think, but then the line on my statement says something different, and now my balance doesn't add up either.
this happens every single time i move money between my own accounts, it's been like that for a while now. my husband says he has the same thing on his login.
can you just fix the balance please, i'm away from tomorrow
--- agent notes (Marcus, Tier 1) ---