<aside> 🚀 How I run 6 AI agents 24/7 for — and how you can deploy the same system in an afternoon.

</aside>

Why One AI Agent Isn't Enough

One agent doing everything is like hiring one employee for sales, marketing, ops, engineering, and customer support. They'll be mediocre at all of it.

The fix: specialists. One brain that routes work to agents that each do one thing extremely well.

That's the orchestrator pattern. It's how I run my entire content operation — carousels, Twitter threads, daily briefings, engagement tracking, lead magnets — without touching any of it manually.

The Orchestrator Pattern

The orchestrator is your main agent. It never executes tasks. It only routes them.

You text it: "Make a carousel about AI agents."

It thinks: That needs a content specialist.

1. Spawns the carousel agent with a clear brief
2. Carousel agent writes copy + image concepts
3. Spawns the image agent with the concepts
4. Image agent generates + styles the visuals
5. Orchestrator validates format, uploads, pushes to Notion
6. Sends you the finished product

<aside> 🔥 One message in. Finished carousel out. No human in the loop.

</aside>

How to Design a Sub-Agent

Every agent needs a SOUL.md file. This is their identity — what they do, how they do it, what they never do.

A good SOUL.md has 5 parts:

• Role — One sentence. What is this agent?
• Input requirements — What does it need to start working?
• Output format — Exactly what it delivers
• Constraints — What it never does (prevents scope creep)
• Quality standards — How to know if output is good