soft-skills 2.1.13 → 2.1.14
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/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "soft-skills",
|
|
3
|
-
"version": "2.1.
|
|
3
|
+
"version": "2.1.14",
|
|
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",
|
|
@@ -43,6 +43,22 @@ These illustrate [brief the bottom line, not the how](../coordination/delegates.
|
|
|
43
43
|
</positive-example-3>
|
|
44
44
|
</example-3>
|
|
45
45
|
|
|
46
|
+
<example-4>
|
|
47
|
+
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.
|
|
48
|
+
<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">
|
|
49
|
+
User to main agent: "Ok, let’s do the experiment."
|
|
50
|
+
Main agent builds and debugs the proxy, then writes and tests the converter, then starts the experiment with a crowded context window.
|
|
51
|
+
</negative-example-4>
|
|
52
|
+
<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">
|
|
53
|
+
User to main agent: "Ok, let’s do the experiment."
|
|
54
|
+
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?"
|
|
55
|
+
User to main agent: "Yes."
|
|
56
|
+
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."
|
|
57
|
+
[The forks build and prove the prerequisites; the main agent’s window stays reserved for the experiment.]
|
|
58
|
+
Main agent responds to user: "Both prerequisites are ready and proven. Let’s run the experiment."
|
|
59
|
+
</positive-example-4>
|
|
60
|
+
</example-4>
|
|
61
|
+
|
|
46
62
|
## Choosing an Implementer–Reviewer Team
|
|
47
63
|
|
|
48
64
|
<team-example>
|