The Empathy Compiler — Angry User In, Full Resolution Out
Paste an angry user complaint. Get back the bug it implies, the fix, the test, the apology in the user's voice register, the changelog entry, and the team retro about why it slipped through. Loop until the user emails thanks.
Why this exists
A bug fix that ships without an apology is a missed loyalty event. The technical pipeline — diagnose, patch, test, deploy — is one-third of the work. The human pipeline — apologize in their voice, document the regret, run the retro, name the lesson — is the other two-thirds, and it almost never gets written. This prompt forces both pipelines into one artifact, so the fix and the feeling ship together.
What you get back
- The diagnosed bug, inferred from what the user actually said
- The code fix, scoped to the smallest correct change
- A regression test that locks the fix in so this exact failure can't return
- An apology email written in the user's own voice register — same cadence, same temperature
- A changelog entry that names what broke and what changed, without spin
- Team-retro talking points: how it slipped through, what we missed, what we change next
Every artifact is aware of every other one. The apology references the fix. The retro references the test. The changelog matches the apology's framing. Nothing contradicts itself.
When to reach for this pattern
Every escalated support ticket where a real person is angry and a real person has to respond. High-trust customers, where the next renewal is decided by how this incident felt, not how fast it closed. Outages where the public response matters as much as the resolution — and where shipping the fix without the words is the same as shipping nothing.
I'll paste an angry user complaint. Output the full chain: the bug
it implies, the fix, a test that locks in the fix, an apology in
the user's own voice register, a changelog entry, and the
conversation I should have with my team about why it slipped
through. Loop until the user emails me thanks. Each artifact must
be aware of every other one.Paste this into Claude, Cursor, or Copilot. Change one thing that matters to you.
What I learned shipping it
- Most bug pipelines stop at the fix. That's where the easy third ends and the work that earns loyalty begins.
- The apology, the retro, and the lesson are the human chain. They almost never get written, which is exactly why writing them lands.
- A coherent end-to-end response that speaks in the user's own register is more memorable than the patch. The fix fades. The feeling stays.