<aside> 💡 Use case: your first full pass through the system. You fill five files, run the weekly loop once, hand one job to a department, review the draft, approve it, and fire one playbook. By the end you have seen every part of the loop work on your own brand.

</aside>

Step 1. Fill the 5 first files

<aside> 📝 Open each file and replace every [FILL IN: ...] prompt with your own words. Short and true beats long and vague.

</aside>

File What to put in it Template on
owner/brand-voice.md How you sound, words you use, words you never use Owner inputs
owner/approval-bar.md What may go out without you, and what always waits Owner inputs
brand-os/brand-brain/voice-guide.md Your voice in detail, with lines that sound like you /brand-brain
brand-os/brand-brain/tone-rules.md The rules the voice check tests every draft against /brand-brain
brand-os/content/content-calendar.md What is due, on which channel, with at least one item marked ready /content

<aside> ⚠️ Also fill owner/budget-cap.md and owner/positioning.md, even with one line each. The orchestrator reads all four owner files and stops if any of them still contains a [FILL IN: prompt. If you do not want any spend yet, say so in budget-cap.md.

</aside>

<aside> 📥 Optional: if you have this week's exports from a tool you already use (Google Search Console, Google Business Profile, Meta Business Suite), save them into brand-os/signals-seo/ now. With no exports, the orchestrator plans from your content calendar alone.

</aside>

Step 2. Start Claude Code in the project folder

cd ~/Documents/ai-social-media-team
claude

Step 3. Run the weekly loop

<aside> 🎛️ Ask the orchestrator to run the week:

</aside>

Use the orchestrator agent to run this week's loop.

<aside> 👀 What you should see:

The orchestrator does not draft anything itself. It decides and briefs.

</aside>

Step 4. Hand one item to the Content engine

<aside> ✍️ Pick one brief from the hand-off list that names content-engine and hand it over. Use the real file name from your drafts/briefs/ folder.

</aside>

Use the content-engine agent on drafts/briefs/<the brief file name>.md

<aside> 👀 What you should see: a new draft in drafts/YYYY-MM-DD-<channel>-<slug>.md, a pass or fail on the voice check, and a list of anything marked [VERIFY]. If the voice check failed, the draft sits in queue/held-for-voice-review.md with the rule it broke.

</aside>

Step 5. Review the draft

<aside> 🔍 Open the draft and read it as your customer would. Then ask:

</aside>

Show me the draft you just wrote, the three hook options, the voice check result and every [VERIFY] mark. Do not change the file.

<aside> 🧠 If something sounds wrong, do not just fix the draft by hand. Change the rule that let it through, in brand-os/brand-brain/tone-rules.md or voice-guide.md, and run Step 4 again. A new version is saved with -v2 on the end, so nothing is overwritten.

</aside>