# Personas

> Meet the assistants in your StellarFirm company: the Coder is available now, and Product owner, Marketing, Accountant, and Legal are Coming soon.

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](/docs/ceo/house-rules) require.

## What a persona is

A persona bundles four things:

- **A role.** What the assistant is for, such as writing code or drafting a campaign.
- **Skills.** Step-by-step playbooks it follows for common jobs, such as "fix CI" or "draft a payment reminder".
- **Integrations.** The tools it is allowed to use, such as GitHub for the Coder.
- **A workspace.** A private computer of its own, so one assistant's work never lands in another's files.

## The five personas

| Persona | Status | What it does |
| --- | --- | --- |
| [Coder](/docs/personas/coder) | Available | Turns goals and tickets into tested code changes, and takes them as far as your house rules allow. |
| [Product owner](/docs/personas/product-owner) | Coming soon | Triages the backlog, writes clear issues, and drafts stakeholder updates. |
| [Marketing](/docs/personas/marketing) | Coming soon | Drafts campaign briefs, launch posts, emails, and social posts, and finds your assets. |
| [Accountant](/docs/personas/accountant) | Coming soon | Triages invoice mail, summarizes expenses, and drafts invoices and reminders. |
| [Legal](/docs/personas/legal) | Coming soon | Builds review checklists for contracts and policies, and drafts correspondence. Not legal advice. |

> [!NOTE]
> Today the Coder is the one persona you can use. The other four pages describe what each will do when it opens, so you can plan your company ahead of time.

## How the CEO briefs them

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.

1. You give a goal in plain words.
2. The CEO assistant routes it to the right persona. See [routing](/docs/ceo/routing).
3. The assistant works and shows its progress, its terminal, and its changes.
4. If a step is risky, it waits for your Approve in [Approvals](https://stellarfirm.ai/app/approvals).
5. 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.

```prompt title="Name the assistant yourself"
Coder, look at the open issues on [repository] and tell me which one you would pick up first, and why.
```

## Several assistants, one goal

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.

> [!SOON]
> Mixed teams of personas in one session arrive as the other personas open.

```prompt title="Plan 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.
```

## Several Coders at once

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](https://stellarfirm.ai/app/settings). See [the Coder](/docs/personas/coder#several-coders) for details.

```prompt title="Split 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.
```

## In this section

| Page | What it covers |
| --- | --- |
| [Coder](/docs/personas/coder) | Skills, how it works, integrations, prompts, limits. |
| [Product owner](/docs/personas/product-owner) | Coming soon: backlog and requirements. |
| [Marketing](/docs/personas/marketing) | Coming soon: campaigns and launch copy. |
| [Accountant](/docs/personas/accountant) | Coming soon: invoices and expenses. |
| [Legal](/docs/personas/legal) | Coming soon: checklists and drafts. |

Ready to put them to work for a specific kind of company? See the [playbooks](/docs/playbooks).

---

Source: https://stellarfirm.ai/docs/personas