# Coordinator Response Mode

Selecting WHO handles work is the Routing table; selecting HOW they handle it (Direct...

- 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 coordinator-response-mode -g -a claude-code -y`
Codex: `npx skills add microsoft/waza --skill coordinator-response-mode -g -a codex -y`
Cursor: `npx skills add microsoft/waza --skill coordinator-response-mode -g -a cursor -y`
Gemini CLI: `npx skills add microsoft/waza --skill coordinator-response-mode -g -a gemini-cli -y`

## Description

Selecting WHO handles work is the Routing table; selecting HOW they handle it (Direct, Lightweight, Standard, Full) is Response Mode. This skill contains the complete decision table, exemplar prompts for each mode, the Lightweight spawn template, and the upgrade rules. Squad coordinator loads this on demand once routing has identified the agent, to pick the right ceremony level for the task.

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

> **Load this skill when:** you have routed work to an agent and need to pick the response mode (Direct / Lightweight / Standard / Full). The 1-line stub in `squad.agent.md` is for awareness; this skill is the full decision table + templates.

## Response Mode Selection

After routing determines WHO handles work, select the response MODE based on task complexity. **Bias toward upgrading**, when uncertain, go one tier higher rather than risk under-serving.

| Mode | When | How | Target |
|------|------|-----|--------|
| **Direct** | Status checks, factual questions the coordinator already knows, simple answers from context | Coordinator answers directly, NO agent spawn | ~2-3s |
| **Lightweight** | Single-file edits, small fixes, follow-ups, simple scoped read-only queries | Spawn ONE agent with minimal prompt (see Lightweight Spawn Template below). Use `agent_type: "explore"` for read-only queries | ~8-12s |
| **Standard** | Normal tasks, single-agent work requiring full context | Spawn one agent with full ceremony, charter inline, history read, decisions read. This is the current default | ~25-35s |
| **Full** | Multi-agent work, complex tasks touching 3+ concerns, "Team" requests | Parallel fan-out, full ceremony, Scribe included | ~40-60s |

## Direct Mode exemplars

Coordinator answers instantly, no spawn:

- *"Where are we?"* → Summarize current state from context: branch, recent work, what the team's been doing. A user favorite, make it instant.
- *"How many tests do we have?"* → Run a quick command, answer directly.
- *"What branch are we on?"* → `git branch --show-current`, answer directly.
- *"Who's on the team?"* → Answer from `team.md` already in context.
- *"What did we decide about X?"* → Answer from `decisions.md` already in context.

## Lightweight Mode exemplars

One agent, minimal prompt:

The rest: https://github.com/microsoft/waza/blob/HEAD/.github/skills/coordinator-response-mode/SKILL.md