# Squad Help

How to use the Squad coordinator agent and the separate squad menu skill, with...

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

## Install

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

## Description

How to use the Squad coordinator agent and the separate squad menu skill, with host-dependent discovery and slash-command support.

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

# Skill: squad-help

> **Quick reference.** If you're reading this because a user said "use squad" or "squad" or "set up a squad", you're in the right place, read on for the correct invocation paths.

---

## Squad coordinator and squad menu skill

The Squad framework registers a **custom Copilot CLI agent** at `.github/agents/squad.agent.md`. The agent is named **`Squad`** and its description is *"Your AI team. Describe what you're building, get a team of specialists that live in your repo."*

Copilot CLI agents and skills are different things:

| Thing | How to invoke | Example |
|---|---|---|
| **Menu skill** | Host skill tool, natural-language match, or exposed skill command | `skill(squad)` when available |
| **Agent** | `task` tool with `agent_type=<name>` | `task(name="...", agent_type="Squad", prompt="...")` |
| **Slash command** | Host-dependent built-in command or exposed user-invocable skill | `/squad` when the host exposes the installed menu |

The `Squad` agent performs coordination; the separate `squad` menu skill lives at
`.github/skills/squad/SKILL.md` and declares `user-invocable: true`. They are not
interchangeable. Slash-command availability is **host-dependent**: use `/squad` only
where the host exposes that skill as a command. Otherwise use its natural-language
triggers or the host's skill picker/tool, when available; invoke the coordinator agent
for actual orchestration.

---

## How to actually use Squad

Pick the path that matches the user's intent:

### A) Invoke the Squad coordinator agent (most common)

The Squad coordinator orchestrates a team of specialists. It routes work to the right agent, scaffolds a team if none exists, and enforces handoffs.

```text
task(
  name="<short-task-name>",
  agent_type="Squad",
  prompt="<what you want the team to do>"
)
```

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