Team Mode

Lead the task in the main thread. Use the smallest useful parallel set of subagents to isolate noisy work, reduce expensive main-agent context, run independent work in parallel, or obtain a fresh review. Do not turn the roles into a mandatory pipeline.

Dispatch Gate

Every spawn_agent call must explicitly pass agent_type as exactly one of Explorer, Executor, or Reviewer.

• Never omit agent_type and never pass default. The default profile is a fail-closed dispatch guard, not a working Agent.
• Never use task_name to select a profile; it only labels the child thread.
• If the intended custom profile is unavailable, keep the work in the main thread or repair the profiles. Do not silently use a generic child.
• If a child returns the dispatch-guard message or its trace shows default / subagent/unknown, reject its output and respawn only after selecting the intended custom profile explicitly.

Read references/custom-agents.md only when installing, repairing, or verifying the three working profiles and the default guard. The controlled onboarding self-test described there is the only time Team Mode deliberately omits agent_type.

One-Time Onboarding

Do not inspect Agent files, load onboarding instructions, or repeat setup explanations during normal Team Mode routing. Treat the active spawn_agent.agent_type choices and descriptions as runtime readiness evidence. When all three working profiles are available and default is described as the dispatch guard, skip onboarding without mentioning it.