PTENES
Skip to content
MODULE 2.4

🤖 Agents that do the work

Up to this point, you’ve directed one helper at a time. Now you become the boss of a team: handles entire tasks, puts several agents to work at the same time, and brings everything together at the end—like a conductor conducting the orchestra.

6
Topics
~55
Minutes
Practical
Level
Practice
Type
Progress in this module0%

0 of 6 sections read

💡 New here? Three words before you start

  • Agent — an AI that, instead of just answering, goes and does it the task from start to finish, on its own.
  • Delegate — handing an entire objective to someone (or an agent) to take care of, instead of doing it by hand.
  • In parallel — several tasks happening at the same time, side by side, without waiting for one to finish before starting another.
1

📨 Delegate an Entire Task to an Agent

Until now, you’ve talked with AI step by step: you ask for something, it responds, then you ask for the next thing. Delegate it’s different — you give it the goal whole at once and let the agent handle everything on its own: it reads, decides, does the work, checks it, and comes back with the finished work.

It’s like asking a human assistant: you don’t dictate every click. You say "organize the invoices folder by month and let me know if anything is missing" and trust that it’ll handle it. Your job becomes describe the goal well e check the result — not monitoring every move.

🔑 The central idea

Think about the difference between give instructions every minute e hand off the mission:

  • •Micromanage: "open the file... now copy line 3... now paste it here..." — you do almost everything.
  • •Delegate: "combine these 5 spreadsheets into one, removing duplicates" — the agent handles the steps in between.
MICROMANAGE 🙂 step keeps going back and forth 🔁 DELEGATE 🧑‍🎤 ✅ ready the agent handles the middle 🤖
On the left, you're stuck going back and forth; on the right, you hand off the mission and get the result. Delegating gives you back time.

🧪 Copy and run: delegate an entire task

Goal: feel what it’s like to hand over the whole mission instead of asking for step-by-step instructions. Paste it into Claude or ChatGPT, replacing what’s between < >.

Aja como um agente que executa a tarefa DO COMEÇO AO FIM.

TAREFA: <ex: organizar estas anotações soltas num resumo
de reunião com decisões e próximos passos>.

MATERIAL: <cole aqui suas anotações / dados>

Como quero o resultado: <ex: um resumo em tópicos, com uma
lista de tarefas no final, cada uma com responsável>.

Trabalhe sozinho até terminar. No fim, me entregue:
1) o resultado pronto,
2) uma linha dizendo como EU posso conferir se ficou certo.

How to know it worked: AI should come back with the work ready-made (not just a plan) and finish by telling you how to check it. That's delegation — you only review it at the end.

Key concepts

📌 Deliver the goal, not the steps
📌 Let the agent autonomy
📌 Your role: describe + check
📌 Stop micromanaging
2

👥 Several at once (fan-out)

If an agent can already do the whole task on its own, why not have several working at the same time? That’s the fan-out — a fancy word for “spreading out the work.” You split the mission into parts and send one agent to each part, all working in parallel.

Imagine you need to research 5 competitors. Instead of having one agent analyze them one by one (slowly), you send 5 agents, each handling a competitor. They work together, and you get all 5 reports in almost the same time it would take to get one. That's where the speed takes off.

FAN-OUT · 1 orchestrator → multiple agents 🎼 you (the conductor) 🤖 🤖 🤖 🤖 part A part B part C part D all at the same time ⚡
The conductor launches one agent per part and all run together. Four tasks in the time of one—that’s fan-out.

💡 Practical tip

Fan-out is only worthwhile when the parts are independent — one doesn’t need to wait for the other. Researching 5 competitors is perfect. But “write chapter 2, which depends on chapter 1” won’t work: that’s better handled by a single agent, step by step.

Key concepts

📌 Fan-out = spread the work
📌 Multiple agents in parallel
📌 Works in parts independent
📌 Multiplies the speed
3

🪓 Break a large task into pieces

To distribute work among several agents (or just get more out of one agent), first you need to break the task into pieces. A task that’s too big confuses even AI: focus gets lost, details slip through. Smaller pieces are easier to do well—and easier to check.

The image below summarizes the module: you're the conductor coordinating agents that do the heavy lifting, each in their own area.

A conductor in the center, surrounded by several glowing AI agents carrying out tasks in parallel, connected by blue threads of light — an image of delegating and orchestrating work.
The heart of module 2.4: you conduct; the agents execute, each handling its own part.
1

🎯 Look at the end goal

Before cutting, make it clear what “done” means. Example: “a report on 5 competitors.”

2

✂️ Split into natural sections

Look for the obvious “seams”: one competitor per section, one chapter per section, one month per section.

3

📋 Give each piece the same template

Each agent gets the same response format. That makes it easy to put everything together at the end.

4

🧩 Put the pieces together

When the parts follow the same pattern, putting together the final result is like fitting pieces together.

💡 Practical tip

Rule of thumb: if you can’t describe a part in one clear sentence, it's still too big. Cut it down again until each part fits in one sentence.

Key concepts

📌 Smaller piece = better result
📌 Cut by natural connections
📌 Same template in each part
📌 One sentence per piece
4

🔍 Review What the Agent Delivered

Delegate no it’s giving up control. The agent does the heavy lifting, but the result has your name on it — so the review is still yours. The good news: reviewing is much faster than doing the work, and with practice you develop an eye for where mistakes tend to show up.

The right review isn’t rereading everything line by line. It’s check the points that matter: was the goal met? Do the numbers add up? Is anything made up? Is anything missing? When you clearly defined “what good looks like” at the top, review is easy—you just compare.

✓ Conductor’s review

  • ✓Check whether the goal was achieved
  • ✓Confirm important facts and numbers
  • ✓Look for missing or made-up parts
  • ✓Asks for adjustments and runs it again if needed

✗ Blind trust

  • ✗Accepts everything without reading
  • ✗Assumes that “looks right” = is right
  • ✗Doesn't check any numbers
  • ✗Uses the result and discovers the error afterward

💡 Practical tip

Ask the agent itself for a "checklist" along with the result: "tell me 3 things I should check before trusting this". It points out the weak spots—and focuses your review.

Key concepts

📌 Delegate ≠ abdicate
📌 Reviewing is faster than doing
📌 Check what matters
📌 The result is yours
5

⚖️ When to use one agent or several

More agents aren’t always better. Launching five when one would do only creates confusion and unnecessary expense. The choice is simple when you look at the task: does it breaks it into independent parts or is one thing, in sequence?

Use the two charts below as your compass. When in doubt, start with one agent—it's easier to keep track of—and only move on to several when you feel you can split them up without the parts depending on one another.

✓ One agent is enough when…

  • ✓The task is small or quick
  • ✓One step depends on the previous one (sequence)
  • ✓You want to keep a close eye on it
  • ✓Everything is about the same topic

✓ Multiple agents are worth it when…

  • ✓The work is large and separable
  • ✓The parts don’t depend on one another
  • ✓Speed matters a lot
  • ✓Every part is similar (same template)

💡 Practical tip

Do the the stitching test: try describing the task as “do X for each ___.” If the phrase sounds natural (“for each competitor,” “for each month”), it’s fan-out. If you need “first... then... after that...,” it’s an agent working in sequence.

Key concepts

📌 More agents ≠ always better
📌 Sequence → one agent
📌 Separable → several
📌 When in doubt, start with one
6

🎼 Orchestrate like a conductor (put it all together)

Here, the module’s five ideas become one dance. Orchestrate it’s your job as the conductor: you define the goal, break it into pieces, launch the agents (one or several), review what each one brings back, and combines everything into one result that feels like you.

Notice: you didn’t touch an instrument. You didn’t program or do the heavy lifting. But you conducted it—and the result bears your name. That’s the heart of this entire course, now put into practice with a team of agents.

🎯 The maestro’s cycle

  • 1.Define the goal and “what good looks like.”
  • 2.Cut in pieces that fit an agent.
  • 3.Launch — one agent, or several in parallel.
  • 4.Review what each one delivered.
  • 5.Gather all in one result.
📨
Delegate: deliver the entire mission, not the steps.
👥
Fan-out: several agents at the same time, on independent parts.
🔍
Review and combine: you review and assemble the final result.

✋ Before you continue — you need to research 5 competitors, and each search is independent of the others. What's the best move?

🎓 Module summary

✓
Delegate the entire task — give it the objective, not the steps.
✓
Fan-out — several agents working in parallel on independent parts.
✓
Cut and review — small pieces, with you still doing the review.
✓
Orchestrate — you lead the team and bring everything together into one result.

Next module:

2.5 — ✅ Verify and prove: how to measure, test for real, and turn what you did into proof.