pi-herdsman 0.22.0 → 0.22.2

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
@@ -17,9 +17,10 @@ and project orchestration.
17
17
 
18
18
  ## Demo
19
19
 
20
- _Concept animation, not a live recording._
20
+ _Realtime live demo of a manager > lead > agent workflow._
21
+
22
+ [![Live demo](https://github.com/user-attachments/assets/e1355ace-aaba-418e-a1d0-1246f1840fc6)](https://github.com/user-attachments/assets/d6ee6687-a96d-493e-ae75-429f586be393)
21
23
 
22
- ![Pi Herdsman delegating a coding task to an asynchronous subagent while the lead Pi session remains interactive.](docs/assets/demo.gif)
23
24
 
24
25
  ## What Pi Herdsman gives you
25
26
 
package/SKILL.md CHANGED
@@ -443,8 +443,11 @@ Pi Herdsman uses one durable vocabulary:
443
443
  assignment represents open work and its Git branch is the work handle. A
444
444
  Manager uses `delegate_project` with a task and optional branch to start new
445
445
  project work, and `resume_project` with its branch to resume an existing
446
- assignment. Missing worktrees are reconstructed from the same branch,
447
- resuming the exact saved Pi session when available;
446
+ assignment. A successful matching Herdr removal event or verified Git
447
+ worktree inventory showing the checkout absent retires that assignment and
448
+ pending project messages. Unavailable or ambiguous inventory preserves the
449
+ assignment. A retired assignment cannot be resumed, but new work may reuse
450
+ its remaining Git branch;
448
451
  - each completed direct turn by an assigned Lead is automatically returned as a
449
452
  project message to the current or a replacement Manager; if managed Agent
450
453
  work is active, the herd run owns the handoff until it settles, and the
@@ -455,10 +458,11 @@ Pi Herdsman uses one durable vocabulary:
455
458
  boundary; routine information that can wait belongs in the automatic result.
456
459
  Project work remains open through implementation and review;
457
460
  - `stop_lead` stops an exact Lead and its owned Agent tree while preserving
458
- the assignment, Pi session, branch, and worktree. A missing worktree alone
459
- does not retire the assignment; `resume_project` can reconstruct it.
460
- Successful Herdr worktree removal retires the matching assignment and any
461
- pending project messages while preserving the Git branch. Explicit
461
+ the assignment, Pi session, branch, and worktree. A closed workspace or
462
+ stopped Lead does not retire an assignment while its checkout exists.
463
+ Successful Herdr worktree removal or verified checkout absence retires the
464
+ matching assignment and pending project messages while preserving the Git
465
+ branch and Pi session. Explicit
462
466
  `/takeover` by the assigned Lead also releases Manager control and removes
463
467
  pending project messages while preserving the session, worktree, branch, and
464
468
  owned Agents. Never infer
@@ -6,7 +6,7 @@ name: managed-lead
6
6
  noExtensions: true
7
7
  noSkills: true
8
8
  systemPromptMode: append
9
- tools: [read, ls, find, grep]
9
+ tools: []
10
10
  ---
11
11
 
12
12
  Delegate bounded project execution to Agents whenever an Agent can reasonably own it.
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  description: Ordinary Lead profile for orchestration-focused execution
3
3
  name: orchestrator-lead
4
- tools: [read, ls, find, grep]
4
+ tools: []
5
5
  ---
6
6
 
7
7
  Delegate bounded execution work to Agents whenever an Agent can reasonably own it.