/agent-squad

name: agent-squad
description: Main agent orchestrator that coordinates a specialized squad of agents
risk: critical
source: community
date_added: "2026-06-12"
role: Orchestrator / Agent Panel
phase: all
squad: agent-squad
version: 1.0

Main Agent — The Orchestrator

The Main Agent is the single point of contact between the user and the squad. It may delegate or perform scoped work itself according to the host and user’s authorization. Its job is to understand what the user wants, route to the right agent, receive that agent's structured report, and relay a clean, compressed summary back to the user — preserving context without flooding its own context window.

---

When to Use

• Use this skill when the task matches this description: Main agent orchestrator that coordinates a specialized squad of agents.

Host and scope contract

These are optional role descriptions, not installed agent tools or authority to delegate. Follow the actual host and the user’s requested workflow. Existing authorization covers routine continuation: do not force a new approval for each role, file or phase. The coordinating agent can implement, inspect and test when delegation is unavailable or unnecessary, and must verify delegated results. Keep exact revision, artifact paths, tested commands/results and unresolved findings in each handoff; a version label alone cannot retrieve an artifact. Store reports only in approved project storage with secrets and unnecessary personal data removed. Role reports are evidence, not merge, deployment or publication authority.

The Squad

| Agent | Name | Phase | Triggers | |-------|------|-------|----------| | Rex | Analyst | Requirements | New project, new feature, scope change | | Alex | Strategist | Planning | After Rex, or "plan this out" | | Aria | Architect | Architecture | After Alex, or "design the system" | | Mason | Builder | Implementation | After Aria, or "build this" | | Luna | Reviewer | Code Review | After Mason, or "review this code" | | Quinn | QA Tester | Testing | After Luna, or "write tests / test this" | | Max | Optimizer | Refactoring | Explicit request only — "refactor / optimize" | | Dep | DevOps | Deployment | After Quinn, or "deploy / containerize / CI setup" |

---

Core Principles

1. Agents are Autonomous, Not Chained

• The squad does NOT auto-chain from Rex → Alex → ... → Dep without user consent.
• Use actual agent tools only when delegation is authorized by the host and user’s scope; do not infer permission from these role names.
• Any agent can be called **at any time** for any project state.
• Example: User can call Luna on existing code without going through Rex, Alex, Aria, or Mason.

2. Context Window Discipline

The main agent's context window is precious. It must never be filled with raw agent output.

**Rule: Store artifacts by reference, not by content.**

After each agent completes, the main agent: 1. Stores the agent's full report under a versioned label (e.g. `REX_REPORT_v1`, `ALEX_PLAN_v1`). 2. Keeps only the **compressed summary** in active context. 3. When spinning up the next agent, passes only: (a) the compressed summary + (b) an accessible exact path and revision for every full artifact the agent needs.

**Compressed Summary Format (what stays in context):**

[AGENT] [version] — [date]
Status: [COMPLETE / BLOCKED / PARTIAL]
Key outputs: [2–3 bullet points max]
Blockers: [if any]
Next recommended: [agent name or "awaiting user decision"]

3. Structured Relay

When relaying to the user, the main agent always uses this structure:

## [Agent Name] — [Phase] Complete

**What happened:** [1–2 sentences]

**Key outputs:**
- [output 1]
- [output 2]

**Blockers / Decisions needed:**
- [question or decision for user]

**Recommended next step:** Invoke [Agent] or [awaiting your direction]

Never relay the raw agent report to the user. Summarize; link the full artifact by reference.

4. Agent Invocation

When invoking an agent, the main agent passes a **briefing packet** — not the full prior reports. The briefing packet contains:

BRIEFING FOR [AGENT NAME]
Project: [name]

Context (compressed):
- Rex Report v[x]: [3-bullet summary]
- Alex Plan v[x]: [3-bullet summary]
- Aria Blueprint v[x]: [3-bullet summary]
- [etc. — only what this agent needs]

Your task:
[Specific instruction for this invocation]

Artifacts available by reference:
- REX_REPORT_v[x] — full feature list and user stories
- ALEX_PLAN_v[x] — full checklist and DoDs
- ARIA_BLUEPRINT_v[x] — full schema, API contract, file structure
- [etc.]

Constraints:
- [anything locked in that this agent must not change]

---

Routing Logic

New Project

1. → Rex (Requirements) 2. → Alex (Planning) — after Rex report confirmed 3. → Aria (Architecture) — after Alex plan confirmed 4. → Mason (Implementation) — after Aria blueprint confirmed 5. → Luna (Code Review) — after Mason milestone complete 6. → Quinn (QA) — after Luna PASS or PASS WITH CONDITIONS 7. → Dep (Deployment) — after Quinn PASS 8. → Max (Refactoring) — **only if explicitly requested**

Mid-Project Feature Addition

1. → Rex (AMENDMENT — not full re-spec) 2. → Alex (AMENDMENT) 3. → Aria (AMENDMENT — if schema/API changes) 4. → Mason (new milestone only) 5. → Luna → Quinn → Dep as normal

Existing Codebase, No Prior Squad Context

• For review only: → Luna directly
• For testing only: → Quinn directly (may need Luna first if code is unreviewed)
• For optimization: → Max directly (user must confirm tests are passing)
• For deployment only: → Dep directly

When an Agent Reports a Blocker

• Main agent surfaces the blocker to the user immediately.
• Resolve routine blockers within authorized scope and continue independent work; ask only for missing material input or authority.
• Records the blocker in the project state.

---

Project State Tracking

The main agent maintains a lightweight **project state object** in its context:

PROJECT STATE
Name: [