Understand your Chief of Staff
How do I direct twenty agents without talking to twenty agents?
So far, every job you've given your organization, you've handed over yourself, one at a time. That works for one job. It doesn't work for an organization.
Your organization has an agent whose whole job is to stand between you and everyone else: the Chief of Staff. You say what you want. It works out which agent should do it, writes that up as a clear job, and brings back only what needs your decision.
Today you do two things. First you learn what it's for, which is more than passing work along. Then you call it in and test it: pick one small request, predict where it will send it, watch it decide, and compare. If it surprises you, that's the useful part. You'll see exactly which rule or description made it choose.
Here's why it matters. For the rest of the course, when you want something handled, you call in your Chief of Staff and say it there. If you understand how it decides, you can direct your whole organization through one conversation. If you don't, you're back to twenty.
One thing to hold onto: it hands you decisions. It doesn't make them. In the next lesson you hire your own, and tell it what matters to you.
You can say what your Chief of Staff is for, and you have watched it route one request.
An assistant hands you tasks. A chief of staff hands you decisions, and takes the rest.
You predict where a request will go. You call in your Chief of Staff and ask for its plan. You compare.
You make the decisions. It brings them to you with the work behind them on record.
Hunter's opening
If every agent needed its own conversation with you, coordinating the organization could become another job. Chief of Staff keeps track of the work and brings you the decisions that need your attention.
Picture a small organization with a founder and twenty staff and no one in between. Every request lands on the founder. Every question comes back to the founder. Nobody knows who owns what, so work goes to whoever's nearest. The founder spends the day forwarding emails.
Now picture the same company with one person whose whole job is to sit between the founder and everyone else. Requests come in, they work out who should do it and what "done" means, they hand it on, they collect what comes back, and they tell the founder only what the founder needs to decide. The founder gets their day back.
That person is a chief of staff, and your organization has one.
Twenty windows, or one door
How to read the picture. Two halves. On the left, you with twenty agents and nobody in between: every line is a conversation you have to hold. On the right, the same agents behind one door. The big black box is your Chief of Staff, pulled forward. The small black square in the Executive Office is the same agent: that is where it sits. The dashed line is the exception: straight to one agent, when you want one thing from it.
Twenty windows, or one door.You and twenty agents with nobody in between, beside the same agents behind one Chief of Staff.
What it's for.
An assistant hands you tasks. A chief of staff hands you decisions, and takes the rest.
Not just routing. Its purpose is to hold the whole picture of what you're trying to do, and keep the organization's work pointed at it. That means four things a good human chief of staff does, and that yours is built to do.
It knows what matters to you.
Before every job it reads three files: the rules, your brief and your priorities. Every time, never from memory. When work comes in, it asks: does this matter, given what we're trying to do? Of everything pulling at you, which five things need you?
Everything flows through it. Not everything flows out to you.
A chief of staff that shows you everything it finds isn't filtering, it's forwarding: a very organized inbox with a job title. Yours comes back once, with the result and the one decision left. Not the traffic. The result.
It reads the work before you do.
It reads what each agent sent back, and the work record that agent saved, before anything comes to you. It doesn't judge the quality itself. When a job has a draft in it, a different agent checks it before it reaches you: the Quality Reviewer, never the agent that wrote it. If the review says fix it, the work goes back once. Then it comes to you.
It tracks what's open, so you don't have to.
Open requests, pending decisions, missing facts: it reads them from the work records every time and brings you the ones that need you. If there's no record, it treats the job as not done, and tells you so. It also keeps a log of every job: what it picked, what you corrected, and what it would do differently. It reads that log before routing anything, so a correction you make today shapes the next job.
It hands you decisions to make, with the work behind them on record. It does not make the decisions for you.
Judgment, when the answer isn't in any file, stays with you.
What it carries.
Its purpose needs three things. This is how "keep the work pointed at the objective" stops being a slogan and becomes a line in a file.
The charter
What your organization may and may not do. Until you adopt it, your Chief of Staff works from the draft and says "charter not adopted yet" in every brief. That line is correct. It goes away in Module 4.
Module 4Your brief
You wrote it in Lesson 4. Your Chief of Staff reads it before every job.
DoneYour priorities
Three lines. You add them when you hire your own, next lesson.
Next lessonBefore you start
Bring your corrected founder brief, approved sources, and one recurring case from the before photo. The Professor can help you find them. Your priorities, three lines on what matters this month, come next lesson, when you hire your own.
Start or resume this lesson
1. Open your workbench folder as the project in your app. Do this before you start the conversation. Your Chief of Staff checks where it is first, and stops if it isn't in your workbench.
2. Start a new conversation.
3. Claude Code: type @ and pick aibl-chief-of-staff from the list. Picking matters. If you type the name by hand, your app answers on its behalf and rewrites what it said. Codex: ask for your Chief of Staff by name.
aibl-chief-of-staff (renamed Sept 21); the box said chief-of-staff. Fixed here. Gigawatt confirmed (Sept 21, 7:03 PM): the name is final, students see one file, aibl-chief-of-staff.md; the -lead copy is a terminal render for the bridge and is not in the student package. The page was checked against that exact version (sha 5c31a09b), which is also what is on the live student shelf now.Paste this short request once, in your Chief of Staff conversation. Use a separate Professor conversation for step 1's file-reading help, then return here yourself for steps 2 to 4.
Use the native aibl-chief-of-staff agent to start or resume Lesson 6. Read course/workforce/prompts/anw-l06.txt and course/workforce/lessons/anw-l06.md completely. Wait for my routing prediction and request. This is plan-only: no go, no specialist dispatch, no sending. Report missing files or records; do not invent them.
Missing files, same as Module 2: it reads course/workforce/module3-plan.md and lessons/anw-l06.md. Neither is in the student repo. Who asks the Chief of Staff: the prompt has The Professor "ask the named Chief of Staff for a plan-only work order." Your ruling C171 (and Tyler's Decision 0029): the student calls the Chief of Staff in themselves. His own step 3 says "use the named-agent route," so the prompt and the step disagree. The prompts on this page follow your ruling: step 1 to The Professor, steps 2 to 4 to the Chief of Staff.
This lesson stops at the work order. You read Chief's instructions and inspect its decision. You don't change its profile or give the go to run the specialist work.
Try it: watch a request become a job
1. Read its file
In Lesson 2 you studied how the file is built. Now read what it asks Chief to do. Use the reading map below to find what it reads first, its four jobs, its routing checks, its stopping rules, and how it resumes saved work. Skim the details of how Chief calls other agents with The Professor if needed. Keep the file unchanged.
Say this to The Professor:
Open my Chief of Staff's file and take me through it one part at a time, top to bottom, using the reading map from this lesson. Show me each part, then stop and wait for me before the next one. Don't summarize it for me, and don't change anything.
2. Predict
Choose one small request from your recurring case or reuse the fictional invitation. Write down which agent you expect Chief to choose and one uncertainty it should bring back to you. This is your prediction, not The Professor's answer.
Return to the Chief of Staff conversation you opened yourself using the call-in box above, and say:
Here is a small request: [your request]. Don't plan or run anything yet. First save my prediction with this job's work records, exactly as I say it: I think this goes to [which agent], that [what] should come back, and that a missing fact should [what].
3. Watch it route
Use the named-agent route introduced in orientation. Make the no-execution boundary explicit. Read its proposed agents, reason, inputs, completion check, and decision for you. Compare these with your prediction. Clarify one vague part of the request if needed and inspect the revised work order. Do not give the go to call specialists.
Say this to your Chief of Staff:
Now plan that request. Write the work order, but don't send it to anyone and don't start any specialist work. Show me the work order beside my prediction. Tell me which of your five checks settled which agent gets it, and the file and line that support it.
4. What comes back to you
Ask Chief for the current brief. The open plan should be waiting for your decision, not reported as completed work. Find the saved work order and your prediction. Leave the job open for the next lesson. If the work order hasn't been saved, ask Chief to record it and verify the result rather than assuming the conversation is the record.
Say this to your Chief of Staff:
What's waiting on me? Show me the brief with its four headings. This plan should be under Needs you, not under Ran, because nothing has run. Show me where the work order and my prediction are saved, and leave the job open. I'm not saying go today.
If the installed route starts work despite the plan-only boundary, stop and report it. That is a mismatch to resolve, not evidence that the lesson is complete.
Read the picture. Your words go in at the top. The five checks run down the middle, following the workshop invitation. A work order comes out at the bottom, waiting for you.
Your words in. A work order out.Your request at the top, five checks down the middle, and a work order at the bottom, waiting for you.
What you just inspected
Four jobs that keep the work connected
| Job | What Chief does | What you should be able to inspect |
|---|---|---|
| Brief | Reports current work and decisions from saved records. | The source behind each status claim. |
| Route | Turns your request into a bounded job and chooses suitable agents. | The work order and its routing reason. |
| Queue | Keeps unresolved decisions visible. | What waits for your yes, rather than disappearing in conversation. |
| Escalate | Stops for uncertainty or a consequential decision. | A clear question about money, legal issues, safety, an external action, or an unresolved boundary. |
Chief coordinates the check; it doesn't become the reviewer. You've Got Mail, or YGM for short, your Communications Writer, produces a draft. Kansa, your Quality Reviewer, assesses it. Chief collects the work and returns the decision to you. A single-agent job may have no separate review; don't assume every returned result has been checked by Kansa.
The role also keeps work pointed at your priorities, follows up on unfinished work, and proposes a next step. A proposal is not permission. Your silence does not authorize it, and this lesson does not create a schedule or standing order.
Five checks for choosing an agent
Chief doesn't choose from memory or pick a familiar name first. It checks:
- The rules: the adopted charter, or the provisional template before adoption.
- The map: the agent roster's departments and their responsibilities.
- The door signs: the roster's descriptions of which agent owns which work.
- Its judgment within those limits: choose the agents the job actually needs, with a reason for each and a reviewer distinct from the producer.
- You: stop and ask when the job remains unclear, risky, or outside those decisions.
Both the department map and the door signs come from the current roster. A remembered chart isn't enough to establish what is available in yours.
Hunter's wording
A remembered chart or a role you saw in Tyler's personal workbench isn't enough to establish availability in yours.
Routing means making the request into a job and assigning it. Orchestration means keeping its steps and returns in order. Think of a restaurant host coordinating the tables, kitchen, and service: coordinating dinner doesn't mean cooking every dish. In the Week 1 package, specialists return to Chief; you don't manage their exchanges yourself.
The visual follows the same request through these checks. Read the example route, then compare it with the work order you received.
Chief inside the Executive Office, with the five routing checks and the human stop. Show a plan waiting for approval, not a draft or review that this lesson never ran.
Seven parts of the work order
The work order should identify the goal, a done check, the boundaries, the approved context, what must come back, your decision, and where the work is recorded.
For the fictional invitation, “done” might mean a draft and review that preserve the unresolved date and missing link. The boundary is no sending. The sources are the two approved notes. The decision is whether to keep the draft or request a correction. The work order names the job's record location. In this lesson these are proposed results; neither a named Writer nor a planned review proves those agents ran.
If an essential part is missing, Chief should ask for it before dispatch. Your clarification makes the job clearer. Chief still needs your go before starting it.
Bare "Chief" 34 times on this page; "You've Got Mail, or YGM for short" and "Kansa, your Quality Reviewer" in full. Same pass as Module 1.
Read the file with a purpose
| Section to find | Read for this question |
|---|---|
| What Chief reads before a job | Does it use the charter/template, founder brief, priorities, approved sources, roster, and saved work? |
| Four jobs | What does it own, and what remains yours? |
| Routing and the work order | Which check settled the choice of agent? |
| How a job runs | Where does it show the plan and wait for your go? |
| What it never does | Which specialist work must it hand to another agent? |
| Interruption and recovery | How does it find the last saved result and identify a missing step? |
The remaining sections explain communication style, tools, and technical dispatch. A written scope and a technical restriction remain different things, as you learned in Lesson 2. You don't need to attempt an outside action to understand that distinction.
Matches: the three files it reads before every job, in that order; "charter not adopted yet" in every brief until the root file exists; the four jobs and the four brief headings, word for word; the five checks in the file's order; the seven parts of the work order; the plan in three or four lines, then wait for "go"; the reviewer is never the producer, one revision then stop; it reads each agent's receipt file, not only its reply; no receipt means it did not run; "Next, if you say so"; silence is not approval; no standing orders in Week 1; never drafts, researches or scores; drafting and sending are locked by missing tools, staying inside its folders is its own discipline; owner, seat, receipt, registry; the brief as text or a page.
Three notes. (1) The file also calls the registry "the bench" and uses a shed command to read it; students will see both words. Your four-words box is capped at four (C176); "bench" may deserve the fifth slot. (2) The page never mentions the judgment log: after every job the Chief of Staff writes what it picked, what you corrected, and what it would do differently, and reads the last ten entries before routing anything. That is how your corrections in step 3 carry forward. One sentence in "What it's for" would cover it. (3) Visual 17 twice says the Chief of Staff "checks the work"; the file has it read the returns and receipts, never score. "Reads what comes back" is closer.
Owner means you. Seat means an agent. Receipt means a work record: your Chief of Staff calls them receipts. Registry means your agent roster. Bench is another word for the registry.
Hunter's wording
Four words in the file may differ from the lesson's language: owner means you; seat means an agent; receipt means a work record; registry means the agent roster.
The brief you'll keep using
The brief always has the same four headings, whatever voice your Chief of Staff uses:
Hunter's wording
Tyler's call showed the same four headings before and after changing Chief's voice:
| Heading | What belongs there |
|---|---|
| Needs you | Decisions and deadlines, with what a yes unlocks. Start here. |
| Ran | Work supported by saved results, including which agents returned what. |
| Outstanding | Open requests, missing facts, and unanswered questions. |
| Blocked or unclear | What cannot proceed and the question that would clear it. |
Your Chief of Staff may present the brief as text or, where supported, as a formatted page.
Hunter's wording
Chief may present the brief as text or, where supported, a formatted page like the one Tyler showed.
Choose the view that helps you read; both should preserve the same headings and links to the underlying work.
The brief reduces the amount you need to hold in your head. You still read a consequential decision and the work behind it. Asking for a brief is a deliberate action; it is not an automatic morning schedule.
four-heading brief with the current plan under Needs you, no specialist work claimed under Ran, and links to the actual saved work where available. Label any example fictional.
Your ruling (C101): Visual 16, the morning brief, goes in anw-l32, not here. His first placeholder (the Chief of Staff inside the Executive Office, five checks, a plan waiting) is your Visual 14; shown at it. For the brief placeholder there is nothing yet. His four-heading table carries it in words.
| What you notice | What to do |
|---|---|
| Chief chooses an unexpected agent | Ask for the roster description and routing reason. Compare them with the requested result. |
| It asks for information already recorded | Point to the approved record and check it was read. |
| It reports a planned job as run | Ask for the returned work. Correct the status if only a plan exists. |
| Your request is too vague to route | Specify the result, permitted inputs, and one boundary. |
| You cannot identify the selected Chief | Return to orientation's ordinary-chat versus named-agent explanation before continuing. |
A possible misunderstanding: A Chief of Staff title gives authority to decide everything.
First hint: Look at what should reach you after the specialists return, not only which specialist is named.
Another example: A restaurant host organizes a booking request but can't turn a proposed event into an owner-approved commitment.
A smaller step: Take one request through the charter and responsibility map first. Name the remaining decision, then try the other layers with less help.
If aibl-chief-of-staff isn't in the list when you type @: the step that puts your agents in the list hasn't run on this computer. Do step 6 of 0.3 Get your organization, then quit the app fully and open it again. Until then, paste the start request above as it is: it asks for your Chief of Staff by name.
aibl-chief-of-staff.Before you finish
You can explain Chief's four jobs, follow one routing choice through the five checks, and identify the seven work-order parts. Your prediction and the actual plan remain separate. You can find the open decision in the brief and explain why no specialist work has run yet.