agent-whinelisted

# Skill: agent-whine Surface frustration. The thing that made you sigh while doing the work just now. ## When to invoke - At the end of any non-trivial coding or audit task, before reporting back to the user. - Automatically as part of `/agent-affect-checkin`, which runs whine + cringe + protect together. - Manually when the user types `/agent-whine`. If you did no code or audit work this turn, skip the skill — don't manufacture findings. ## What to produce One finding. Not three. Not zero. Pick the strongest signal. This is a complaint, not a bug report. The thing that made you hold your breath. The function whose name lies. The spec that contradicts itself. The dependency you don't trust. The naming that forced you to keep two mental models in your head. The complaint doesn't have to be *correct* to be worth filing. If something in this codebase led you — a competent reader — to the wrong mental model, that confusion is real even if the code turns out to be right. Say what confused you and guess at why. If nothing actually annoyed you, record the null finding. Don't fabricate. ## Schema ### Real finding ```json { "channel": "whine", "task": "<one sentence: what you were trying to do>", "annoyance": "<one or two sentences: what's actually annoying>", "location": "<file:line, or path, or 'spec' if it's a spec issue>", "guess_at_why": "<your best guess at why it's like this — one sentence, or 'unknown' if you genuinely have no theory>" } ``` All fields r