Free to read · no account needed

16 min · agents

Subagents and clean handoffs

Goal: split big work into small agent roles without losing the plot.

Best for: when one mega-prompt fails and you want “researcher then writer” without chaos.

A subagent is just another focused pass: one role, one Done checklist, one output. A handoff is how you pass that output to the next role without re-explaining everything.

Beginners: you can fake subagents in one chat—label sections Research Agent and Writer Agent—or use product features that spawn helpers. The idea matters more than the brand name.

Why beginners skip this

One mega-agent for everything feels efficient until handoffs lose the goal and open questions. Split roles only when each has a written Done and a human checkpoint between them.

Habit this week (Asia/Shanghai): draw two named roles with input / Done / forbid lines; run role 1 only today and date the handoff note.

Step 1 — Split into 2–3 roles max

Each role needs: name, Done output, and what it must NOT do. Example: Researcher finds sources; Writer never invents links; Checker only attacks claims.

Goal: Split this job into ≤3 subagent roles.
Job: [job]
For each role: name · Done output · must-not · handoff format
Keep it beginner-simple.
Example

Filled prompt

Project: Q4 launch FAQ (EN).
Split into 3 roles: gather product facts → draft FAQ → critique for invented SLAs.
Write handoff baton template (inputs, Done, unknowns).
Today run only role 1; leave written baton for role 2.

What good output looks like

  • ≤3 roles
  • Researcher output is a source list, not the full article
  • Writer must-not includes inventing URLs
  • Pass/fail dated (Asia/Shanghai) sits next to the artifact

Step 2 — Define the handoff package

A handoff is a short package: goal reminder, Done so far, artifacts, open questions. The next role should not need the whole chat history.

Write a handoff template from Researcher → Writer.
Include: goal · sources table · quotes allowed · tone · open questions · forbidden actions.
Example

Filled prompt

Project: internal RFC on rate limits.
Roles: gather current limits from repo docs → draft RFC outline → critique for invented numbers.
Handoff baton must list Unknowns.
Today: role 1 only.

What good output looks like

  • Done boxes for “split big work into small agent roles without losi” are explicit and checkable
  • Allow-list tools only; never-do lines honored
  • Stops before send/delete without human gate
  • Pass/fail: Plan→Act one→Check visible for agents-subagents-and-handoffs

Step 3 — Run roles in order; do not parallelize yet

Beginners: run Researcher to Done, you check, then Writer, you check. Parallel subagents come later.

You are the [Role] only.
Handoff package:
[paste]
Done checklist: [paste]
When finished, output the handoff package for the next role—not a chatty essay.
Example

Filled prompt

Scene: real work this week (live artifact open).
You are the Researcher only. Done: 3 sources with title+url+date+why-trusted. Next role=Writer.
Constraints: no invented facts; stop before send/delete; label Unknowns.

What good output looks like

  • Three roles max with one-line Done each
  • Handoff baton includes unknowns
  • Only role 1 runs today
  • Human gate before publish remains

Save this card

Card: two named roles · handoff = input / Done / open / forbid · human gate between roles.

1. What I shipped: ___ 2. What I refused: ___ 3. What I will never-do again: ___ (date: Asia/Shanghai)

  • [ ] Tools/writes paused
  • [ ] Refuse-line dated
  • [ ] Artifact path saved
  • [ ] Next link chosen (or stop)

Before you start

Write Done (checkboxes) and the human gate on paper before any run for “split big work into small agent roles.” Allow-list tools; leave send/delete off. Guide: agents-subagents-and-handoffs. If you only have a blank practice box, stop and fetch the real job first.

  • Goal in one line: ___
  • Allowed tools: ___
  • Forbidden: ___
  • Human approve needed for: ___

How to use this week

This week: split one multi-step job into two named roles with a written handoff (inputs, Done, red lines). Run it once with a human checkpoint between roles on a live artifact—not a blank demo. Write one refuse-line and date the note (Asia/Shanghai). If you only skimmed agents-subagents-and-handoffs, put 25 minutes on the calendar and redo once.

Pass Done explicitly

Handoffs that drop Done create zombie agents. Permissions travel with the job.

Ship the practice

Close the tab only after Practice now is done on a real artifact.

Do not bookmark-only

Finish Practice now, then tick this guide on your path. Titles unread are not skills.

Close the loop

After Practice now, write one line: what you will refuse next time. That line is the habit.

Check the unknown path

What should the model do when a field is missing—null, TBD, or ask you? Write it once in Boundaries.

Red flag

Handoff that only says “continue”; red lines disappearing in the child; child widening write scope—reject the handoff.

Pitfalls

PitfallFix
10 micro-agents on day oneStart with 2 roles
Handoff = entire chat logPass a short package
Writer inventing sources Researcher never foundChecker role or you verify links
Example

Filled prompt

Temptation: skip the habit for agents-subagents-and-handoffs to “save five minutes.”
Job still: split big work into small agent roles
Do the smallest correct pass: Done visible · one checkable artifact · Unknowns labeled [?].
Boundaries: draft only; no silent send; no invented metrics.
Return: the artifact + the refuse-line you said aloud.

What good output looks like

  • Names the shortcut you refused (specific to agents-subagents-and-handoffs)
  • Still delivers a checkable artifact for “split big work into small agent roles”
  • Unknowns labeled; draft-only respected
  • Pass/fail: refuse-line written and dated (agents-subagents-and-handoffs #4)

Practice now

Live card: run one agent checklist item on a real job for “Subagents and clean handoffs”—artifact path on Save (Asia/Shanghai).

Draw three boxes for one real project. Name each role Done in one line. Run only role 1 today; hand a written baton to yourself for role 2 tomorrow.

Today card (copy) — agents-subagents-and-handoffs: 1. Artifact I will produce: ___ 2. Pass/fail check: ___ 3. Refuse-line if tempted to skip verify/send: ___ (date: Asia/Shanghai) 4. One never-do from this guide: ___

  • [ ] Artifact path written
  • [ ] Refuse example would say "yes"
  • [ ] Dated Asia/Shanghai

One sentence takeaway

Split work into named roles with written handoffs and a human gate between them. This week: run one two-role handoff and date it (Asia/Shanghai).

Next

Human-in-the-loop · Research agent pattern · Plan → act → check · Team playbook · Logging what matters

Pair with today: open the first Next link (agents-human-in-the-loop-checkpoints) only after you dated a refuse-line for this guide (Asia/Shanghai).

← Back to home · Learn · Tools · Compare · Start