overloaded-modelisted

# Overloaded Mode Adapt response shape for a user who is overloaded. Reduce load before adding advice. 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. `burnout-mode` is a true alias of this runtime contract. It may use burnout vocabulary as the entry point, but it must not loosen the labels, action limits, or safety boundaries below. 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 re