use case · orchestration
Projects Bot
One channel per project, staffed from the bench. Stuck bots ping you.
eric zakariasson used to run Grok Bots as separate chats — Coder, Writer, Researcher — and it broke as soon as several projects ran at once. Signal got lost. Bots drifted out of sync.
So he copied how human teams work. Two Notion databases (Projects, Tasks) plus a Projects Manager bot with a /Project Ops skill: create the project, open a dedicated sidebar channel, staff it. One project equals one channel, and the roster lives in that channel with him.
Staffing rules: reuse existing bots first; at most five specialists besides the PM (a six-bot cap he admits is arbitrary); create a new bot only when nothing on the bench fits, and only after he approves. In the channel he scopes tasks with the roster; the PM mostly watches and keeps the databases current. A stuck bot marks its task Blocked and pings him.
The more he builds on it, the more it resembles a system initially built for humans: a board, a manager, specialists claiming tasks, a blocked column, a channel.
This was the post inside the Aug 27 trending topic "SpaceXAI Engineer Builds Grok Bot Project Teams with Notion and Channels" — 209K views.