A coordinator has found a failing test's file path and its stack trace, and now spawns a non-fork subagent to fix it. How should it give the subagent this information?
id q05193e2f9c
Home / Claude Certified Architect – Foundations / Objective 1.3
Domain 1: Agentic Architecture & Orchestration · 27% of the exam · Full exam outline
The Task tool as the mechanism for spawning subagents, and the requirement that allowedTools must include "Task" for a coordinator to invoke subagents. That subagent context must be explicitly provided in the prompt—subagents do not automatically inherit parent context or share memory between invocations. The AgentDefinition configuration including descriptions, system prompts, and tool restrictions for each subagent type. Fork-based session management for exploring divergent approaches from a shared analysis baseline. Including complete findings from prior agents directly in the subagent's prompt (e.g., passing web search results and document analysis outputs to the synthesis subagent). Using structured data formats to separate content from metadata (source URLs, document names, page numbers) when passing context between agents to preserve attribution. Spawning parallel subagents by emitting multiple Task tool calls in a single coordinator response rather than across separate turns. Designing coordinator prompts that specify research goals and quality criteria rather than step-by-step procedural instructions, to enable subagent adaptability.
A coordinator has found a failing test's file path and its stack trace, and now spawns a non-fork subagent to fix it. How should it give the subagent this information?
id q05193e2f9c
Your telemetry counts subagent launches by inspecting tool_use blocks in the Agent SDK message stream. To stay correct across older and current SDK versions, which tool names should it match?
id q7bf38f7495