Task statement 1.2 · Agentic architecture and orchestration
Orchestrate multi‑agent systems with coordinator‑subagent patterns
In the research system, the coordinator decides which subagents run and what each one is asked. When that decision is wrong, every subagent can succeed and the report still silently skips part of the topic.
share
When a report misses whole subtopics, the tempting fix is to broaden the queries of the subagent whose output looks thin. That fails when every subagent's output is correct, because the missing subtopics were never assigned to anyone. The same trust in the pipeline sends a one-fact question through all four subagents, which costs minutes and adds no coverage.
KnowledgeHub and spoke
Hub-and-spoke is an architecture in which the coordinator is the hub and each subagent sits on a spoke. The coordinator manages all communication, error handling and information routing, so search results reach synthesis only because it passes them on. Each subagent works in its own context window and does not inherit the coordinator's conversation history, so it knows only its prompt. Routing everything through the coordinator gives observability, because one log shows every delegation and result. It also gives consistent error handling and controlled information flow, because one agent decides what to retry and what each subagent sees.
KnowledgeWhat the coordinator decides, in order
The coordinator's role covers task decomposition, delegation, result aggregation, and deciding which subagents to invoke based on query complexity. Decomposition is its first split of the query into subtasks. Subagents cannot change it, because none of them sees the whole query. Only the coordinator can revise it, by reading the combined results for gaps and re-delegating, a loop called iterative refinement.
- Judge the query's complexity and select which subagent types it needs.
- Decompose it into subtasks, one distinct subtopic or source type each.
- Delegate each subtask with a Task tool call whose prompt is the full brief.
- Each subagent works in its own context window and returns its final message.
- Aggregate the results, invoke synthesis, and evaluate its output for gaps.
- Re-delegate targeted queries and re-invoke synthesis until coverage is sufficient.
More precise than the guide. The guide says a coordinator needs "Task" in allowedTools to invoke subagents. In the Agent SDK, allowedTools only pre-approves tools, and the delegation tool runs without approval whether listed or not. Claude Code 2.1.63 renamed the tool Agent, and Task still works as an alias (checked 2026-09-30). Exam answer: include "Task" in the coordinator's allowedTools.
Interactive · which subagents does this query need?
Choose a query to see which subagents the coordinator invokes.
Simple fact-finding: one web search subagent. Document analysis, synthesis and report generation are not invoked.
Direct comparison: one search subagent per chemistry. No long documents to read, so document analysis is not invoked.
Broad research: search split by subtopic, analysis by source type, and a gap check that can re-delegate before the report.
SkillSelect which subagents to invoke, not just how many
The coordinator analyzes each query and dynamically selects which subagents to invoke, rather than always routing through the full pipeline. For the year a standard was ratified, it needs one web search subagent making 3–10 tool calls, and it answers without document analysis, synthesis or a report. To compare two battery chemistries, it runs two search subagents, one per chemistry, and skips document analysis because no long documents need reading. Anthropic's figure for a direct comparison is 2–4 subagents making 10–15 tool calls each. Only a broad topic warrants more than ten subagents.
SkillPartition the scope so subagents cannot overlap
Subagents cannot see each other's assignments, so the coordinator prevents duplication by partitioning the scope into distinct subtopics or source types, one per agent. Anthropic's early runs gave several subagents the brief "research the semiconductor shortage", and two of them duplicated each other on 2025 supply chains. The fix was a four-part brief: an objective, an output format, guidance on tools and sources, and clear task boundaries.
SkillWorked example: too narrow a decomposition
Asked about "the impact of AI on creative industries", the system returns a cited report on digital art, graphic design and photography. Every subagent succeeded, and nothing says music, writing or film are missing. The coordinator's log shows three subtasks, all visual. That overly narrow decomposition left most of a broad research topic unassigned, so no subagent could notice the gap. The first fix is to list the sectors before assigning them.
Three subtasks, all visual
// coordinator log, pass 1 subtasks = [ "AI in digital art creation", "AI in graphic design", "AI in photography", ]
The topic listed, then split
// coordinator log, pass 1 sectors = ["visual art","music","writing", "film","games","design"] subtasks = one per sector, each with objective, output format, sources, boundaries
The second fix is the refinement loop. After the first synthesis pass, the coordinator checks the draft against its sector list. The film section cites one source, from 2019, so it re-delegates a targeted query to one search subagent instead of rerunning every search. It then re-invokes synthesis, and stops when a stated coverage bar is met, not after a fixed number of passes.
// coordinator, after synthesis pass 1 gap: "film" cites 1 source, dated 2019 re-delegate → web search subagent objective: "AI in film production 2023–2026: VFX, dubbing, script tools" output: "5–8 findings as {claim, url, date}" sources: "trade press, studio filings" boundaries: "film and TV only; other sectors are done" re-invoke synthesis with all findings stop when: every sector has 3+ sources from 2023 on
- The coordinator picks which subagent types run, and how many. A one-fact question needs one search subagent.
- Partition by subtopic or source type, because subagents cannot see each other's briefs.
- Refinement: check synthesis for gaps, re-delegate a targeted query, re-run synthesis until a stated coverage bar is met.