A persona is a job title for an assistant. Each one has its own skills, its own integrations, and its own private workspace, so you can hand it a goal the way you would hand it to a colleague. You are the CEO. You give the goal, the assistants do the work, and anything risky waits for your Approve, as your house rules require.
You do not need to pick the right assistant yourself. You write a goal in chat, and the CEO assistant reads it, chooses the persona that fits, and briefs it with the details it needs. The chosen assistant then works in its own workspace and reports back in the same chat.
You give a goal in plain words.
The CEO assistant routes it to the right persona. See routing.
The assistant works and shows its progress, its terminal, and its changes.
If a step is risky, it waits for your Approve in Approvals.
You get the result in chat.
If you already know who should do the job, name the assistant at the start of your message and routing is skipped.
PromptName the assistant yourself
Coder, look at the open issues on [repository] and tell me which one you would pick up first, and why.
A chat in StellarFirm is a session. A session can hold several assistants at once, all reading the same conversation. You can address one of them, or everyone.
Address one assistant by name at the start of a message: "Coder, ...".
Write a goal with no name and the CEO assistant plans it and hands each part to the right assistant.
Each assistant works in its own workspace, so they do not overwrite each other.
Every risky step from any of them lands in the same Approvals list.
Today the Coder is the only persona, so a session mostly holds one or more Coders. When the other personas open, the same session will let a Product owner write the ticket, a Coder build it, and Marketing announce it.
PromptPlan a goal across the team
Team, our goal this week is [goal]. Break it into parts, tell me who does what, and start with the parts the Coder can do now.
You can run more than one Coder. Each Coder has its own name, its own focus (for example "UI engineer" or "backend engineer"), its own repository, its own login to your source host, and its own workspace. They run side by side, so a UI change and a backend change can move at the same time.
Address a Coder by its name, or let the CEO assistant route the message by focus or by the repository it names. Set them up under Coders in Settings. See the Coder for details.
PromptSplit work between two Coders
UI Coder, build the [component] on [repository-one]. API Coder, add the endpoint it needs on [repository-two]. Tell me when each pull request is ready.