# Cross Squad Communication

Protocol for sending queries, delegating tasks, and sharing context between independent...

- Repository: https://github.com/microsoft/waza (1496 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-31
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add microsoft/waza --skill cross-squad-communication -g -a claude-code -y`
Codex: `npx skills add microsoft/waza --skill cross-squad-communication -g -a codex -y`
Cursor: `npx skills add microsoft/waza --skill cross-squad-communication -g -a cursor -y`
Gemini CLI: `npx skills add microsoft/waza --skill cross-squad-communication -g -a gemini-cli -y`

## Description

Protocol for sending queries, delegating tasks, and sharing context between independent Squad instances across different repositories

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

## 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.md` covers **discovery** of peer squads via `squad 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.

---

## Patterns

### Decision Tree: Choosing the Right Pattern

The rest: https://github.com/microsoft/waza/blob/HEAD/.github/skills/cross-squad-communication/SKILL.md