Team Organization¶

This document is a visual index of the agent team. For behavioral details of each agent, see Agents. For orchestration mechanics, see Architecture.

Team Agents¶

Org chart showing the Orchestrator at the top, dispatching to ten team agents: Software Engineer, QA Engineer, UI/UX Designer, Architect, Product Manager, Technical Writer, Security Engineer, Platform Engineer, ADR Author, and Codebase Recon.

The Orchestrator sits at the root and routes every request to one or more of the ten team agents based on task classification. Only the Orchestrator spans phases; the other agents are loaded on demand when their phase begins and unloaded via summarization before the next phase starts. Full roster: Agents → Team Agents.

Review Agent Dispatch (Phase 3 Inline Checkpoints)¶

Dispatch diagram: a unit of work on the left, a file-type decision layer in the middle, and fan-out to targeted review agents on the right (e.g., JS/TS files → js-fp-review + complexity-review; Svelte → svelte-review; any change → arch-review + doc-review; security surface → security-review).

The Orchestrator selects review agents based on what changed in each unit of work. Language-agnostic agents (doc-review, arch-review, claude-setup-review, token-efficiency-review) always run; language-specific agents run only when matching file types are present. Full list of review agents and their scopes: Agents → Review Agents.

Special-purpose review agents¶

progress-guardian is a process gate-keeper, not a code reviewer — it is not in the standard review-dispatch fan-out above. It tracks plan-step completion and commit discipline, and is invoked by its owning orchestrator, never by /code-review.

/test-improve does not use a separate phase-gate agent; its per-phase progress files under memory/test-improve/<slug>/phase-<n>.md and its end-of-phase review loop (Phase 4 and Phase 5) carry the equivalent evidence contract.