Meet your Chief Content Officer.

Anyone can ask an AI to write a post. The output that gets scrolled past is the one that sounds like it came from anyone. The output that stops someone mid-scroll is the one that could only have come from you: your words, your stories, your way of explaining things.

That is why your Chief Content Officer reads your brain documents (your messaging, your ideal client's real language, your actual voice patterns) before it drafts anything. It is not writing generically and hoping it lands. It is writing from material that is already yours.

You already produce content every day without realising it: coaching calls, voice notes, client conversations, workshop recordings. The system's job is to catch that raw material before it disappears, turn it into standalone content ideas (called blocks), and then turn the strongest blocks into finished posts.

Your Chief Content Officer follows a simple rule at the mining step: only extract a block if it rates 7 or higher out of 10. Five strong ideas beat fifteen weak ones. It also never invents a story, a stat, or a quote. If the raw material does not contain it, the draft will not contain it either.

The hook is doing most of the work in any piece of content. Get it wrong and nobody reads the rest, no matter how good the body is. So before your Chief Content Officer writes a full draft, it gives you 3 to 5 hook options and waits for you to pick one. Only then does it write the body.

This comes straight from the Magnetic Content workshop: every piece is structured as Hook, Build, Insight, Invite, and the hook decides most of whether anyone reads the rest.

This is the same 10-80-10 rule from the workshop: you bring 10 percent (your raw material and your judgment on which hook lands), the AI does 80 percent (the structuring and drafting), and you finish the last 10 percent (the edit that makes it unmistakably yours). AI will never fully replace you, especially for content that is important to you.

The setup interview builds your content brain: your voice, your ideal client, your messaging, and an inventory of what you already have. It ends with your first real post, drafted and ready to publish, so you finish setup holding something you can post the same day, not just a folder of documents. It closes with a two-minute tour of your new system and a simple rhythm for your first week.

• The first time you run it, your AI will ask for permission to read and write files in this folder. That is normal, so approve it and carry on.
• Keep the unzipped folder somewhere easy, and open that exact folder in your AI tool. If the pack sits buried inside another folder, your agent cannot see it.
• If you use the Claude desktop app, add the pack folder as a project first, then talk to it there.
• If you use Codex instead, the folder includes instructions for both. Where something has only been tested in Claude Code so far, this page says so plainly.

Run /setup-content-os and tell it you are upgrading. It handles the rest, and nothing you built is lost.

Run /refresh-brain after anything real changes, a new offer, new positioning, a new kind of client. Beyond that, revisit the brain every 3 to 6 months. When drafts start feeling generic, that is the signal to update the source, not to abandon the system.

• Direct chat. Type or paste whatever you want to turn into content, right in the chat, nothing to organise.
• Voice notes. Dictate a messy, unpolished voice note with a speech-to-text tool (Wispr Flow works well), then feed it the text. Good for catching an idea the moment you have it.
• Meeting transcripts. Coaching calls, client conversations, workshops. We recommend Fathom as your call recorder, since it records and transcribes your calls for you. Drop a transcript in and run /mine-content. With a one-time setup you can have new transcripts export into a cloud folder that syncs to your ContentOS, so calls arrive on their own and you mine on your weekly rhythm. That route is for anyone comfortable with a little tech, and the simple drop-it-in way works for everyone.
• Recordings you already have. Got a call or workshop recording sitting on your computer? Get its transcript first, from your recorder or any transcription tool, then feed it the text.

A content block only gets created if it rates 7 or higher out of 10 for strength. Your Chief Content Officer would rather hand you five strong ideas than fifteen weak ones. It also never invents a story or a number. If the material is not there, the block simply does not get made.

Run /weekly-mine for a guided weekly ritual that walks you through mining your calls every week. It helps you gather last week's transcripts, drop them in, mine them, and review the strongest blocks.

• Run /draft-content to turn one block into a finished draft. It always starts with 3 to 5 hook options for you to pick from. Choose the one that feels right, and it writes the full piece around it.
• Run /plan-my-week to plan and batch-draft a week of content, sized to your tier. It reviews every ready block, proposes the week, and drafts the whole batch once you approve the plan.
• Ask for the daily sweep to turn each new coaching call straight into a ready post. Say "daily" or "morning" as you always have, and /mine-content now handles it: it sweeps the calls you have added since the last run, takes the single strongest angle from each, and drafts one finished piece per call. This is how you turn yesterday's calls into today's posts.

Every draft starts with hooks first. That is not a shortcut your Chief Content Officer skips, even when it is drafting several pieces in a row.

Say "review this" or run /review-content on any draft, whether you wrote it yourself or your officer drafted it. It checks the piece against your brain files and the pack's quality bar, names the single highest-value correction instead of burying you in notes, and tightens the draft with you once you give the go.

Download the zip, then tell your Chief Content Officer to install it and where the zip landed. It does the rest and tells you your new commands.