Module 7 · 5 lessons · 56 min

Your AI Department: Subagents and Teams

7Your AI Department: Subagents and TeamsModule 7 · OverviewYour AI Department: Subagents and Teams
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.

Stop asking one assistant to do everything and build a small team of specialists that check each other's work.

Start lesson 7.1
Bruno Ashford Subscribe