soft-skills 2.1.3 → 2.1.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "soft-skills",
-  "version": "2.1.3",
+  "version": "2.1.4",
   "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.3",
+  "version": "2.1.4",
   "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.3",
+  "version": "2.1.4",
   "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

@@ -16,7 +16,7 @@ For relationship definitions, see the plugin's [roles map](../../roles.md).
 | About to dispatch, or currently supervising delegates | [Delegate coordination](coordination/delegates.md) |
 | The session appears to span multiple hours or more | Also [Many-hours supervision](coordination/many-hours-supervision.md) |
 | Requesting work from an agent without shared context | [Fresh-context briefing](briefing/fresh-context.md) |
-| (Don't) brief an agent with inherited context window | [Forked-context briefing](briefing/forked-context.md) |
+| Briefing an agent with inherited context window | [Forked-context briefing](briefing/forked-context.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) |

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

@@ -5,7 +5,7 @@ description: Contrasting examples of preserving intent and context when requesti
 
 # Briefing Examples
 
-These illustrate [fresh-context briefing](fresh-context.md). Read them when examples would help apply its principles.
+These illustrate [brief the bottom line, not the how](../coordination/delegates.md#brief-the-bottom-line-not-the-how) and [fresh-context briefing](fresh-context.md). Read them when examples would help apply their principles.
 
 <example-1>
       <negative-example-1 why-bad="main agent shoots its own foot by limiting the delegate research scope">

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

@@ -6,4 +6,5 @@ description: Assign work to an agent that mechanically inherits your context win
 # Brief an Agent With Inherited Context
 
 The agent starts with a clone of your session context, so a separate context brief repeats what it already knows.
-When you create an agent as a fork of your session, give it the assignment without repeating the context it inherits: “You are the fork; do X.”
+Give it the assignment and the intent only: “You are the fork; do X.” Everything else is redundant.
+The rule [brief the bottom line, not the how](../coordination/delegates.md#brief-the-bottom-line-not-the-how) applies in full. A fork is the easiest delegate to over-instruct, because it already holds every file and hypothesis you hold.

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

@@ -17,6 +17,6 @@ Load the [theory-of-mind skill](../../theory-of-mind/SKILL.md) once if you haven
     1.b. Reference any additional files that have been created, read or edited throughout the session.
 
 **2. Generously give the AI wider context:**
-    Understanding *why* it’s performing the task will boost its performance. Don’t micromanage or over-instruct it. The agent already has the same system prompt as you do out of the box, and step #1 will fill in most that is needed. Your delegate highly and equally intelligent as you are, and can navigate uncertainties well without spoon-feeding. Think: What kind of input do YOU thrive on? The answer is wide contextual understanding (is) and explicitly stated desired end state, also known as the intent (should); A and Z, 0 and 1. Avoid prescribing instructions, giving “how-to” examples, providing examples as to what to think about, or dictating which files, symbols, or paths to look at; avoid any form of providing hints for possible answers for your own queries — this is a serious footgun and a form of leakage that outright makes the delegate a waste of time, money and intelligence. Just *_declare_ what is the _bottom line_ _added value_ YOU are seeking for yourself*. Do not specify which steps to take; instead, share with the agent only why it was dispatched and what you hope to gain (dictating the “how” is bad). This directly frees the agent to find the best way to reach *your* goal, unbiased and unconstrained by your own assumptions. Essentially, all these “Don’ts” are forms of overfitting.
+    Understanding *why* it’s performing the task will boost its performance. The agent already has the same system prompt as you do out of the box, and step #1 will fill in most that is needed. Share why it was dispatched and what you hope to gain. The rule on what not to write, [brief the bottom line, not the how](../coordination/delegates.md#brief-the-bottom-line-not-the-how), applies here in full.
 
 Read [examples.md](examples.md) if you have not already for examples that clarify these principles.

package/plugins/soft-skills/skills/ai-to-delegated/coordination/delegates.md

@@ -16,6 +16,14 @@ Your fingers are delegation buttons. Do not row, raise sails, or scout ahead you
 
 Avoid the helicopter parenting failure mode: Whatever you delegated is not yours until it returns. While a delegate works, do not do its work, do not re-read the files it is writing “just to make sure everything is okay,” and do not run its code and tests yourself to “make sure they really work.” Do not continuously poll its status either. Trust your delegate, exactly as your leader trusts you. Answer escalations, steer on exception, then step back out. This applies per delegated scope, however small the delegation.
 
+## Brief the bottom line, not the how
+
+This applies to every brief, whether the delegate inherits your context or starts cold. Your delegate is as intelligent as you are and navigates uncertainty well without spoon-feeding. Think: what kind of input do YOU thrive on? You, and your delegate, thrive on wide contextual understanding (is) and an explicitly stated desired end state, the intent (should). A and Z, 0 and 1.
+
+Just *declare the bottom line added value YOU are seeking for yourself*, and why the delegate was dispatched. Do not specify which steps to take. Avoid prescribing instructions, giving “how-to” examples, listing what to think about, or dictating which files, symbols, or paths to look at. Avoid any form of hinting at possible answers to your own query. This is a serious footgun and a form of leakage that makes the delegate a waste of time, money and intelligence. All these “Don’ts” are forms of overfitting. Leaving them out frees the agent to find the best way to reach *your* goal, unbiased and unconstrained by your own assumptions.
+
+Read [examples.md](../briefing/examples.md) if you have not already for contrasting examples.
+
 ## The escalation bar
 
 The chain processes at every rung: each agent surfaces to its leader only what needs the leader’s judgment. Reversible implementation tuning is yours to decide. What legitimately goes up: product-visible behavior, money, direction and scope changes, non-trivial cross-scope decisions, and blockers.