Run each project as a channel with a roster and a Notion boa

How this helps you

Each project gets its own space and status board, so Bots stop mixing projects and you see what is blocked at a glance.

✦ Try it

Write a Project Ops skill for yourself. When I start a project: add it to my Notion Projects database, open a group chat named after it, and propose a roster. Reuse my existing Bots first, propose at most [5] Bots besides you, and only suggest a new Bot if nothing fits, after I say yes. Track tasks in my Tasks database. If a Bot gets stuck, it marks the task Blocked and pings me in the channel.

Fill in: [5] is the cap on Bots per project; the author used five plus the PM.

What they did

Eric Zakariasson ran his Bots as separate chats (Coder, Writer, Researcher) until juggling several projects made it hard to keep them in sync. So he copied how human teams work. He made two Notion databases, Projects and Tasks, and a projects Manager Bot with a Project Ops skill that creates a project, opens a channel in the sidebar and staffs it. Staffing rules: reuse existing Bots first, propose at most five Bots besides the PM (six per channel, a number he picked), and create a new Bot only when nothing fits and only after he says yes. He scopes tasks with the roster in the channel. When a Bot gets stuck it marks its task Blocked and pings him there.

Who it's for: People running two or more projects at once with a bench of specialist Bots.

Before you start

Notion connected to the Bot that will manage projects.
A few working specialist Bots to staff projects with.
Comfort with group chats and skills.

How to try it

Create two Notion databases: Projects and Tasks (with a Blocked status).
Make a projects Manager Bot.
Ask it to write a Project Ops skill that creates a project entry, opens a group chat for it and proposes a roster.
Add the staffing rules from the guide to that skill.
Start a project, then scope the tasks in the channel with the roster.
Watch the board. Step in when a task goes Blocked.

What to expect

One sidebar channel per project, a roster of Bots plus you, and cards moving across a Notion board, with Blocked cards pinging you.

Common mistakes

Letting it create new Bots freely. The guide's rule is reuse first, and new Bots only with your yes.
Treating it as finished. The author says it is an experiment.

Related tips

Use a group thread to watch Bots work together: Put several Bots in one chat so you can see every handoff instead of hidden Bot-to-Bot messages.
Start with a chief of staff Bot: Talk to one coordinator Bot and let it hand work to your specialist Bots.
One job per Bot: Give each Bot one job and a list of things it never does.