• Defects are found and must be communicated for fast fix and retest.
• Team has recurring misunderstandings about issue severity or reproduction.
• Management needs clear defect status and impact visibility.

• Produce actionable bug reports with clear reproduction and impact.
• Improve fix turnaround by reducing back-and-forth clarification.
• Enable reliable prioritization by severity and business risk.

1. Capture environment, precondition, and minimal reproduction steps.
2. Document expected vs. actual behavior with objective evidence.
3. Assess severity, scope impact, and user/business consequence.
4. Attach logs/screenshots/api payloads for quick diagnosis.
5. Propose verification points after fix.
6. Track lifecycle and closure evidence.

Input:

• Checkout failure under expired-token refresh path

Output:

• Repro steps, request id, failing response payload
• Severity rationale (payment interruption)
• Retest checklist for fix validation

Input:

• "Payment has bug"

Output (problem):

• No environment, no reproducible steps, no expected result
• Developer cannot verify root cause efficiently

• Do not submit bugs without reproducible evidence.
• Do not overstate severity without impact rationale.
• Do not mix multiple unrelated issues in one ticket.
• Do not close issue without retest proof.
• Do not hide intermittent behavior; mark and track it explicitly.