AI Chief of Staff Agent: The Persona, the Guardrails and the First Week
Updated: November 12, 2026 · By Brian Arrington (Founder, AI Consultant and Business Coach)*
The short answer
An AI chief of staff agent runs a leader's operating rhythm. It reads your calendar, inbox, goals and meeting notes, then drafts a daily brief, a decisions log, an action tracker and a weekly summary. It drafts only. You approve anything it would send, post, pay or schedule.
This article is about an AI agent, not about hiring a person for the role. Below is the role, what to feed it, the guardrails it needs, and a simple first week, built on the agent called "Chief" from the BotPlaybooks library.
What an AI chief of staff agent does (and does not do)
The job is follow-through. The agent called "Chief" has a one-line job on its public page: it "Runs the operating rhythm for a leader: priorities, meeting prep, follow-through and decisions." [7]
xAI's own Grok Bot docs list Chief of Staff as a use case, with the outcome it owns described as "a source-linked digest of what changed and what needs attention." [3] Every item should point back to where it came from.
What it does not do is act on your behalf without asking. It does not send the email, accept the meeting, post the update or pay the invoice. It prepares those things, and you decide.
What is an AI chief of staff agent? An AI chief of staff agent is an AI agent given the job of running a leader's operating rhythm. It reads your calendar, inbox, goals and meeting notes, then drafts a daily brief, a decisions log, an action tracker and a weekly summary. It prepares the work, and you approve anything that goes out.
What to give it and what you get back
The page for the agent called "Chief" lists its inputs as "your calendar, inbox (read), goals or OKRs, meeting notes, and who owns what," and its tools and connectors as "Calendar, email (read, drafts only), notes, task or project app, shared docs for the decision log." [7] Here is how each input feeds the work.
| What you give it | Why it matters | What it feeds |
|---|---|---|
| Calendar | Shows what is coming and what needs prep | The daily brief |
| Inbox | Holds the asks, promises and loose ends | The action tracker |
| Goals or OKRs | Tells it what matters most this quarter | Your priorities in each brief and summary |
| Meeting notes | Record what was agreed and by whom | The decisions log |
Every tool on that list reads or notes. None sends. xAI's advice for any new Bot fits here: "Every example stops for your review. Keep sending, publishing, purchasing, and production changes behind approval." [3]
Start read-only, and widen access only once you trust the briefs.
The guardrails every chief of staff agent needs
A chief of staff agent sees your calendar, email and plans, so the rules matter more than the prompt.
The guardrail on Chief's page is one line: "Drafts only: it never sends, posts, pays or contacts anyone without your approval, and never invents facts." [7]
Three guardrails cover most of the risk.
- An approval line. Anything that leaves your desk goes through you. xAI's approvals page says to "Keep sending, publishing, purchasing, deletion, and production changes behind approval." [4] In Grok Bot, when an action needs approval, "the conversation shows the proposed operation and its inputs," and you can choose Allow once, Always allow or Deny. [4]
- No invented facts. Ask the agent to mark anything it could not confirm, such as a due date nobody stated or an owner nobody named. A brief that says "not confirmed" is more useful than one that guesses.
- Sources on every item. Ask it to link each item in the brief back to the email, invite or note it came from, so you can check it in a few clicks.
What guardrails should an AI chief of staff have? An AI chief of staff agent should draft only and never send, post, pay or contact anyone without your approval. It should never invent facts, and it should mark anything it could not confirm. It should also link each item back to its source, so you can check the email, invite or note behind it.
Your first week with Chief (5 steps)
A suggested plan. Change the pace to fit your week.
- Monday: get a brief. You could start with the example first task from Chief's page: "Act as my chief of staff this week. Start with tomorrow's brief, then set up a decision log and action tracker from my last three meeting notes." [7] Note what was useful and what was noise.
- Tuesday: add your goals. You could share your goals or OKRs and ask for a short priorities list tied to them.
- Wednesday: start the decisions log. You could give it notes from one or two recent meetings and ask it to pull out each decision, who made it and when.
- Thursday: start the action tracker. You could ask it to list open actions from your inbox and notes, with an owner and a due date for each. Anything without an owner or date should be marked, not filled in.
- Friday: ask for the weekly summary. You could ask for the weekly summary, then write down what you want changed: a shorter brief, a different order, fewer items. Those changes become lasting rules in the agent's setup.
xAI's docs suggest the same habit for the Chief of Staff use case: "Tune the Bot by marking what was useful and what was noise. Then schedule the digest for a time you can review it." [3] Set a routine only once you would actually read the brief.
Give Chief a small team
A chief of staff can hand specific jobs to specialists. Here is one way to arrange it, with each persona described from its public page.
- The agent called "Helm" (CEO) sits above Chief. It sets the week's priorities. Its page says you get back "A Monday priorities memo, a delegation table (task, owner agent or person, brief, due date), and a Friday CEO review with a decisions-needed list." [8]
- The agent called "Docket" (Inbox Triage Assistant) "Sorts your email, team chat and DMs into act, reply, read and archive, drafts the replies, and can send a read-only brief of just the top 3 urgent items." In brief mode its page says you get back "only the top 3 urgent items with source links and one suggested next step each." [9]
- The agent called "Agenda" (Meeting Agenda and Minutes Keeper) prepares "An agenda before; minutes (attendance, decisions, motions if any, actions, open questions) plus a recap draft after." [10]
- The agent called "Book" (Scheduling Coordinator) handles time. You get back "3 time options, a draft invite and a draft message." [11]
Chief keeps the rhythm, and the others feed it. Helm's priorities shape Chief's briefs. Docket's urgent items and Agenda's minutes feed the action tracker and decisions log. Book drafts the time options when a follow-up meeting is needed. All four carry the same drafts-only guardrail on their pages.
Don't build the whole team on day one. xAI's Bot docs say to make a separate Bot when the work has its own goal, tools, approval boundary or schedule, and to start with the smallest useful roster. [1] Start with Chief, and add a specialist when the same kind of task keeps coming up.
Some Grok Bot users already work this way. One user on X described their setup as Grok Bot acting as "chief of staff, with ~10 specialist bots under it." [12]
Set it up in your tool
Every BotPlaybooks persona is one plain Markdown file with a role, inputs, workflow, output format, guardrails, tools and connectors, routines and an example first task. Here is where it goes in each tool. Full steps are on the setup page.
Grok Bot. Grok Bot has no SOUL.md. In your main Grok Bot, use the plus button to give it the persona's Markdown file. Tell it to take that file and build the persona as a new agent. If you already have a CEO bot, tell it that Chief reports to it. Then send the Example First Task.
Hermes and OpenClaw. Both use a SOUL.md file. Hermes' docs call SOUL.md the agent's primary identity and put project rules in AGENTS.md, so paste the whole persona, including its standing approval rules, into SOUL.md and keep only project-specific instructions (commands, paths and repo conventions) in AGENTS.md. [5] OpenClaw's guide says: "Keep AGENTS.md for operating rules; keep SOUL.md for voice, stance, and style." [6] For OpenClaw, you can paste the whole Persona / System Prompt into SOUL.md, or split it: voice and boundaries in SOUL.md, workflow and output format in AGENTS.md. See SOUL.md templates for business agents for the split.
Muse. Back up Soul.md first, then paste the prompt at the end under its own heading (for example "## Persona: Chief"), and set the name to Chief in Identity. Meta describes Soul.md as "Who your Muse is, including core truths, boundaries, and personality." [13]
OpenAI Dots. Send your dot the prompt as its working instructions, then turn the guardrails into Custom Rules, such as "Ask before sending any email." [7][14]
FAQ
What is an AI chief of staff agent?
An AI chief of staff agent is an AI agent given the job of running a leader's operating rhythm. It reads your calendar, inbox, goals and meeting notes, then drafts a daily brief, a decisions log, an action tracker and a weekly summary. It prepares the work, and you approve anything that goes out.
What is a good AI chief of staff prompt?
A good AI chief of staff prompt has five parts: the role, the inputs it reads, the workflow it follows, the output format for each brief or log, and the guardrails. The guardrails should say it drafts only and never invents facts. The Chief of Staff persona page on BotPlaybooks lists the inputs, outputs and guardrails.
How do I build a chief of staff AI agent?
Pick a platform such as Grok Bot, Hermes, OpenClaw, Muse or OpenAI Dots. Load the chief of staff persona the way your tool expects. Connect your calendar, email and notes with read-only access. Run one real task, such as tomorrow's brief, review it, and keep anything it would send behind your approval.
Can an AI chief of staff send emails for me?
It can draft them, and that is where it should stop. Keep sending behind your approval, so the agent prepares the reply and you choose whether it goes out. The Chief persona is built this way: it never sends, posts, pays or contacts anyone without your approval, and it never invents facts.
Which tools work with the Chief persona?
The Chief persona works with Grok Bot, Hermes, OpenClaw, Muse and OpenAI Dots. In Grok Bot, use the plus button in your main Grok Bot to give it the Markdown file and tell it to build the persona as a new agent. If you already have a CEO bot, tell it that Chief reports to it. In Hermes the persona goes in SOUL.md, and only project-specific instructions go in AGENTS.md. In OpenClaw you can split it, with voice and style in SOUL.md and operating rules in AGENTS.md. In Muse it goes in Soul.md, and in OpenAI Dots it becomes the dot's working instructions.
Is an AI chief of staff the same as a CEO agent?
No. A CEO agent sets the week's priorities and delegates the work, like the agent called "Helm" with its Monday priorities memo and delegation table. A chief of staff agent runs the rhythm under those priorities: the daily brief, the decisions log, the action tracker and the follow-through.
Give your week a chief of staff
Give your week a chief of staff: get the Chief persona on botplaybooks.com.
Want to try a persona first? Get a free persona. You can also browse the library of 175+ personas, or see the Leadership and C-Suite Pack and the Operations and Admin Pack for Helm, Docket, Agenda and Book.
We add new personas regularly, and All-Access includes every one.
Which part of your week would you hand to a chief of staff agent first?
Related guides: SOUL.md Templates for Business Agents.
Sources
Official pages, read October 21, 2026. Persona pages read the same day.
- Grok Bot, create and manage Bots: https://docs.x.ai/grok-bot/bots
- Grok Bot, overview: https://docs.x.ai/grok-bot/overview
- Grok Bot, use cases: https://docs.x.ai/grok-bot/use-cases
- Grok Bot, approvals, security and privacy: https://docs.x.ai/grok-bot/approvals-security-and-privacy
- Hermes Agent, personality and SOUL.md: https://hermes-agent.nousresearch.com/docs/user-guide/features/personality
- OpenClaw, SOUL.md personality guide: https://github.com/openclaw/openclaw/blob/main/docs/concepts/soul.md
- BotPlaybooks, Chief of Staff persona: /personas/chief-of-staff
- BotPlaybooks, CEO persona: /personas/chief-executive-officer-ceo
- BotPlaybooks, Inbox Triage Assistant persona: /personas/inbox-triage-assistant
- BotPlaybooks, Meeting Agenda and Minutes Keeper persona: /personas/meeting-agenda-minutes-keeper
- BotPlaybooks, Scheduling Coordinator persona: /personas/scheduling-coordinator
- X post describing Grok Bot as a chief of staff: https://x.com/maikunari/status/2112146986556154131
- Meta, Muse Identity, Soul and Memory files: https://www.meta.com/help/artificial-intelligence/2225571704857152/
- OpenAI, Dots: https://learn.chatgpt.com/docs/dots
AI can make mistakes. Always review outputs before acting. Personas are templates, not legal, financial, tax, medical or HR advice.
BotPlaybooks is independent and not affiliated with xAI, Meta, OpenAI, Nous Research, OpenClaw or any agent platform.
Brian Arrington is an AI consultant and business coach, the founder of BotPlaybooks and of Arrington Consulting LLC, a retired USAF Master Sergeant, and the 2025 Georgia Vetrepreneur of the Year.