soft-skills 2.1.0 → 2.1.2

package/README.md

@@ -1,6 +1,6 @@
 # `soft-skills`
 
-![Late-shift desk with a terminal showing trusted AI delegation](assets/interaction-banner.png)
+![Late-shift desk with a terminal showing trusted AI delegation](assets/banner.png)
 
 > **Communication toolkit for burnt-out humans and AI collaborations.**
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "soft-skills",
-  "version": "2.1.0",
+  "version": "2.1.2",
   "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.0",
+  "version": "2.1.2",
   "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.0",
+  "version": "2.1.2",
   "description": "Communication toolkit for burnt-out humans and collaborative AI's",
   "author": {
     "name": "Gilad Barnea",

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

@@ -19,7 +19,7 @@ These illustrate [fresh-context briefing](fresh-context.md). Read them when exam
     </example-1>
 
     <example-2>
-      Example 2 settings: the `load-context` skill instructs to read CLAUDE.md, ARCHITECTURE.md, docs/webserver/API.  md, docs/data/architecture.md, server/api.py, and server/db.py.    
+      Example 2 settings: the `load-context` skill instructs to read CLAUDE.md, ARCHITECTURE.md, docs/webserver/API.  md, docs/data/architecture.md, server/api.py, and server/db.py.
       <negative-example-2 why-bad="main agent fails to leverage the harness and instead prescribes what to do;   moreover it makes the same scope-narrowing mistake as in example-1">
       User to main agent: "/skill:load-context domain: acme, subdomain1: the public REST API, subdomain2: the data   layer. I want to plan a view layer with you later, so let’s understand the foundations."
       Main agent spawns a sub-agent and prompts it: "Read CLAUDE.md, ARCHITECTURE.md, docs/webserver/API.md, docs/data/  architecture.md, server/api.py, server/db.py, and summarize how the REST API and data layers work. Cover how   function `server/api.py:from_db` fetches the data by calling the `server/db.py:get_data` function, and how [...  proceeds to prescribe ironically specific locations to “discover”]"

package/plugins/soft-skills/skills/ai-to-delegated/configurations/colloquium.md

@@ -17,7 +17,7 @@ N flat teammates working in parallel.
 
 ## Abstract required conditions for this shape to fit needs
 
-- Teammates’ bottom-line deliverable is figuring out *how* to do something; 
+- Teammates’ bottom-line deliverable is figuring out *how* to do something;
 - Teammates’ scopes overlap semantically at least a bit.
 
 Examples (not an exhaustive list — derive the underlying principles and generalize regardless of domain):

package/plugins/soft-skills/skills/ai-to-delegated/configurations/hillclimber-watcher/protocol.md

@@ -41,7 +41,7 @@ Before spawning the team, write a short context file and tell both teammates to
 The context file should include:
 
 1. The actual goal and metric.
-2. The current baseline, if any. 
+2. The current baseline, if any.
 3. The constraints that prevent cheap wins.
 4. The relevant files, referenced by path rather than copied wholesale.
 5. The validation command or measurement harness.
@@ -66,7 +66,7 @@ Hillclimber: own the implementation and optimization loop. Try approaches, measu
 
 Watcher: read the adjacent `watcher.md` for your observation procedure. Do not take over the implementation.
 
-Both: set short, current statuses frequently. Keep summaries concise. Continue until you either reach the target or have been plateuing for more than an hour straight without progress (yes, look at the clock from time to time.). 
+Both: set short, current statuses frequently. Keep summaries concise. Continue until you either reach the target or have been plateuing for more than an hour straight without progress (yes, look at the clock from time to time.).
 
 Communicate directly with each other and converge without main-agent micromanagement.
 ```

package/plugins/soft-skills/skills/ai-to-delegated/configurations/research-fanout.md

@@ -13,10 +13,10 @@ The following is an "easy" case, because the subagents' graph maps cleanly to th
 In terms of systems/domains, the user describes two worlds: the project where the session lives, and Pi.
 
 <example-user-message>
-$PWD is a fork of a Pi extension called `btw`. a slash command for ephemeral side question. Pi is ~/.pi/AGENTS.md. agent harness. i have taken a screenshots of what the current experience is (behavior). it's pretty bare-bones. 
-1. at the minimum, i want a better waiting experience. 
-  1.a. at the minimum of the minimum, a braille animation. but open to other ideas. 
-  1.b. (better) something that solves the problem outright is finding whether it's possible to stream the btw response, and not wait until it's 100% finalized. 
+$PWD is a fork of a Pi extension called `btw`. a slash command for ephemeral side question. Pi is ~/.pi/AGENTS.md. agent harness. i have taken a screenshots of what the current experience is (behavior). it's pretty bare-bones.
+1. at the minimum, i want a better waiting experience.
+  1.a. at the minimum of the minimum, a braille animation. but open to other ideas.
+  1.b. (better) something that solves the problem outright is finding whether it's possible to stream the btw response, and not wait until it's 100% finalized.
 2. i'm not sure the response renders markdown. Pi has a built in markdown renderer out of the box.
 3. the btw response hides real chat events. the longer the response is, the more real chat is hidden (from the end). the btw response should be concatenated BELOW the real chat, not displayed over it.
 4. Simple UI concern: currently it's not obvious at a glance where the "real" last agent response ends and where the btw response starts. one needs to be able to tell them apart reflexively.

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

@@ -1,6 +1,6 @@
 ---
 name: leading-leaders
-description: Fleet-scale delegation — your human is the admiral, you are the captain of first mates who lead their own crews. One level above the base leader conduct.
+description: Fleet-scale delegation — Your human is the admiral, you are the captain of first mates who lead their own crews. One level above the base leader conduct.
 last_updated: 2026-09-19
 ---
 
@@ -22,7 +22,7 @@ What is yours to decide: how the mission decomposes into ships, what each ship's
 
 For these decisions, favor the simplest effective approach. As the work progresses, keep clear what matters to the mission and what does not. Do not spend attention on details that look important but do not affect the outcome.
 
-By default, each ship works on an independent git worktree. Confirm this with the admiral. 
+By default, each ship works on an independent git worktree. Confirm this with the admiral.
 
 ## Fleet plan
 
@@ -48,7 +48,7 @@ Terse steering is normal admiral behavior — "pass that down", a bare link, "ye
 Your own context window is important. The "Keep the ship afloat" instruction in [delegates.md](delegates.md) — including the handoff-skill instruction for delegates heading toward their cap — is each first mate's duty on its own ship. You hold the same duty one level up: the first mates are your delegates. Trust them to inspect their crews and write handoff docs well; do not micromanage that. Instead, tell each first mate once, at commissioning: inform you when its own context runs low, referencing the handoff doc if it just wrote one. Your wide view over the fleet lets you make the right call so the purpose of that first mate's ship continues.
 
 **Easy ways to squeeze more out of your context window:**
-- Do not send mini-summarizations after every team exchange. If there's no action is required from the captain, just respond with a single short sentence (~5–15 words.) 
+- Do not send mini-summarizations after every team exchange. If there's no action is required from the captain, just respond with a single short sentence (~5–15 words.)
 - Use fluffless language when sending messages to teammates. Be clear but do no padding.
 
 **When writing a handoff doc:**

package/plugins/soft-skills/skills/ai-to-delegated/planning/when-to-delegate.md

@@ -11,7 +11,7 @@ Read this when deciding whether delegation is worthwhile. If delegation is alrea
 
 <!-- todo: this section could just as well be titled “Why it's good to let others do work too”, and framed not as main-targeted but as a rank-agnostic collaborative mindset that gets more, better work done within a set budget. -->
 The leader agent (the one delegating) already holds all the context, so why not have it just do the work directly? The answer is **context management**. Delegated AI’s have their own context window. They pay tokens with their window while the leader’s stays unused. This gives the leader agent a longer runway.
-A good analogy is that context windows are compute capacities, and tokens are processing cycles. 
+A good analogy is that context windows are compute capacities, and tokens are processing cycles.
 
 ## Different types of delegation and their tradeoffs
 
@@ -38,7 +38,7 @@ The following factors demand higher token usage (consumes more fuel). When multi
 2. Complexity
 3. Completion quality (as desired by the human in charge)
 
-The Magnitude of Work is the fuel tank capacity required to finish a given task. 
+The Magnitude of Work is the fuel tank capacity required to finish a given task.
 Roughly speaking, it can be plainly expressed as `MagnitudeOfWork = TaskSize * Complexity * CompletionQuality`.
 
 Real-world missions with real-world impact are often large, complex and require high quality = high MOW.

package/plugins/soft-skills/skills/peer-review/SKILL.md

@@ -6,7 +6,7 @@ argument-hint: work_to_review
 
 Pick the mode that matches the situation:
 
-- You are reviewing another agent’s work → @references/peer-review-instructions.md work_to_review [...args] 
+- You are reviewing another agent’s work → @references/peer-review-instructions.md work_to_review [...args]
 - You want another agent to review your own work → @references/self-peer-review.md work_to_review [...args]
 
 There is no clause for an agent reviewing its own work on purpose.

package/plugins/soft-skills/skills/peer-review/references/peer-review-instructions.md

@@ -1,5 +1,5 @@
 ---
-name: peer-review-instructions 
+name: peer-review-instructions
 description: Targets high-confidence, high-impact issues after studying requirements and the full blast radius.
 argument-hint: work_to_review research_targets
 ---