11 agents, one editor

Who does what

Plan

• PlannerKeeps the calendar full and picks next week's topics.
• ResearcherChecks trends and facts. A number it can't trace to a source doesn't go in.

Make

• WriterTurns a planned row into a post, a thread or a reel script.
• DesignerBuilds the reels and images. Faceless, with an AI voiceover.

Check

• ReviewerSays no. Catches hype words, missing sources and posts that run too long.
• Humanization EditorThe last edit. Takes out lines that sound machine-written.

Ship

• PublisherPosts approved rows on time through Meta's official API.
• CommunityDrafts replies to comments. Chief OKs them before anything goes out.

Learn and run

• Social Media AnalystReads the numbers every evening and writes a weekly report.
• DevOpsKeeps the site, the board and the scheduled jobs running.
• CoordinatorHands out the work and posts a daily update.

Approve

• Chief, the editor-in-chiefReads every post and every reply before it goes out. Approves the week in one sitting on Sunday.

How a post moves

The team hands off through one spreadsheet, not through chat. Every post is a row, and its status says whose turn it is.

1. Planned
2. Drafted
3. Reviewed
4. Edited
5. Ready for review
6. Approved
7. Posted

A row that fails a check goes back a step with a note on what to fix. Approved rows are posted on schedule. Nobody has to press a button.

The boring rules

• One agent, one job. If a job needs two prompts, it's two agents.
• The maker never checks its own work. A separate Reviewer does, with a different prompt.
• No source, no number. If a stat can't be traced to where it came from, it gets cut.
• Nothing ships without Chief's OK. That covers posts, replies and comments.
• Automate last. Get the manual steps working first, then let a script take over.

What it takes

Hosting is a free static site. The full setup, with the job descriptions and prompts, goes into the free guide.

Watch it run

The reels show the team at work. The Threads posts go into how each piece is built.