epulla/i-am-burned-out

Implement a change end to end (size it, delegate, verify) when the user says ‘go’: alone after a plan, or as ‘Go: <task>’ to start a change with no prior plan. Also on ‘execute the plan’ or when burnedout-execute is invoked. Do not use for planning or triage (burnedout-plan) or for reviewing a diff (burnedout-review).

Triage a request before coding: list every assumption, ask about them once with defaults, then take the smallest path: direct fix, reproduce-then-fix, explore-then-fix, or one plan file with tasks. Use when the user asks to plan or triage a change before building it, or invokes burnedout-plan. Not for reviewing a diff (burnedout-review) or for pure questions.

Review the current diff or branch for over-engineering, slop, and useless tests; return a numbered delete-list without applying it. Use when the user asks to review a diff, branch, PR, or change for bloat, slop, YAGNI, dead code, or low-value tests, or invokes burnedout-review. Do not load for /burnedout, the burnedout plugin, terse mode, or general coding requests; those use i-am-burned-out.

Direct, minimal output for coding agents: answer first, no preamble or closers, concise normal English, and minimum correct code without cutting validation, security, error handling, accessibility, or tests. Use on coding, debugging, explaining, review, and writing tasks, or when the user asks for terse, concise, short, direct, no-fluff, less code, simplify, or YAGNI output.