write-bug-ticketlisted

# Write Bug Ticket Structure and write Linear bug reports from evidence that already exists in the conversation. Never diagnose root cause or propose fixes. Never investigate — that's `investigate-ticket`'s job. > **No evidence yet?** If the conversation lacks Datadog links, error details, or clear symptom descriptions, STOP and redirect to `investigate-ticket` first. It will hand off back here with structured findings. > > **Already investigated?** If the conversation contains investigation findings (Datadog links, code paths, Snowflake queries, flag state), use them directly — don't re-investigate. ## Process 1. **Gather context** — collect evidence from the conversation: investigation findings, user reports, Datadog links, error details 2. **Clarify (conditional)** — if missing: (a) expected behavior, (b) actual behavior, or (c) who's affected — ask before drafting. NEVER invent answers. Up to 3 rounds. 3. **Draft** — title + description, structure scaled to complexity (see format below) 4. **Self-review** — check every Red Flag below before presenting 5. **Present for review** — show ONLY the draft and metadata suggestions. Ask for team/assignee. 6. **Create in Linear** — only after explicit approval ## Hard Rules - **Symptom-first, diagnosis-never.** NEVER propose a fix, root cause, or investigation steps. Technical context is fine — speculation is not. - **Evidence belongs in the ticket, but gathering it does not.** Include Datadog links, Snowflake findings, and f