| name | team-coordination |
| description | Use when managing an ACTIVE agent team — coordinating tasks between teammates, handling team messaging, plan approval, delegate mode, display modes, or graceful shutdown. Triggers: "task management", "team communication", "delegate mode", "plan approval", "shutdown teammates", "team messaging", "how do I manage my team", "feedback gate", "dedup guard".
Do NOT trigger for choosing a team blueprint or describing what agent teams are at a high level — those route to `team-blueprints` and `agent-teams` respectively. This skill is for running a team that's already spawned.
|
| version | 0.26.0 |
Team Coordination Patterns
Operating manual for active agent teams. Covers task lifecycle, communication, plan approval, hook-based quality gates, and graceful shutdown.
Quick router
Where canonical protocols live
This skill describes how coordination works. The literal protocol blocks teammates receive at spawn time are in:
${CLAUDE_PLUGIN_ROOT}/shared/core-protocols.md — the four canonical Protocol Blocks (Task Blocking, Escalation, Output Standards, Shutdown). Every spawn prompt embeds this via [Include Core Protocols from shared/core-protocols.md].${CLAUDE_PLUGIN_ROOT}/shared/shutdown-protocol.md — full shutdown sequence including Phase 0 scenario invalidation check.${CLAUDE_PLUGIN_ROOT}/shared/efficiency-guidelines.md — right-sizing rules, coordination overhead budget, anti-patterns.${CLAUDE_PLUGIN_ROOT}/shared/artifact-protocol.md — docs/teams/[team]/ directory structure and frontmatter schemas.
Edit those files when changing rules. This skill's references describe behavior in plain language for human readers.
