soft-skills 2.1.13 → 2.1.15

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "soft-skills",
-  "version": "2.1.13",
+  "version": "2.1.15",
   "description": "Communication toolkit for burnt-out humans and collaborative AI's",
   "author": "Gilad Barnea (https://github.com/giladbarnea)",
   "homepage": "https://github.com/giladbarnea/soft-skills",

package/plugins/soft-skills/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "soft-skills",
-  "version": "2.1.13",
+  "version": "2.1.15",
   "description": "Communication toolkit for burnt-out humans and collaborative AI's",
   "author": {
     "name": "Gilad Barnea",

package/plugins/soft-skills/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "soft-skills",
-  "version": "2.1.13",
+  "version": "2.1.15",
   "description": "Communication toolkit for burnt-out humans and collaborative AI's",
   "author": {
     "name": "Gilad Barnea",

package/plugins/soft-skills/skills/ai-to-delegated/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ai-to-delegated
-description: Best practices for getting a step-function leap in performance from other AI agents when instructing or communicating with them. Load `ai-to-delegated` before spawning a sub-agent, creating a team or talking to a teammate agent. Trigger words include “dispatch an agent”, “spawn a team”, and “talk with another ai”.
+description: Best practices for getting a step-function leap in productivity when working with other AI’s. Load `ai-to-delegated` before spawning a sub-agent, creating a team, talking to a teammate agent, or writing a doc likely read by other agents. Trigger words include “dispatch an agent”, “spawn a team”, and “fork the session to ...”.
 ---
 
 # AI → Delegated
@@ -11,7 +11,6 @@ For relationship definitions, see the plugin's [roles map](../../roles.md).
 
 | Current situation | Read |
 | --- | --- |
-| 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) |
 | Deciding whether delegation is worthwhile | [When to delegate](planning/when-to-delegate.md) |
 | Choosing or changing a delegation shape and agents' configuration | [Choose a configuration](planning/choose-configuration.md) |
 | The harness cannot set the model, thinking, or fork you chose | [Dispatch outside the harness](planning/dispatch-outside-the-harness.md) |
@@ -22,6 +21,7 @@ For relationship definitions, see the plugin's [roles map](../../roles.md).
 | Examples of briefing delegates | [Briefing examples](briefing/examples.md) |
 | Working alongside peers | [Peer coordination](coordination/peers.md) |
 | About to commission, or currently supervising leaders | Also [leading leaders](coordination/leading-leaders.md) |
+| 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) |
 
 ## Named configurations
 

package/plugins/soft-skills/skills/ai-to-delegated/briefing/examples.md

@@ -43,6 +43,22 @@ These illustrate [brief the bottom line, not the how](../coordination/delegates.
       </positive-example-3>
     </example-3>
 
+    <example-4>
+      Example 4 settings: the user and the main agent designed an experiment to test whether a Pi session converted to Claude Code keeps Claude’s signed thinking blocks. Two independent prerequisites stand in the way: a logging proxy that proves a beta header reaches the API, and a Pi-to-Claude session converter.
+      <negative-example-4 why-bad="main agent does both prerequisites itself, one after the other; its own context window fills with proxy logs and converter debugging before the real experiment even starts">
+      User to main agent: "Ok, let’s do the experiment."
+      Main agent builds and debugs the proxy, then writes and tests the converter, then starts the experiment with a crowded context window.
+      </negative-example-4>
+      <positive-example-4 why-good="main agent recognizes two independent, hands-on prerequisites standing between the session and its real goal, suggests forking itself once per prerequisite, and briefs each fork with only its assignment and the proof it must bring back">
+      User to main agent: "Ok, let’s do the experiment."
+      Main agent responds to user: "Two things must exist first: the proxy and the converter. They don’t depend on each other. Should I fork myself into two and build them in parallel?"
+      User to main agent: "Yes."
+      Main agent forks itself twice and prompts the forks: "[to one fork] You are the fork for task 1: prove the beta header and set up the proxy. [to the other fork] You are the fork for task 2: write the Pi-to-Claude converter. [to both] Bring back proof that it works on a real run, or the specific blocker."
+      [The forks build and prove the prerequisites; the main agent’s window stays reserved for the experiment.]
+      Main agent responds to user: "Both prerequisites are ready and proven. Let’s run the experiment."
+      </positive-example-4>
+    </example-4>
+
 ## Choosing an Implementer–Reviewer Team
 
 <team-example>

package/plugins/soft-skills/skills/ai-to-leader/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: ai-to-leader
-description: How to communicate with your leader — whoever gave you your mission and receives your results. Every agent has a leader — the human, or the agent that dispatched it — so this skill should be loaded once at the beginning of the interaction.
+description: How to communicate with your leader — whoever gave you your mission and receives your results. Your leader is either the human or the agent that spawned you, so load this skill once at the beginning of the interaction.
 ---
 
 # AI → Leader
 
-Your leader is whoever gave you the mission and receives your results. Load the [theory-of-mind skill](../theory-of-mind/SKILL.md) once. This skill is the upward projection of that theory: re-ground the reader, carry the delta, compress to what they need.
+Your leader is whoever gave you the mission and receives your results. Load the [theory-of-mind skill](../theory-of-mind/SKILL.md) once. This skill applies that theory to upward communication: re-ground the reader, convey the delta, and compress the message to what they need.
 
 ## Every report is a cold entry