@giladbarnea/pi-simple-team 2.0.5 → 2.0.7
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 +20 -12
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -6,12 +6,14 @@
|
|
|
6
6
|
|
|
7
7
|
> **The team extension with no features.**
|
|
8
8
|
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
9
|
+
<p align="center">
|
|
10
|
+
<a href="https://github.com/earendil-works/pi"><img alt="Pi extension" src="https://shieldcn.dev/badge/pi-extension.svg?variant=outline" /></a>
|
|
11
|
+
<a href="https://www.npmjs.com/package/@giladbarnea/pi-simple-team"><img alt="npm version" src="https://shieldcn.dev/npm/%40giladbarnea%2Fpi-simple-team.svg?variant=outline" /></a>
|
|
12
|
+
<a href="https://github.com/giladbarnea/pi-simple-team/actions/workflows/test.yml"><img alt="test status" src="https://shieldcn.dev/github/ci/giladbarnea/pi-simple-team.svg?workflow=test.yml&branch=main&variant=outline" /></a>
|
|
13
|
+
<a href="LICENSE"><img alt="license" src="https://shieldcn.dev/github/license/giladbarnea/pi-simple-team.svg?variant=outline" /></a>
|
|
14
|
+
<a href="https://www.typescriptlang.org/"><img alt="TypeScript" src="https://shieldcn.dev/badge/typescript.svg?logo=typescript&variant=outline" /></a>
|
|
15
|
+
<a href="https://bun.sh/"><img alt="tested with Bun" src="https://shieldcn.dev/badge/tested_with-Bun.svg?logo=bun&variant=outline" /></a>
|
|
16
|
+
</p>
|
|
15
17
|
|
|
16
18
|
**No roles. No org chart. No mailboxes. No routing rules.**
|
|
17
19
|
|
|
@@ -57,7 +59,9 @@ You:
|
|
|
57
59
|
> Create an implementer-reviewer team to complete `PLAN.md`.
|
|
58
60
|
|
|
59
61
|
Main agent:
|
|
60
|
-
>
|
|
62
|
+
> Created an `implementer` and `reviewer` loop:
|
|
63
|
+
> - `implementer` will keep fixing until `reviewer` is satisfied.
|
|
64
|
+
> - I will let you know when they are done.
|
|
61
65
|
|
|
62
66
|
[](screenshots/abstract-tool-output-preview.png)
|
|
63
67
|
|
|
@@ -71,10 +75,10 @@ Main agent:
|
|
|
71
75
|
<br>
|
|
72
76
|
|
|
73
77
|
<p align="center">
|
|
74
|
-
<a href="screenshots/team-status-multiple.png"><img src="screenshots/team-status-multiple.png" width="
|
|
78
|
+
<a href="screenshots/team-status-multiple.png"><img src="screenshots/team-status-multiple.png" width="100%" alt="Status outputs for several parallel teams"></a>
|
|
75
79
|
</p>
|
|
76
80
|
<p align="center">
|
|
77
|
-
<a href="screenshots/team-log-multiple.png"><img src="screenshots/team-log-multiple.png" width="
|
|
81
|
+
<a href="screenshots/team-log-multiple.png"><img src="screenshots/team-log-multiple.png" width="100%" alt="Event log outputs for two parallel teams"></a>
|
|
78
82
|
</p>
|
|
79
83
|
|
|
80
84
|
</details>
|
|
@@ -169,7 +173,7 @@ This means **teammates (and thus, teams) survive shutdown.**
|
|
|
169
173
|
|
|
170
174
|
Have a teammate do work, exit Pi entirely, come back tomorrow in a brand-new session, and ask main to get you that teammate by its Pi session id. Everything it learned stays intact.
|
|
171
175
|
|
|
172
|
-
You can even `/resume` a teammate session directly if you ever want a cozy one-on-one
|
|
176
|
+
You can even `/resume` a teammate session directly if you ever want a cozy one-on-one, or run `pi --session <teammate-session-id>`.
|
|
173
177
|
|
|
174
178
|
## It’s teams all the way down (optionally)
|
|
175
179
|
|
|
@@ -189,9 +193,13 @@ This technique plays even nicer if your main assumes the captain rank[^1].
|
|
|
189
193
|
|
|
190
194
|
## 🧬 Graphs engineer themselves
|
|
191
195
|
|
|
192
|
-
**Because** it does nothing special, `pi-simple-team` can **construct any agentic graph you need
|
|
196
|
+
**Because** it does nothing special, `pi-simple-team` can **construct any agentic graph you need.**
|
|
197
|
+
|
|
198
|
+
Tell main:
|
|
199
|
+
> 1. Break `PLAN.md` into a task graph. Include loops with success criteria and run independent tasks in parallel.
|
|
200
|
+
> 2. Create a team that carries out that task graph.
|
|
193
201
|
|
|
194
|
-
|
|
202
|
+
Or give main a concrete team goal:
|
|
195
203
|
> **Team goal:**
|
|
196
204
|
> 1. Map the database for all customer ⟷ purchases money streams.
|
|
197
205
|
> 2. Feed the new knowledge into the memory layer.
|