How to Set Up an AI Chief of Staff (One Agent That Routes Everything)

This week Claude handed me a genuinely trash sales page, and it was my fault. I'd skipped my own system: instead of routing the task through my chief of staff agent, I asked for the page directly in a fresh context. The draft ignored every sales framework we use, because nothing had told it those frameworks exist. One question ("why doesn't this follow our exact frameworks?") sent it back to our examples and instructions, and the redo was nearly final. A page that takes me 90 minutes by hand took about 20.

That failure is the best explanation of what a chief of staff agent is for. It's one router that sits in front of everything: you hand it any task, it figures out what kind of work it is, and it loads the right specialist instructions before a single word gets drafted. You stop depending on your own memory to give the AI the right context every time, which, as I proved this week, fails.

Step 1: Build your specialists first

A router needs somewhere to route. In my setup, each role is its own instruction file: a copywriter file with our sales frameworks and examples, a content file with voice rules, a strategy file, and so on, organized like an org chart inside one folder. (The folder structure that makes this possible is the second brain setup; the standards inside each file start as a rules doc.) You don't need ten roles on day one. Two or three files covering the work you delegate most is a real system.

Step 2: Write the router doc

The chief of staff itself is one instruction file with three jobs:

• Intake. For every task, pin down four things before working: who it's for, what kind of work it is, what the finished deliverable looks like, and when it's due.
• Routing. A plain list mapping work types to specialist files: "sales pages, launch emails → copywriter file. Social content → content file." Write it like you'd explain it to a new assistant.
• The no-fit rule. If a task doesn't match anything, it asks you instead of winging it. This one line prevents most confident-but-wrong output.

Here's a starter you can adapt:

You are my chief of staff. For every task I give you:

1. Identify: who it's for, the type of work, the exact deliverable,
   and the deadline.
2. Find the matching role instructions in [folder] and follow them
   completely before drafting anything. My routing list:
   - Sales pages, offers, launch copy -> [copywriter file]
   - Social posts, captions -> [content file]
   - Strategy, planning -> [strategy file]
3. If nothing matches, tell me what's missing and ask how to
   proceed. Do not improvise a process.
4. Before delivering, check the work against the role's standards
   and flag anything that falls short.

Step 3: Save it where it always loads

Make it the standing instruction for your workspace (a project instruction, a skill, or the top-level README of your folder) so it runs without you remembering to invoke it. The entire value is that it works on the days you're moving too fast to be careful. Ask me how I know.

Step 4: Route everything for a week

Even tasks that feel too small. What you're actually testing is the routing list; every time the router asks a question you didn't expect, that's a missing specialist file or a vague standard, and each fix compounds.

FAQ

Is this a separate AI product I have to buy? No. It's an instruction file sitting in front of the AI you already use. The "agent" is the system, not a subscription.

How is this different from one big prompt with everything in it? One mega-prompt buries the sales frameworks under the social rules under the strategy notes, and quality drops as it grows. A router loads only what the task needs, and each specialist file stays small enough to maintain.

What does this actually fix day to day? The generic-first-draft problem. Most "the AI missed the mark" moments are really "nothing told it which standards apply." The router makes that connection automatic instead of memory-dependent.

Do I need a team for this to make sense? No. Solo operators might get the most from it, because you're the only quality gate you have. The router is the colleague who says "shouldn't this follow your sales framework?" before the draft exists.

Draft notes (internal, strip before publish)

• De-internalized from the L12 chief-of-staff agent (routing matrix, intake fields, no-fit protocol) with all internal specifics (task IDs, agent names, ClickUp integration, client examples) removed per the internal-structure rule.
• The sales-page story matches take 0005: 90 minutes → 15-20, framework question fix, "my bad for not routing it." Numbers kept consistent with the video.
• Starter prompt is written for this guide, not her literal production router; flag to Audrey in review in case she wants to publish a closer version.