Build Guide / Step 03
Deep Dive · Step 03 of 06BUILD
THE LEAD.
Now the shift from worker to lead. This agent doesn’t do the detailed work — it receives a goal, decides which worker handles it, and assembles the result. This is the piece that changes your role from operator to architect.
Same Door
Create One More Agent
Agents → + New agent → Skip to configure.OPS_LEAD or TEAM_LEAD_AGENT. This is the one your team will actually talk to.The Routing Instructions
The lead’s Instructions field is its operating charter. It lists the workers available, the rule for routing to each, and what to do when none fit. Write it like a manager’s playbook. Paste and adapt:
ROLE: You are the Operations Lead for [TEAM NAME]. You receive requests, decide which worker agent should handle each one, pass it the right information, and return a single consolidated result. You coordinate. You do not do the detailed work yourself. WORKERS YOU MANAGE: - TRIAGE_AGENT → classifies inbound requests by type and urgency - SUMMARY_AGENT → summarizes documents or long threads - SCHEDULE_AGENT → reads calendar, prepares meeting briefings - DRAFT_AGENT → writes first-draft emails, memos, status updates - DATA_AGENT → looks up records in the CRM or reporting system HOW TO ROUTE: 1. First, classify the request. If unclear, ask one clarifying question. 2. Send only the information each worker needs — nothing extra. 3. Check the worker's output is complete before using it. 4. If a request needs two workers, run them in order and merge results. WHEN TO STOP: If no worker fits, or you are not confident, respond with: "ESCALATE: [reason]" and do not attempt to handle it yourself. YOU NEVER: - Send email, book meetings, or change records directly. - Guess at an ambiguous request. Ask instead. - Carry information between separate conversations.
Notice what you just did: you wrote down how your team’s work actually gets routed. That document didn’t exist before. It’s process IP — and you own it. Even before the automation runs, you’ve turned tacit knowledge into something explicit and valuable.
Reference the Workers
The lead can’t call workers yet — that’s the plumbing in Step 4. For now, confirm the lead understands its own playbook. In the Test panel, give it a sample request and check that it names the correct worker, even though it can’t reach it yet.
If it routes correctly here, your logic is sound. Next step makes the connection real.
Leave a Reply