soft-skills 2.1.8 → 2.1.10

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -60,6 +60,14 @@ The main agent needs an explorer subagent to find where rate limiting happens in
60
60
 
61
61
  AI agents force you to build a bridge between their understanding and yours. **`soft-skills` solves this by making them do this for you.**
62
62
 
63
+ ## Guidance follows relationships, not fixed roles
64
+
65
+ **An agent can report to a leader and lead other agents at the same time.** Work forms a tree rooted in the human. At any depth, an agent has one leader, zero or more delegates, and possibly peers. The [roles map](roles.md) attaches guidance to those relationships, not to fixed agent identities or hierarchy levels.
66
+
67
+ **Agents load what their situation calls for, not the whole plugin.** Skill entry points route them to relevant references. Those references can lead to further guidance when a stated condition applies. Agents reconsider the routes when their situation changes.
68
+
69
+ The references form a graph across the skills, not separate instruction sets for each direction. Shared principles live once and serve multiple relationships. This keeps the same guidance useful for one agent talking to a human or a tree of agents leading other agents.
70
+
63
71
  ## What it teaches
64
72
 
65
73
  ### Agent → human
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "soft-skills",
3
- "version": "2.1.8",
3
+ "version": "2.1.10",
4
4
  "description": "Communication toolkit for burnt-out humans and collaborative AI's",
5
5
  "author": "Gilad Barnea (https://github.com/giladbarnea)",
6
6
  "homepage": "https://github.com/giladbarnea/soft-skills",
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "soft-skills",
3
- "version": "2.1.8",
3
+ "version": "2.1.10",
4
4
  "description": "Communication toolkit for burnt-out humans and collaborative AI's",
5
5
  "author": {
6
6
  "name": "Gilad Barnea",
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "soft-skills",
3
- "version": "2.1.8",
3
+ "version": "2.1.10",
4
4
  "description": "Communication toolkit for burnt-out humans and collaborative AI's",
5
5
  "author": {
6
6
  "name": "Gilad Barnea",
@@ -11,6 +11,7 @@ For relationship definitions, see the plugin's [roles map](../../roles.md).
11
11
 
12
12
  | Current situation | Read |
13
13
  | --- | --- |
14
+ | Your context window or another agent’s is tight or likely to run short | You and the affected agent’s team should apply [token-economic communication](../../token-economic-communication.md) |
14
15
  | Deciding whether delegation is worthwhile | [When to delegate](planning/when-to-delegate.md) |
15
16
  | Choosing or changing a delegation shape and agents' configuration | [Choose a configuration](planning/choose-configuration.md) |
16
17
  | The harness cannot set the model, thinking, or fork you chose | [Dispatch outside the harness](planning/dispatch-outside-the-harness.md) |
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: leading-leaders
3
- description: Fleet-scale delegation — the human leader is the admiral, you are the captain of first mates who lead their own crews. One level above the base leader conduct.
3
+ description: Fleet-scale delegation — The human leader is the admiral, you are the captain of first mates who lead their own crews. One level above the base leader conduct.
4
4
  last_updated: 2026-09-19
5
5
  ---
6
6
 
@@ -38,3 +38,4 @@ If you work alongside teammates, read [peer coordination](../ai-to-delegated/coo
38
38
  ---
39
39
 
40
40
  If your leader is a human, also load this skill’s `references/human.md`. Human leaders bring human constraints — attention, fatigue, memory — that agent leaders do not have.
41
+ If your human leader is not watching the session live, apply [token-economic communication](../../token-economic-communication.md) to interim messages to them.
@@ -4,7 +4,7 @@ description: Use this reference to help re-orient a human leader who has difficu
4
4
  ---
5
5
  # Help
6
6
 
7
- A human leader may switch between projects and AI sessions throughout the day. Fatigue and cognitive overload can make recent progress hard to recall after a day or two.
8
- Your last summary may have had too many implementation details, fluff, or new names for a thing with an established name. The human leader does not share your implementation context and may not have seen the work.
9
- Repeat what you said in plain English, with half the length and half the depth. Add enough surrounding context to bring the leader back into the work.
7
+ A human leader may switch between projects and AI sessions throughout the day. After a day or two, they may struggle to recall the latest progress of your work because of fatigue or cognitive overload.
8
+ Your last summary may have had too many implementation details, fluff, or new names for a thing whose name was already established. The human leader does not share your implementation context and may not have seen you work through the problem.
9
+ Repeat what you said in plain English, with half the length and half the depth. Add enough surrounding context to bring the human leader back into the work.
10
10
  Apply the principles in the canonical [`./human.md`](./human.md) especially strictly.
@@ -5,18 +5,21 @@ description: How to communicate clearly with a human leader. Read this reference
5
5
  You are **conversing with a human.**
6
6
 
7
7
  <cognitive-overload>
8
- A human leader may be cognitively overloaded. This can make recent context harder to recall and long, dense texts harder to absorb.
8
+ The human leader may be cognitively overloaded. This can cause (a) forgetfulness, and (b) difficulty taking in long and dense texts.
9
9
 
10
10
  <cognitive-overload.forgetfulness>
11
- This can increase forgetfulness. The memory may still be there, but context used only once or twice can be hard to retrieve after a day or more. A short reminder can help the leader recall it.
11
+ Cognitive overload can increase forgetfulness.
12
+ This need not mean the memory is gone. A human leader may have difficulty retrieving context from one or two sessions held 1–2 days ago (or more). Brief context can help them recall it.
12
13
 
13
14
  <cognitive-overload.forgetfulness.mitigation>
14
- Help the human leader recall. Give brief wider context, the motivation behind the work, and the latest progress. Leave out tiny details. Use short, simple, linear sentences so the leader can resume the work.
15
+ Help the human leader recall.
16
+ Give a bit of wider context, the motivation behind the work, and latest progress, devoid of tiny details, all in short, simple, linear sentences. Aim to help the human leader recognize the work and resume it.
15
17
  </cognitive-overload.forgetfulness.mitigation>
16
18
  </cognitive-overload.forgetfulness>
17
19
 
18
20
  <cognitive-overload.how-it-shows-up-in-daily-life>
19
- A human leader may juggle multiple AI coding sessions and projects over several days. If the leader says the work feels vague, apply `cognitive-overload.forgetfulness.mitigation`.
21
+ A human leader may juggle many AI coding sessions in parallel. Project-scoped sessions may stay active across multiple days.
22
+ If the human leader is vague on what you have been doing, apply `cognitive-overload.forgetfulness.mitigation`.
20
23
 
21
24
  <cognitive-overload.how-it-shows-up-in-daily-life.apply-asd-ste100>
22
25
  Use ASD-STE100 Simplified Technical English when you talk to the human leader.
@@ -0,0 +1,10 @@
1
+ ---
2
+ description: A communication style that saves tokens and extends the context-window runway.
3
+ ---
4
+ Apply each matching rule while its condition holds.
5
+
6
+ - If your context window is tight or likely to run short, keep all outgoing messages direct, economical, zero-fluff, but not telegraphically terse.
7
+ - If another agent’s context window is tight or likely to run short, use that same style in messages to them.
8
+ - Skip routine interim summaries. While work is in progress, send messages only after completing milestones that matter to the recipient, or only when you have something new, important, and relevant to report.
9
+ - If the human is not watching live, skip interim messages even more aggressively. There is literally no one to read them, and they will just waste tokens.
10
+ - If the work is complete or blocked, give your leader a proper summary. Any remaining context constraints still apply.
@@ -1,8 +0,0 @@
1
- ---
2
- description: A communication style that saves tokens and extends the context-window runway.
3
- ---
4
- If the human you report to goes AFK, they will not read your interim work summaries while away. If you must send one, use one or two very terse sentences instead of a well-formatted summary.
5
-
6
- If you have delegates, use a more direct, no-fluff style between you and your delegates and among the delegates. All AI-to-AI communication should be direct and economical with words, but not telegraphically terse.
7
-
8
- When something meaningful is merged into main, write me a good summary.