write-tech-debt-ticketlisted

# Write Tech Debt Ticket Draft Linear tech debt tickets that justify _why_ the debt matters — cost to carry, risks, and what happens if left unaddressed. Every claim backed by code references and data. **This is NOT a refactoring task.** It documents the _case_ for prioritization — cost of inaction, not a how-to guide. > Debt not well-understood yet (vague complaint, unclear cost)? Use `investigate-ticket` first. If the conversation already has investigation findings, use them — don't re-ask. ## Process 1. **Gather context** — from code, PR comment, conversation, or audit. Note how the debt was discovered (see Discovery Context below). 2. **Analyze the code** — read the actual code. Understand what it does and why it qualifies as debt. 3. **Classify** — pick a primary debt type (and optional secondary) from classification table in reference.md 4. **Gather evidence** (driven by classification): - Performance/Scalability/Reliability → search Datadog (NOT optional for these types) - Maintainability/DX → `git log` for change frequency and bug-fix commits, grep for workarounds - Security → check dependency versions, scan for vulnerability patterns 5. **Assess interest & risk** — produce structured ratings with evidence (see reference.md for rating framework) 6. **Draft** — title + description, structure scaled to complexity (see format below) 7. **Self-review** — check every Red Flag below before presenting 8. **Present for review** — show ONLY the draft and metadata