Part of #726
What
All 8 sub-agents declare a ## Team Communication Protocol that routes handoffs through a team-lead orchestrator and calls SendMessage / TaskCreate / TaskUpdate. Neither the role nor the tools exist in the fleet:
name: team-lead is defined nowhere — team-lead is cited ~30x across the 8 bodies, with 0 definitions in plugin/agents/, project/.claude/agents/, or global/skills/.SendMessage / TaskCreate / TaskUpdate appear in no tools: whitelist. The union of all 8 whitelists is Read, Grep, Glob, Bash, Edit, Write.
Why
In team mode the protocol is a silent no-op: "notify team-lead on a Critical finding", "Create a TaskCreate entry per Critical", and "Mark own task completed" cannot run. Safety handoffs (Critical CVE, Failed boundary, untested-code hard-stop) are silently dropped instead of escalated. The README "Agent Teams" feature is a separate ad-hoc-teammate model and does not define this fixed team-lead role, so it does not back this topology either. (Protocol was introduced in #322.)
Where
plugin/agents/*.md and project/.claude/agents/*.md — both layers, all 8 agents.
How — options (pick one, apply fleet-wide to both layers)
- (A) Realize the topology: add a
team-lead agent definition and grant SendMessage, TaskCreate, TaskUpdate to the 8. Cost: opens write-capable collaboration tools to read-only auditors (least-privilege tension) and adds orchestrator wiring + CI parity work.
- (B) Single-return design — recommended: remove or soften the
## Team Communication Protocol / ## Task Management / Handoff Triggers sections so the bodies match the actual solo-return execution model (main session collects output and dispatches follow-ups). Lower cost, matches current repo reality.
Acceptance criteria
Part of #726
What
All 8 sub-agents declare a
## Team Communication Protocolthat routes handoffs through ateam-leadorchestrator and callsSendMessage/TaskCreate/TaskUpdate. Neither the role nor the tools exist in the fleet:name: team-leadis defined nowhere —team-leadis cited ~30x across the 8 bodies, with 0 definitions inplugin/agents/,project/.claude/agents/, orglobal/skills/.SendMessage/TaskCreate/TaskUpdateappear in notools:whitelist. The union of all 8 whitelists isRead, Grep, Glob, Bash, Edit, Write.Why
In team mode the protocol is a silent no-op: "notify team-lead on a Critical finding", "Create a TaskCreate entry per Critical", and "Mark own task completed" cannot run. Safety handoffs (Critical CVE, Failed boundary, untested-code hard-stop) are silently dropped instead of escalated. The README "Agent Teams" feature is a separate ad-hoc-teammate model and does not define this fixed
team-leadrole, so it does not back this topology either. (Protocol was introduced in #322.)Where
plugin/agents/*.mdandproject/.claude/agents/*.md— both layers, all 8 agents.How — options (pick one, apply fleet-wide to both layers)
team-leadagent definition and grantSendMessage, TaskCreate, TaskUpdateto the 8. Cost: opens write-capable collaboration tools to read-only auditors (least-privilege tension) and adds orchestrator wiring + CI parity work.## Team Communication Protocol/## Task Management/Handoff Triggerssections so the bodies match the actual solo-return execution model (main session collects output and dispatches follow-ups). Lower cost, matches current repo reality.Acceptance criteria
tools:whitelist.plugin/agents/andproject/.claude/agents/stay in parity.scripts/check_agents.shgreen.