When a sectioned single-agent prompt beats splitting into two agents

Flashcard·Easy·4.0 · 0·~30s·Asked atAnthropic OpenAI Cursor

Attempt it

Sections in a single prompt give you the conceptual separation (the model knows it is in the research phase, then in the summary phase) without paying for two LLM calls per task, two sets of context, two observability surfaces, and a handoff. The cost difference is roughly 2x on the simple case, and the operational complexity is much more than 2x because everything else (eval set, monitoring, dashboards, runbooks) doubles in pieces.

The rule is: reach for two agents only when the second agent needs something the first prompt section cannot give it: a different tool subset, a different model, a different context, or a structurally enforceable handoff for HIL. If 'two named sections in one prompt' would have worked, do that. Many production multi-agent systems started life this way and only legitimised the split after evals showed a specific win that sections could not reach.

Your answer

Quick reference

TL;DR

A sectioned single-agent prompt buys you the same conceptual phasing as a two-agent split without paying twice on cost, latency, and ops surface.

Memory aid

Easy to grasp

Think of writing a recipe and then cooking from it. You could hire two people, one to plan and one to cook, and have them hand notes back and forth. Or one person could read the recipe, decide what to do, and cook. As long as one person can do both, the second person is extra. They cost twice as much, they need to agree on what the notes look like, and if they miscommunicate the meal is wrong. In agent land, two named sections in one prompt is the one-cook version. The model knows it is in the planning step, then the cooking step. You only hire the second cook when the first one genuinely cannot reach the stove.

Key concepts

Multi-Agent Systems

Detailed answer & concept explanation

~6 min read

Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.

Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example.

Quick scan · 2–4 min

Everything important, quickly.

5 min: sectioned prompts vs multi-agent + what each gives you + cost and ops doubling + four legitimate split reasons + migration path.

Real-world examples

Real products, models, and research that use this idea.

Anthropic's published guidance on building agents recommends starting with a single well-prompted agent and reaching for multi-agent only when a specific need appears.
Claude Code's subagent feature spawns a separate agent only for well-scoped sub-tasks; the primary loop is one agent doing most of the work.
Cursor's agent mode runs as a single agent with a tool belt, not a crew, even for complex multi-file edits.
Many CrewAI tutorial workflows (research and write, scrape and summarise) collapse to a sectioned single-agent prompt with no measurable quality loss.
Devin and Replit Agent use planner plus executor splits because the planner genuinely needs a different model and tool surface than the executor, not because two agents felt cleaner.

Interviewer follow-ups

What an interviewer would ask next. Try answering before peeking at the approach.

QWalk through a workflow where sections looked sufficient but failed in production. What broke?

QIf you do split, what does the handoff payload look like, and why does that shape matter?

QHow do you measure whether a split actually improved quality?

Don't say this

Red flags and common mistakes that signal junior thinking. Click to expand.

Most common mistake

Splitting into two agents because separation of concerns feels right. The split has to earn its keep with a named single-agent failure, not aesthetics.

60-second cheat sheet

The night-before-the-interview bullets. Scan these on the way to the call.

References

Primary sources. Skim if you want the original framing.