Cross Squad Communication
Protocol for sending queries, delegating tasks, and sharing context between independent...
Install
npx skills add microsoft/waza --skill cross-squad-communication -g -a claude-code -y- Repository
- microsoft/waza1.5k
- Category
- Engineering
- Updated
- 4d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Protocol for sending queries, delegating tasks, and sharing context between independent Squad instances across different repositories
Context
When multiple repositories each have their own Squad (AI team), they need to exchange information: knowledge queries, PR reviews, task delegation, and dependency analysis. Each squad has its own agents, MCP tools, and issue tracker, there is no shared runtime.
Companion skill, read first:
cross-squad/SKILL.mdcovers discovery of peer squads viasquad registry add/list/remove. This skill picks up after a peer is known and covers the communication protocols themselves, the four numbered patterns below: Pattern 0 (synchronous CLI), Pattern 1 (read-only knowledge query), Pattern 2 (git-based async), and Pattern 3 (GitHub-issue-based delegation). A separate non-numbered appendix (Cross-Repo Dependency Scan) is provided as a related analysis tool, not a communication pattern. The two skills are designed to be used together.
When this skill applies:
- A squad agent needs information from another squad-enabled repo
- A task needs to be delegated to another squad
- Cross-repo dependency analysis is needed
- PR review requests span repo boundaries
Key constraint: Each squad has its own runtime, MCP tools, and issue tracker. Cross-squad communication can be synchronous (via CLI session targeting the other repo) or asynchronous (file-based or issue-based). The coordinator decides which approach fits.
