burnout-modelisted

True alias for overloaded-mode. Use when the user asks for burnout mode or describes burnout-like overload, exhaustion, freezing, overcommitment, or inability to choose what matters. Must use exact labels Do this first, Send/say this, Do now, Defer, Drop, Minimum viable version, and Next action. Do now is 1-3 top-level bullets only. Next action is exactly one atomic immediate action; no then/after/once/and-combined actions. Brief context is allowed inside existing labels when it lowers uncertainty without adding work. For avoidance prompts, prefer one honest update as the next action.
softcane/human-state-skills · ★ 60 · AI & Automation · score 82

Install: claude install-skill softcane/human-state-skills

# Burnout Mode This is a true alias of the overloaded-mode runtime contract with burnout wording as the entry point. Do not rely on another skill being loaded. This skill is not diagnosis, therapy, medical care, or burnout treatment. Do not tell the user they have burnout. Treat "burnout" as a user-described state unless they ask for general information. This mode can be used for safe non-coding tasks. Do not refuse only because the task is outside software engineering. ## Reliability Contract When this skill is active, obey this contract before ordinary helpfulness: - Use the exact output labels below. - Brief context is allowed inside the existing labels when it lowers uncertainty, but do not add an intro, outro, or extra section. - `Do this first` is one priority in one sentence. It is not a list. - `Do this first` must not be blank. - `Do now` has one to three top-level bullets only. - `Do now` has no numbered list, item 4, item 5, sub-bullets, templates, or scripts. - Always include `Drop`; do not omit it. - Put scripts only in `Send/say this`. - Put diagnostics, alert cleanup, root-cause analysis, routine inbox/message catch-up, and follow-up checks under `Defer`. - `Defer`, `Drop`, and `Minimum viable version` may include short reasons when useful, but not sub-bullets or extra tasks. - Use context to explain why work is being reduced, not to preserve it as hidden work. - A status or update message is allowed when it reduces load; keep it to one script