This lesson is being recorded

Every video of this course is being uploaded to my YouTube channel. Subscribe so you do not miss it.

Bruno AshfordBruno Ashford @brunoashfordSubscribe

Module 7 · Lesson 7.4 · 11 min

Parallel Work

Run several specialists on the same problem at the same time to get multiple perspectives quickly.

Module 7
Your AI Department

Subagents and teams that check each other's work

Bruno Ashford
Bruno Ashford · Module 701 / 13
The problem
You would never ask one employee to prospect, write, do the books and proofread in the same meeting. Stop asking your AI to.
Bruno Ashford
Bruno Ashford · Module 702 / 13
7.1 One agent per role

What a subagent is

A specialist with its own instructions, context and tools.

  • Starts with a clean context
  • Reads its own job description
  • Uses only the tools you allow
  • Returns a summary, keeps the noise
Bruno Ashford · Module 703 / 13
The three-question test

Does this task deserve a specialist?

  1. 1Repeats weekly?Recurring work earns a role
  2. 2Different mindset?Writing versus checking
  3. 3Lots of noise?Research and data crunching
Bruno Ashford · Module 704 / 13
7.2 The file

Anatomy of a subagent

FieldWhat it does
nameUnique id, lowercase with hyphens
descriptionWhen Claude should hand work to it
toolsAllowed tools, comma separated
modelsonnet, opus, haiku or inherit
bodyThe job description in plain English

Project agents: .claude/agents/. Personal agents: ~/.claude/agents/.

Bruno Ashford · Module 705 / 13
7.2 Least privilege

Only the tools the role needs

Leave tools out and the agent inherits everything.

  • Analyst: read, search, write reports
  • Researcher: read, web search, web fetch
  • Reviewer: read and search only
  • Nobody gets send by default
Bruno Ashford · Module 706 / 13
7.3 The reviewer
Writing and checking are different jobs. Give them to different agents.
Bruno Ashford
Bruno Ashford · Module 707 / 13
The loop

Write, review, fix, review

  1. 1WriteSpecialist drafts
  2. 2ReviewRead-only checklist
  3. 3FixEvery issue addressed
  4. 4Review againFixes create new mistakes
Bruno Ashford · Module 708 / 13
7.4 Parallel work

Independent views in minutes

Same question, several specialists, no groupthink.

  • Same inputs for every agent
  • Same output format
  • Read the disagreements first
  • Save it for decisions that matter
Bruno Ashford · Module 709 / 13
Accounting practice task map (illustrative case)

23 recurring tasks, sorted

6human only
14agent drafts, human approves
3agent alone
Bruno Ashford · Module 710 / 13
7.5 Org chart

Every agent has a human owner

AgentJobOwnerApproval
sdr-researcherLead researchSales leadNone, internal
copywriterOutreach draftsMarketingHuman sends
data-analystWeekly numbersOwnerNone, internal
reviewerChecks client workOperationsBlockers stop it
Bruno Ashford · Module 711 / 13
Project

Your first AI team

Three to five specialists, one real workflow.

  • Fill the org chart worksheet
  • Create agents with /agents
  • Restrict every tools line
  • Reviewer is always the last step
Bruno Ashford · Module 712 / 13
Recap
A department is not more AI. It is clear roles, clean context, limited tools and a human who owns every result.
Bruno Ashford
Bruno Ashford · Module 713 / 13
01 / 13

Use ← → to move. The marker highlights text and the pencil draws on the slide; navigation locks while you annotate. Undo removes the last mark, Esc exits.

1Ask for parallel work explicitly

Tell Claude which specialists to use and that they should work in parallel and independently. Specify the same inputs for all of them so the comparison is fair.

Prompt for Claude
I am considering raising our prices by 12 percent. In parallel and independently, ask three subagents to analyse this: the data-analyst (using data/ for the last 12 months of sales), the sdr-researcher (competitor prices in our market, with links), and the reviewer (risks and customer reactions to watch). Then combine their findings into one page: where they agree, where they disagree, and your recommendation.
2Split big research into slices

Parallel work is also great for volume. Twenty leads to research? Ask for five researcher runs with four leads each. Each run stays small and focused, and the whole batch finishes much faster than one long sequence.

3Force a structured return

Ask every specialist to return the same format (for example: finding, evidence, confidence high/medium/low). Structured answers are easy to merge. Free-form essays are not.

4Look for disagreement, not just consensus

The value is in the tension. If the analyst says prices can rise and the reviewer warns about churn in one segment, that is the real conversation to have with your team. Ask Claude to highlight disagreements first.

5Watch cost and limits

Each subagent uses its own context, so parallel work uses more of your plan's usage than one prompt. Save it for decisions and batches that matter, not for everyday questions.

When you face a big decision, like raising prices or opening a second location, you would ideally ask your finance person, your sales lead and your most sceptical advisor, all independently, before they influence each other. In real life that takes a week of meetings.

With subagents, Claude Code can send the same question to several specialists at once. Each works in its own clean context, and the main session brings the answers together. You get independent perspectives in minutes, and you can see where they agree and where they fight.

Key points

  • Parallel subagents give independent views before they influence each other.
  • Use it for big decisions and high-volume batches.
  • Same inputs and the same output format for every specialist.
  • Disagreements are the most valuable part of the output.

Avoid

  • Running parallel agents for simple questions and burning usage.
  • Giving each specialist different inputs, then comparing apples with oranges.
  • Reading only the combined summary and never the individual reports.
Real-world example: a roofing contractor

A roofing contractor debating whether to add gutter installation as a service asked for three parallel views: the analyst on his job history and margins, the researcher on local competitors and pricing, and the reviewer on operational risks. The analyst found gutters were already requested in 18 percent of quotes. The researcher found two competitors bundling them. The reviewer flagged that his crew had no certified installer. The decision became obvious: partner first, hire later.

Bruno Ashford Subscribe