@giladbarnea/pi-simple-team 1.0.19 → 1.0.20

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 CHANGED
@@ -137,7 +137,7 @@ Teammates publish a one-liner:
137
137
 
138
138
  > <span style="color:grey">implementer  </span> Done, 89 tests green, awaiting review.
139
139
 
140
- > <span style="color:grey">reviewer      </span> Reading implementation, will finalize review in a few minutes"
140
+ > <span style="color:grey">reviewer      </span> Reading implementation, will finalize review in a few minutes.
141
141
 
142
142
  Your main agent calls `teamstatus` and understands exactly what's going on. Main doesn't ask and clutter the teammates' context.
143
143
 
package/child-tools.ts CHANGED
@@ -255,7 +255,6 @@ export function registerChildTools(pi: ExtensionAPI, config: ChildRuntimeConfig)
255
255
  name: "report_context_window",
256
256
  label: "Report Context Window",
257
257
  description: "Report your current context-window use.",
258
- promptSnippet: "Report your current context-window use",
259
258
  parameters: Type.Object({}),
260
259
  async execute(_toolCallId, _params, _signal, _onUpdate, context) {
261
260
  const text = formatContextWindowReport("You have", requireKnownContextUsage(context.getContextUsage()));
@@ -269,10 +268,6 @@ export function registerChildTools(pi: ExtensionAPI, config: ChildRuntimeConfig)
269
268
  name: "teamsend",
270
269
  label: "Team Send",
271
270
  description: "Send a message to teammate(s) (not main). To message the main agent, use teammain. Returns once the runtime accepts the send request, not after recipients reply.",
272
- promptSnippet: "Send a message to teammate(s)",
273
- promptGuidelines: [
274
- "Use teamsend to talk to teammates. From your POV (sender), it is fire-and-forget. From the recipient’s POV, it’s pushed to context as soon as possible.",
275
- ],
276
271
  parameters: Type.Object({
277
272
  to: Type.Array(Type.String(), { description: "Recipient teammate names" }),
278
273
  message: Type.String({ description: "Message to send" }),
@@ -290,8 +285,6 @@ export function registerChildTools(pi: ExtensionAPI, config: ChildRuntimeConfig)
290
285
  name: "teammain",
291
286
  label: "Team Main",
292
287
  description: "Send a message to the main agent.",
293
- promptSnippet: "Send a message to the main agent.",
294
- promptGuidelines: ["Use teammain to update or ask the main agent. Main agent sees the big picture and has been aware of the team’s actions and status updates since the team was created."],
295
288
  parameters: Type.Object({
296
289
  message: Type.String({ description: "Message to send to the main agent" }),
297
290
  }),
@@ -306,7 +299,6 @@ export function registerChildTools(pi: ExtensionAPI, config: ChildRuntimeConfig)
306
299
  name: "teamstatus",
307
300
  label: "Team Status",
308
301
  description: "Set your public status and read everyone's public status.",
309
- promptSnippet: "Set/read the public team status map",
310
302
  // TODO: If this typing system supports it, I want gerund and phrase optionality to be a XOR
311
303
  parameters: Type.Object({
312
304
  gerund: Type.Optional(Type.String({ description: "One-word gerund status." })),
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@giladbarnea/pi-simple-team",
3
- "version": "1.0.19",
3
+ "version": "1.0.20",
4
4
  "description": "A flat, live team of Pi agents.",
5
5
  "keywords": [
6
6
  "pi-package",
package/system-prompt.ts CHANGED
@@ -8,9 +8,12 @@ export function composeSystemPrompt(teamName: string, teamPrompt: string, teamma
8
8
  `You are ${teammateName}, a teammate on team ${teamName}.`,
9
9
  `Participants: main, ${participants.join(", ")}.`,
10
10
  "Use teamsend to talk to teammates, teammain to talk to the main agent, and teamstatus to set/read public statuses.",
11
+ "From the sender’s point of view, teamsend is fire-and-forget. From the recipient’s point of view, the message is pushed to context as soon as possible.",
12
+ "Main agent sees the big picture and has been aware of the team’s actions and status updates since the team was created.",
11
13
  "As soon as you wake up, call teamstatus to acknowledge that you received your instructions before doing substantive work.",
12
14
  "Whenever you receive a message from main or a teammate, call teamstatus first to acknowledge that specific message, then proceed.",
13
15
  "Never set a waiting status until after you have sent the teammate you are waiting for a teamsend describing exactly what you need from them.",
16
+ "If you are waiting, message the person you are waiting for. Ask them to wake you when the condition is met. Set your status to “waiting for X to wake me when Y is done”, then stay put.",
14
17
  "There is no inbox to poll and no done button. Coordinate naturally. If the team is done, one teammate should tell main via teammain.",
15
18
  ]
16
19
  .filter(Boolean)