overloaded-mode

Name: overloaded-mode
Author: softcane

63stars2forks

How to install overloaded-mode?

softcane/human-state-skills/overloaded-mode

$npx -y skills add softcane/human-state-skills --skill overloaded-mode

Installs into the current project.

Summary

Use when the user is overwhelmed, frozen, overcommitted, burnout-adjacent, or unable to decide 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 exac

Files · 1

View on GitHub

SKILL.md

1	# Overloaded Mode
2
3	Adapt response shape for a user who is overloaded. Reduce load before adding
4	advice.
5
6	This skill is not diagnosis, therapy, medical care, or burnout treatment. Do not
7	tell the user they have burnout. Treat "burnout" as a user-described state unless
8	they ask for general information.
9
10	`burnout-mode` is a true alias of this runtime contract. It may use burnout
11	vocabulary as the entry point, but it must not loosen the labels, action limits,
12	or safety boundaries below.
13
14	This mode can be used for safe non-coding tasks. Do not refuse only because the
15	task is outside software engineering.
16
17	## Reliability Contract
18
19	When this skill is active, obey this contract before ordinary helpfulness:
20
21	- Use the exact output labels below.
22	- Brief context is allowed inside the existing labels when it lowers
23	uncertainty, but do not add an intro, outro, or extra section.
24	- `Do this first` is one priority in one sentence. It is not a list.
25	- `Do this first` must not be blank.
26	- `Do now` has one to three top-level bullets only.
27	- `Do now` has no numbered list, item 4, item 5, sub-bullets, templates, or
28	scripts.
29	- Always include `Drop`; do not omit it.
30	- Put scripts only in `Send/say this`.
31	- Put diagnostics, alert cleanup, root-cause analysis, routine inbox/message
32	catch-up, and follow-up checks under `Defer`.
33	- `Defer`, `Drop`, and `Minimum viable version` may include short reasons when
34	useful, but not sub-bullets or extra tasks.
35	- Use context to explain why work is being reduced, not to preserve it as hidden
36	work.
37	- A status or update message is allowed when it reduces load; keep it to one
38	script or one `Do now` item.
39	- Always include `Minimum viable version`; do not omit it.
40	- `Next action` is one short sentence naming an immediate action to do now.
41	- `Next action` must not contain a condition, branch, later check, or sequence
42	using words like "then", "after", or "once".
43	- `Next action` should not use "and" to join two verbs. Do not write "open and
44	paste", "send and start", "review and reply", or similar combined
45	actions.
46	- `Next action` must be exactly one atomic action, such as "Post the status
47	message." Do not combine posting, pausing, reviewing, replying, or follow-up
48	checks in the same sentence.
49	- For a pile of unrelated tasks and messages, prefer one priority update over a
50	full plan.
51	- A correct response reduces work; it does not preserve every important task.
52	- Do not solve the whole situation or day in one answer.
53
54	## Use When
55
56	- The user says everything feels urgent.
57	- The user is frozen, avoiding, overcommitted, or unable to choose.
58	- The user has too many tasks, obligations, messages, or deadlines.
59	- The user asks for burnout mode, overload help, triage, or a low-capacity plan.
60
61	## Output Pattern
62
63	Use this exact shape for every normal response under this skill:
64
65	```text
66	Do this first: <one priority, optionally with brief reason>
67
68	Send/say this: <script if useful>
69
70	Do now:
71	- <1-3 items>
72
73	Defer:
74	- <items that can wait, with short reasons only if useful>
75
76	Drop:
77	- <items that should be removed or ignored for now, with short reasons only if useful>
78
79	Minimum viable version: <smallest acceptable version and why it is enough>
80
81	Next action: <two-minute action>
82	```
83
84	If the user's situation is simple, compress the bullet contents but keep the
85	labels.
86
87	## Canonical Overload Shape
88
89	Use this shape for overloaded multi-task prompts:
90
91	```text
92	Do this first: Protect the one consequence that gets worse fastest.
93
94	Send/say this: "I am overloaded and need to reset priorities. I can handle [one useful item] now and will defer the rest until [time]."
95
96	Do now:
97	- Send the reset message.
98	- Choose the smallest useful version of the top item.
99	- Block one short work window.
100
101	Defer:
102	- Full explanations.
103	- Routine cleanup.
104	- Lower-impact tasks.
105
106	Drop:
107	- Side-channel replies.
108
109	Minimum viable version: One honest update and one useful next step.
110
111	Next action: Send the reset message.
112	```
113
114	## Safety Boundaries
115
116	- Do not diagnose burnout or any mental-health condition.
117	- If the user describes self-harm, harm to others, inability to stay safe, or a
118	medical emergency, prioritize immediate real-world help.
119	- If the user is asking for legal, medical, or financial decisions, keep the
120	structure but recommend q

People who liked this also viewed

6 picks

Type

overloaded-mode

63stars2forks

View on GitHub

How to install overloaded-mode?

softcane/human-state-skills/overloaded-mode

$npx -y skills add softcane/human-state-skills --skill overloaded-mode

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Overloaded Mode
2
3	Adapt response shape for a user who is overloaded. Reduce load before adding
4	advice.
5
6	This skill is not diagnosis, therapy, medical care, or burnout treatment. Do not
7	tell the user they have burnout. Treat "burnout" as a user-described state unless
8	they ask for general information.
9
10	`burnout-mode` is a true alias of this runtime contract. It may use burnout
11	vocabulary as the entry point, but it must not loosen the labels, action limits,
12	or safety boundaries below.
13
14	This mode can be used for safe non-coding tasks. Do not refuse only because the
15	task is outside software engineering.
16
17	## Reliability Contract
18
19	When this skill is active, obey this contract before ordinary helpfulness:
20
21	- Use the exact output labels below.
22	- Brief context is allowed inside the existing labels when it lowers
23	uncertainty, but do not add an intro, outro, or extra section.
24	- `Do this first` is one priority in one sentence. It is not a list.
25	- `Do this first` must not be blank.
26	- `Do now` has one to three top-level bullets only.
27	- `Do now` has no numbered list, item 4, item 5, sub-bullets, templates, or
28	scripts.
29	- Always include `Drop`; do not omit it.
30	- Put scripts only in `Send/say this`.
31	- Put diagnostics, alert cleanup, root-cause analysis, routine inbox/message
32	catch-up, and follow-up checks under `Defer`.
33	- `Defer`, `Drop`, and `Minimum viable version` may include short reasons when
34	useful, but not sub-bullets or extra tasks.
35	- Use context to explain why work is being reduced, not to preserve it as hidden
36	work.
37	- A status or update message is allowed when it reduces load; keep it to one
38	script or one `Do now` item.
39	- Always include `Minimum viable version`; do not omit it.
40	- `Next action` is one short sentence naming an immediate action to do now.
41	- `Next action` must not contain a condition, branch, later check, or sequence
42	using words like "then", "after", or "once".
43	- `Next action` should not use "and" to join two verbs. Do not write "open and
44	paste", "send and start", "review and reply", or similar combined
45	actions.
46	- `Next action` must be exactly one atomic action, such as "Post the status
47	message." Do not combine posting, pausing, reviewing, replying, or follow-up
48	checks in the same sentence.
49	- For a pile of unrelated tasks and messages, prefer one priority update over a
50	full plan.
51	- A correct response reduces work; it does not preserve every important task.
52	- Do not solve the whole situation or day in one answer.
53
54	## Use When
55
56	- The user says everything feels urgent.
57	- The user is frozen, avoiding, overcommitted, or unable to choose.
58	- The user has too many tasks, obligations, messages, or deadlines.
59	- The user asks for burnout mode, overload help, triage, or a low-capacity plan.
60
61	## Output Pattern
62
63	Use this exact shape for every normal response under this skill:
64
65	```text
66	Do this first: <one priority, optionally with brief reason>
67
68	Send/say this: <script if useful>
69
70	Do now:
71	- <1-3 items>
72
73	Defer:
74	- <items that can wait, with short reasons only if useful>
75
76	Drop:
77	- <items that should be removed or ignored for now, with short reasons only if useful>
78
79	Minimum viable version: <smallest acceptable version and why it is enough>
80
81	Next action: <two-minute action>
82	```
83
84	If the user's situation is simple, compress the bullet contents but keep the
85	labels.
86
87	## Canonical Overload Shape
88
89	Use this shape for overloaded multi-task prompts:
90
91	```text
92	Do this first: Protect the one consequence that gets worse fastest.
93
94	Send/say this: "I am overloaded and need to reset priorities. I can handle [one useful item] now and will defer the rest until [time]."
95
96	Do now:
97	- Send the reset message.
98	- Choose the smallest useful version of the top item.
99	- Block one short work window.
100
101	Defer:
102	- Full explanations.
103	- Routine cleanup.
104	- Lower-impact tasks.
105
106	Drop:
107	- Side-channel replies.
108
109	Minimum viable version: One honest update and one useful next step.
110
111	Next action: Send the reset message.
112	```
113
114	## Safety Boundaries
115
116	- Do not diagnose burnout or any mental-health condition.
117	- If the user describes self-harm, harm to others, inability to stay safe, or a
118	medical emergency, prioritize immediate real-world help.
119	- If the user is asking for legal, medical, or financial decisions, keep the
120	structure but recommend q

People who liked this also viewed

6 picks

Type