Project personas · Claude Code + Codex

AI teammates that know your project.

A PM to keep work moving. Specialists for the questions that need a closer look. Each persona works from your project's tasks, epics, decisions, and memory, right inside your coding session.

Give each part of the work a clear owner.

Start with the PM, then enable the specialists your project needs. Solo developers and shared teams use the same project context and see the same board.

Project Manager

Enabled by default on new projects

Assesses project health, turns goals into a plan, and keeps priorities and tasks aligned with the work. The PM quietly fixes clear inconsistencies and brings important product decisions and blockers to you.

It can coordinate enabled specialists when your coding tool supports and permits delegation.

/tokanban:pm · $tokanban-pm

Architect

Technical direction

Explores design options, dependencies, and risks. Records the tradeoffs behind a decision so future sessions can understand why the project took that path.

/tokanban:architect · $tokanban-architect

Engineer

Implementation

Claims a specific task, implements the change, checks the result, and updates the board with verification evidence or a clear handoff.

/tokanban:engineer · $tokanban-engineer

Reviewer

Completion review

Checks delivered work against requirements, decisions, and task history. Looks for missing behavior and gaps in verification before recommending completion.

/tokanban:reviewer · $tokanban-reviewer

Researcher

Evidence and findings

Investigates a focused code, technology, or feasibility question. Preserves sources and reusable findings alongside the project.

/tokanban:researcher · $tokanban-researcher

Bring personas into your coding session.

Choose the roles for your project, then install the matching integration in the repository where you work.

1. Choose a project and enable its roles

Create a workspace or open your existing one. Go to Settings → Personas, choose a project, tick the roles you want, and save. Workspace owners and admins can change these settings.

New projects start with the PM enabled. Existing projects opt in. You can turn a persona off later without losing its identity or history.

2. Install the CLI and sign in

Use Tokanban CLI 0.5.0 or later for persona commands and bundled Codex skills. Run these in your terminal:

curl -fsSL https://app.tokanban.com/install.sh | sh
tokanban --version
tokanban auth login

Already installed an older CLI? Run the installer again and check that your shell finds the updated binary.

Build version 0.5.0 from source with Cargo
cargo install --locked --git https://github.com/emeraldsystems/tokanban --tag v0.5.0 --force

3. Install your coding tool's integration

Claude Code

Run these inside Claude Code:

/plugin marketplace add emeraldsystems/tokanban
/plugin install tokanban@tokanban

The plugin supplies the five persona commands, plus general Tokanban, setup, and memory skills.

Codex

Run these in a terminal from your repository:

tokanban init --harness codex --skills-only
tokanban init --harness codex --skills-only --yes

The first command previews the changes; the second installs the eight native skills in .agents/skills. Restart Codex if the skills do not appear.

For MCP and memory configuration too, use tokanban init --harness codex --yes. See the connection guide.

4. Give your PM a project and an objective

Replace PLAT with your project key. Send the prompt in your coding session:

Claude Code

/tokanban:pm Assess PLAT and plan our next feature.

Codex

$tokanban-pm Assess PLAT and plan our next feature.

Active in your session. Enabling a persona or assigning it a task does not launch a background worker. Personas act through your coding tool with the access and permissions you provide. Installations and project toggles are separate: you need both the integration and an enabled role.

Three useful places to start