Skip to content

// Orchestration · ~2 min read

Orchestrator-Subagent

Reach for it when: one agent can’t hold all the skills or background information it needs without getting muddled.

After this lesson you can: Split a goal across specialist subagents while the orchestrator only delegates and merges.

// 60-second mental model

How to hold it in your head

A planner owns the goal and never does the specialist work. It dispatches specialists, then merges their results.

An orchestrator agent breaks the goal into parts, hands each part to a subagent through a tool call with fixed inputs and outputs, and merges the results into one answer.

How this differs

Both an orchestrator and a supervisor coordinate workers. In this course neither drafts the content itself (in many frameworks they also write the final reply). An orchestrator breaks the goal into parts and merges the results. A supervisor (next lesson) picks the next worker and can reject what comes back.

// Mini architecture

Orchestrator dispatches; specialists work; results fan in

An Orchestrator holding the goal and plan sends work to three subagents: Research, Draft and Critique. Their results all flow back into one merged output.

The orchestrator may only call delegate_* tools — it is not allowed to write the post itself.

// Mini-project

Research → draft → critique brief

Orchestrator + three stub subagents

Goal: Produce a short brief by dispatching research, draft and critique stubs — orchestrator only merges.

  1. Orchestrator receives: “Brief me on X for a LinkedIn post.”
  2. It must call `delegate_research`, then `delegate_draft`, then `delegate_critique` (stubs return fixed strings).
  3. Refuse any path where the orchestrator writes the draft in its own voice.
  4. Merge critique notes into a final brief.
  5. Log which specialist ran at each step (for the lesson demo).

Stubs are fine. The contract is the lesson: tool-only delegation, no “I’ll just do it myself”.

// Common failure

What goes wrong

Symptom

Orchestrator does the work itself — specialists become decorative.

Fix

Force tool-only delegation contracts: the orchestrator’s only actions are delegate_* and finalize.

// Self-reflection

Sit with this

Would your current multi-step agent be clearer as orchestrator + specialists?

Sources

Session only. Nothing is saved.