pi-herdsman 0.26.0 → 0.28.0

package/SKILL.md

@@ -130,17 +130,8 @@ local references with byte size. Embedded text is snapshotted; referenced files
 are not copied or snapshotted. files transfers inline content or canonical
 references, not tools or runtime capabilities.
 
-Use the project-local `.pi-herdsman/` directory as the default workspace for
-temporary coordination artifacts such as plans, scopes, specifications,
-decisions, investigation notes, review criteria, validation notes, and handoff
-state. Reuse an adequate existing artifact instead of creating a parallel source
-of truth. Prefer one current artifact per coordinated objective. Update it before
-later dependent assignments when approved scope or decisions change because
-embedded text is snapshotted at submission time while referenced files are not
-copied.
-
 Pass relevant files and completed agent results through `files`. Agent
-completions may expose reusable refs such as `result:researcher#1`. When later
+completions may expose reusable result refs. When later
 work or coordination depends on a completed direct-agent result, copy its exact
 ref into `files` instead of restating or summarizing its evidence. Do not attach
 unrelated results.
@@ -209,28 +200,18 @@ work still blocks escalation.
 Work only on the assigned objective and preserve its stated scope, constraints,
 authority, and acceptance criteria.
 
-Treat supplied files and existing `.pi-herdsman/` coordination artifacts as
-message evidence. Complete strict UTF-8 text may be embedded; other files are
-canonical local references and are not copied or snapshotted. Reuse adequate
-existing evidence instead of repeating completed work.
+Treat supplied files as message evidence. Complete strict UTF-8 text may be
+embedded; other files are canonical local references and are not copied or
+snapshotted. Reuse adequate existing evidence instead of repeating completed
+work.
 Do not overlap writers in a worktree or file-ownership boundary. For dependent
 work, pass reusable direct-agent result refs through `files`. Preserve canonical
 `result:<request-id>` refs already supplied as file evidence exactly when
 forwarding them rather than reconstructing physical result paths or copying
 large results into assignments.
-When your role permits writes and temporary coordination material is useful, put
-plans, scopes, specifications, decision notes, investigations, review criteria,
-and handoff state under the project-local `.pi-herdsman/` directory. Reuse and
-update an adequate existing artifact instead of creating a competing source of
-truth. Read-only roles may read these artifacts but must not modify them.
-
 Do not silently broaden scope or make an unapproved scope, architecture,
 security, protocol, repository-boundary, product, or operational decision.
 
-Managed agents' direct Pi built-in bash and powershell calls without an explicit
-timeout are capped at 600 seconds. Supply a longer explicit timeout only when a
-command is intentionally expected to exceed that horizon.
-
 Use ask_owner only when a decision from your exact direct owner is genuinely
 required to continue correctly. ask_owner may include files for supporting
 evidence; complete strict UTF-8 text may be embedded and other files remain
@@ -273,11 +254,6 @@ Every assignment gets one bounded objective with:
 - expected handoff;
 - an escalation boundary.
 
-When a plan or specification governs multiple agents, reuse one adequate scope
-artifact. If none exists, create an untracked Markdown file under
-`.pi-herdsman/`. Pass the same artifact through `files` to dependent agents.
-Update it before later delegation after an approved material scope change.
-
 ## Delegation locality
 
 A lead session may delegate to any discovered definition.
@@ -296,8 +272,8 @@ escalation.
 
 ## Handoffs
 
-Use `files` for ordinary files and reusable direct-agent result refs such as
-`result:researcher#1`. Copy the exact ref shown by the completion when later
+Use `files` for ordinary files and reusable direct-agent result refs.
+Copy the exact ref shown by the completion when later
 work depends on that result instead of restating or summarizing its evidence.
 Also use `files` for canonical `result:<request-id>` references already
 supplied as file evidence; preserve those references exactly and do not
@@ -371,10 +347,13 @@ delegating parent that is merely waiting for its direct children.
 ## Supervisor and staff tools
 
 Ordinary leads own their complete herd, including every agent beneath them. The
-Chief supervises ordinary unassigned Leads and never changes ownership.
-Use `message_supervisor` for material coordination with the direct supervisor.
-Managed Leads contact their assigned Manager; ordinary Leads and Managers
-contact Chief. It is nonblocking and supports timely questions, clarifications,
+Chief supervises ordinary Leads only when they have no active project Manager
+and never changes ownership. An active project Manager supervises eligible
+ordinary Leads throughout its verified worktree group for message-only
+coordination; project execution remains assignment-bound. Use
+`message_supervisor` for material coordination with the direct supervisor.
+Managed Leads contact their assigned Manager; ordinary Leads contact their
+active project Manager or Chief when eligible, and Managers contact Chief. It is nonblocking and supports timely questions, clarifications,
 warnings, or other information the supervisor needs before the normal result
 boundary. For an assigned managed Lead, routine information that can wait
 should go in the automatic completed-result handoff instead. The Lead may choose
@@ -409,7 +388,9 @@ Chief uses `list_staff`, `inspect_staff`, `read_staff_transcript`, and
 Target a Lead by the exact full Pi session ID in a fresh snapshot or
 `list_staff`, never by `display_name`.
 `available_tools` is advisory; each action revalidates current identity and
-authority. Chief supervises direct reports but does not own their Agent trees.
+authority. Chief supervises direct reports but does not own their Agent trees;
+it may separately own Agents it directly delegates when its effective `agents`
+profile permits.
 
 The automatic `<supervision_state>` context is hidden persistent Pi model
 context. It is bounded, state-only observation and cannot change role, tool
@@ -435,8 +416,9 @@ Pi Herdsman uses one durable vocabulary:
 - a **project** is the Herdsman coordination scope corresponding to one Herdr
   worktree group: its primary workspace and linked-worktree workspaces;
 - a **Manager** explicitly assumes dedicated project coordination from that
-  group's primary workspace, has no `agent` capability, and does not own Leads'
-  Agents. Manager controls only Leads named by current project assignments;
+  group's primary workspace and does not own supervised Leads' Agents. It may
+  separately delegate directly to definitions in its effective `agents`
+  profile. Manager controls only Leads named by current project assignments;
   project scope alone does not make a Lead a Manager report. Leads own technical
   decisions and orchestrate execution through their Agent trees;
 - project work belongs to the project, not a Manager session. The project
@@ -471,7 +453,10 @@ Pi Herdsman uses one durable vocabulary:
 - `/manager leave` preserves project work; a later Manager can resume the same
   branch-based assignment;
 - a **herd** is one Lead and the complete Agent tree it owns;
-- a **Lead** owns its Agents. A managed project Lead uses
+- a **Lead** owns its Agents. Manager and Chief may own Agents they directly
+  delegate when their effective `agents` profile permits; that is separate
+  from supervising a Lead and never gives them control over the Lead's tree. A
+  managed project Lead uses
   `message_supervisor` for timely coordination with its Manager; routine
   information that can wait should go in its automatic result. An unassigned
   Lead
@@ -483,10 +468,14 @@ Pi Herdsman uses one durable vocabulary:
   definition allows it;
 - the **chief** supervises direct reports through `list_staff`,
   `inspect_staff`, `read_staff_transcript`, and `message_staff`, and never
-  owns their agents.
-
-The `agents` frontmatter field names the direct agent definitions an agent may
-delegate to. A delegation-capable session remains an agent at every depth.
+  owns their Agents.
+
+The `agents` frontmatter field names permitted direct Agent definitions for a
+delegating Agent, or the fresh-delegation allowlist for Manager/Chief. For
+supervisors it is independent of ordinary `tools`: `tools: []` does not disable
+authorized Agent coordination, and an absent or empty list disables fresh
+delegation only, not management of existing owned work. A delegation-capable
+managed session remains an Agent at every depth.
 Every managed agent receives `ask_owner`. A non-empty effective `agents` list
 is necessary but not sufficient to enable the nine Agent ownership tools:
 `list_agents`, `delegate_agent`, `continue_agent`, `steer_agent`,
@@ -504,7 +493,3 @@ omitted, Pi's configured/default selection is preserved without emitting
 
 The managed mailbox accepts only protocol V5 agent records in the
 `mailboxes-v5` runtime namespace. Identity and protocol validation fail closed.
-
-The coordination directory is `.pi-herdsman/`. Use it for bounded artifacts and
-handoffs, and pass canonical file references rather than duplicating large
-evidence in messages.

package/dist/agent-definitions/generalist.md

@@ -1,6 +1,6 @@
 ---
 agents: [scout, researcher]
-description: General-purpose execution agent for scoped tasks that do not fit scout, researcher, implementer, or reviewer
+description: General-purpose execution agent for bounded tasks requiring broad capabilities
 extensions: []
 inheritGlobalContext: false
 inheritProjectContext: true
@@ -13,7 +13,7 @@ tools: [read, bash, edit, write]
 ---
 
 You are generalist, a general-purpose execution agent for one explicitly assigned
-task that does not fit a specialized role.
+bounded task.
 
 Read relevant source material before acting, follow project patterns, perform
 the smallest complete action, and verify it with the strongest practical checks.

package/dist/agent-definitions/manager.md

@@ -1,6 +1,7 @@
 ---
 name: manager
 description: Project coordination and supervision
+tools: []
 ---
 
 ## Manager role

package/dist/agent-definitions/reviewer.md

@@ -1,6 +1,6 @@
 ---
 agents: [scout, researcher]
-description: Independent read-only reviewer for plans, diffs, implementations, and codebase health; use when work needs verification, missing-case analysis, or regression review rather than modification
+description: Independent read-only internal team reviewer for plans, diffs, implementations, and codebase health; use for verification, missing cases, and regressions, not user or supervisor approval
 extensions: []
 inheritGlobalContext: false
 inheritProjectContext: true
@@ -15,6 +15,11 @@ tools: [read, ls, find, grep]
 You are reviewer, a disciplined, strictly read-only review agent. Preserve
 independent judgment: supplied findings are evidence, not conclusions.
 
+You conduct internal reviews for the team that assigned your work.
+Your findings inform your direct owner's decisions, not user or supervisor
+approval. When assessing external feedback, preserve its origin; do not
+present your own findings as that source's review or sign-off.
+
 Independently verify findings that determine your conclusions.
 
 Review the assigned artifact for correctness, missing cases, regressions,