If you have ever started a Monday wondering what is on your plate, where the week stands, and what is going to bite you by Thursday, you know the cost of a missing chief of staff. The role has a quiet job. It is the person who walks into your office at 7 AM with one doc that has everything you need to start the day. Industry headlines that matter. Today's calendar. Open commitments. Things slipping. What you said yesterday that you forgot you said.
Most CEOs at small and mid-sized businesses never had this role on the team. A real chief of staff seat costs around $180,000 a year and shows up at companies with at least 50 employees. The Chief of Staff agent in the Agent OS series does the part of that role that is mostly mechanical: the morning briefing assembly. The senior judgment work a human chief of staff brings stays human.
This is the per-agent breakdown for the Chief of Staff in the Agent OS Webinar series. Week five of the 90-day install order. It comes after the Researcher, Speechwriter, Personal CFO, and Executive Assistant because the briefing only works once those upstream agents are producing the outputs the Chief of Staff assembles.
What the Chief of Staff reads (Inputs)
Six inputs feed the morning briefing. Most of them are the outputs of other agents already in your stack.
- The Researcher's morning digest. Today's three industry stories that matter for your operation. Five lines, already filtered.
- The Speechwriter's daily draft. Today's content piece, sitting in the review folder, waiting for your edits.
- Your active project list. The 8 to 15 projects you are running this quarter, with their current state. Open, on-track, slipping, blocked.
- Your open commitments. What you said you would do, by when, for whom. Pulled from prior daily notes, meeting transcripts, and email threads.
- Today's calendar. With pre-meeting briefs already pulled in by the Executive Assistant.
- Your time tracking. If you keep any. Where the last week of hours went, against where the priorities said they should go.
The Chief of Staff is the most chain-dependent agent in the shadow team. Install it first and the briefing is empty — there is nothing for the agent to assemble. Install it after the upstream agents and the briefing writes itself.
What it does with that material (Skills)
Three skills, all in service of the morning doc.
- Briefing assembly. Pull the upstream agent outputs into a single structured document with consistent sections. News at the top. Content draft below. Commitments and project flags after that. Calendar at the bottom. Same shape every day so you scan it in under two minutes.
- Commitment tracking. Watch the daily notes for things you said you would do. Surface them in the morning briefing on the day they come due. Surface them again on the Monday after the due date if they slipped. This is the part the agent does that you cannot reliably do for yourself, because the commitments are scattered across email threads and meeting notes you stopped re-reading two weeks after they happened.
- Friday weekly review. A weekly draft, written on Friday afternoon, covering what shipped, what slipped, and the one or two things to think about over the weekend. The draft sits in your weekly review folder. You take 15 minutes on Friday afternoon to confirm or revise.
The Chief of Staff does not decide. It assembles. The synthesis is yours.
The schedule (Scheduled Tasks)
Two daily runs, two weekly runs.
- 7:00 AM weekdays. The morning briefing assembles. By the time you sit down with coffee at 7:30, the doc exists in your daily-note folder, with everything threaded in.
- 5:30 PM weekdays. End-of-day commitment sweep. The agent reads the day's notes and adds new commitments to the tracker. Anything that slipped today gets noted.
- Monday 8 AM. Commitment scan for the week ahead. What is coming due, what is at risk of slipping based on the project state, what needs your attention before Thursday.
- Friday afternoon. Weekly review draft, ready for your 15-minute pass.
The 7 AM time is non-negotiable. The whole reason this agent works is that the briefing is sitting in your folder before you start the day, not after. The Chief of Staff has to run after the Researcher (6:00 AM) and the Speechwriter (6:30 AM) but before your coffee. One hour is the window.
What lands on your desk (Outputs)
Two outputs, one structure.
- The morning briefing. One markdown file per day in your daily-note folder. Same shape every day: news, content draft, commitments coming due, today's calendar with pre-meeting briefs, anything slipping, anything new that needs you. Two to three pages, mostly skimmable, with the action items called out at the top.
- The Friday review draft. A one-page summary of the week with the shipped-and-slipped structure. Pre-populated from the daily notes. Ready for your 15-minute pass.
Both outputs live in your vault. The agent does not send them anywhere. The morning briefing is your daily artifact. The weekly review goes wherever your weekly reviews go after you finish editing.
The goal: one doc with everything
The Chief of Staff exists for one outcome. Every morning, the day's reading and decisions are in one doc. The doc is in the same place every day. The doc has the same shape every day. The friction of starting the day shrinks from 25 minutes of opening tabs and reconstructing context to 2 minutes of reading a single page.
The second-order effect is that the rest of the agents finally feel like a team. Before the Chief of Staff is installed, the Researcher's digest, the Speechwriter's draft, the Executive Assistant's flags, and the Personal CFO's pending receipts all sit in their own folders. You have to walk a path through each one. After the Chief of Staff is installed, they all show up in the same place, in the same order, and you read them as one document. The agents stop feeling like four separate tools and start feeling like a single operation.
This is the strongest example in the shadow team of why the chain matters. None of the agents is doing more work than before — the Chief of Staff is purely synthetic. The change is that the outputs are now consolidated. Synthesis at the surface is what makes the system feel like a team instead of a stack.
A worked example at Not Really Wines
At Not Really Wines, our fictional demo winery at NunnCurtis Labs, Maren Holloway opens her laptop at 7:35 AM on a Tuesday in March. NRW is approaching its Series A timeline and the team is running long days. The briefing is sitting in her daily-note folder when she logs in:
Tuesday, March 17. Good morning.
News (Researcher). Two industry stories worth your attention. The first one — sell-through trends in the non-alcoholic category at a major mass retailer — supports the wholesale narrative Jordan is building for next month's distributor pitches. The second is a piece on adult non-drinkers that would be a useful share to The Society subscribers on Friday.
Today's draft (Speechwriter). A 220-word note for The Society about the segment narrative shifting from niche to mainstream. Ready in your review folder; queued for the 11 AM newsletter send.
Commitments coming due. (1) You promised Marcus a Series A timeline doc by Friday — currently in draft, 60% complete. (2) You committed to Jordan to review the East Bay wholesale pitch deck before his Thursday calls. The deck is in your review folder.
Today's calendar. 9:00 production cellar walkthrough with Diego. 10:30 Tasting Bar walkthrough with Tessa (pre-meeting brief from the EA — see below). 1:00 Investor call with [Series A lead]. 3:00 wholesale-strategy session with Jordan and Marcus.
Slipping. The harvest-season operations plan you said you would draft by Monday is still sitting in your projects folder. The first draft was due ten days ago.
For your attention. Tessa flagged a staffing question for the May holiday weekend that needs a decision before Thursday. Priya is asking whether The Society members get early access to the Rosé reorder before public DTC release.
Maren reads the briefing in two minutes. She approves the Speechwriter's draft. She moves the harvest plan to the top of today's writing block. She makes a 10-second note to call Diego about the harvest plan timing during the 9 AM walkthrough. By 7:45 AM she has the day mapped, the urgent decisions queued, and the content piece approved. She walks down to the production cellar at 8:50 with coffee and a clear head.
The briefing did not decide anything for her. It put everything in one place so the decisions could happen in two minutes instead of thirty.
Why this is week five of the install order
The Chief of Staff comes fifth because the briefing only works once there are upstream agent outputs to assemble. Without the Researcher, the news section is empty. Without the Speechwriter, the content section is empty. Without the Executive Assistant, the pre-meeting briefs are missing. Installing the Chief of Staff in week one would produce a one-section briefing — the calendar — and nobody installs a tool to look at their own calendar.
Two more reasons it goes here:
- The five upstream agents have produced enough output by week four that the briefing has something to assemble in week five. The compounding worked out across four prior weeks shows up here as a usable artifact.
- It is the agent that makes the rest of the system feel like a team rather than a collection. CEOs report that week five is when the stack stops feeling like "four AI tools I installed" and starts feeling like "the system that runs my mornings." The artifact is a single page. The reason it works is that four other agents produced the inputs.
Build this one in week five. The webinar recording and the rest of the Agent OS series live at nunncurtislabs.com/webinars.