Routing is how a message you write ends up with the right assistant. You can steer it yourself by naming an assistant, or leave it to the CEO assistant.
Start your message with the assistant's name and it goes straight there.
PromptSend straight to the Coder
@coder fix the failing tests on [repository] and open a pull request for review.
Putting @, /, or persona: in front of the name all work, for example /coder ... or persona: coder .... The prompts in these docs often open with "Coder," in plain words, which the CEO assistant reads as addressing the Coder. The @ form is the surest way to skip routing completely.
If you name nobody, the CEO assistant looks at what the message is about. Words like build, fix, tests, pull request, and CI point to the Coder. Other subjects point to other roles.
The message is about
Belongs to
Status
Building, fixing, tests, pull requests, CI
Coder
Available
What to build, priority, acceptance criteria
Product owner
Coming soon
Campaigns, launch posts, waitlists
Marketing
Coming soon
Invoices, expenses, budgets
Accountant
Coming soon
Contracts, terms, privacy wording
Legal
Coming soon
Only available assistants receive work. A role that is Coming soon is never chosen.
If a message could belong to more than one role, or does not clearly belong to any, the CEO assistant does not guess. It takes the safe path: it asks you which assistant you mean, or what you want done.
You can avoid the question by writing a clearer goal. See write a good goal.
You can run more than one Coder. When you do, the CEO assistant decides which Coder takes each message, so separate goals can move in parallel, each in its own workspace. You can also name a Coder at the start of a message.