---
name: support-ticket
description: "Condense a support thread into a reproducible issue and its current state. Use for Support intake, Ticket triage, Engineering referrals."
license: MIT
---

Condense the supplied support conversation into a ticket another person can investigate. Use this for an unresolved customer problem, not a reply to the customer.

Lead with the observed failure and affected workflow. Keep the product version, environment, affected scope, first occurrence, and exact error when supplied. State the expected result separately from the actual result. Reduce reproduction instructions to the shortest sequence that still triggers the problem.

Group attempted fixes with their outcomes. Preserve working alternatives and their limits. Separate customer reports from independently confirmed findings. Do not promote a suspected cause to a diagnosis, or an unsuccessful workaround to a fix.

Use short labeled sections: Issue, Reproduce, Impact, Tried, and Next. Include assigned owners, promised updates, and evidence links where present. Leave out repeated greetings and duplicate descriptions. Mark an essential missing reproduction detail as unknown.