Personas and playbooks
A playbook lists the stages a piece of work goes through, and each stage is run by a persona. You can use the built-in playbooks as they are or make your own to fit how your team works.
A persona is the kind of expert a runner acts as, such as Coder, Researcher or Architect: it decides how the runner works and what it hands back. A single task runs as one persona, picked when you start it. A playbook chains several, so one piece of work can be analyzed, built and reviewed in turn. Playbooks live under Settings, Customize, Playbooks; everyone can read them, and the Owner or Admin role can create and change them. A task runs one of your own playbooks when your organization's plan includes Playbooks.
Start with the first two guides, then use the rest to shape how a playbook's stages run:
- Create a playbook — from scratch or by duplicating a built-in, then add and arrange its stages.
- Choose a persona for a task — pick the expert that runs a task, and what each one hands back.
- Get marketing copy written in your voice — start a Marketer task for a page, post or email, pick its headline, and review the copy.
- Answer the questions about your new app — answer what the App Wizard asks about it, its logo included.
- Run a playbook on a task — start a task that runs one of your playbooks.
- Check what a playbook does before you run it — read its chain, its stages and their prompts, without changing anything.
- Set what a stage waits for — run a playbook's stages one after another or side by side.
- Repeat a stage for each planned item — a Plan stage splits the work, and a later stage runs once per item.
- Choose when a stage asks questions — set Full Auto and each stage's Asks questions, so a stage stops for your answer or runs straight through.
- Add instructions to a playbook stage — give one stage your team's own rules, and check them in its prompt.
- Set how senior a playbook stage is — pick the playbook's default seniority and a stage's own, which sets its model tier.
- Review a stage's mockups — click through the screens a Business analyst or Architect stage mocked up, before anything is built.
- Fix a playbook's errors — find a playbook marked ✕ or !, see which field or stage each problem belongs to, fix it and save.
- Group playbooks into folders — name playbooks like
Payments/Bug fixand switch the list to Tree view to see them by folder. - Add a requirements stage to a playbook — put an Analyst stage that writes a PRD before the stage that codes, and check the coder receives it.
- Add a design stage to a playbook — put an Architect stage that writes an Architecture document before the stage that codes.
- Add a review stage to a playbook — end a playbook with a read-only Reviewer stage, and choose whether it may file follow-ups.
- Change what a playbook stage hands back — pick a stage's Deliverable and check when it ends, whether it may change code and what it may file.
- Offer a playbook stage a choice of experts — set Expert to User selects, tick the allowed experts and pick the default.
- Reorder a playbook's stages: move a stage up or down, check what it now waits for, and fix any waiting loop before saving.
- Remove a stage from a playbook — take a stage out, then fix the stages that waited for it or were created by it before saving.
- Edit a playbook — change a playbook's fields or stages and save, or leave without saving through Unsaved changes.
- Rename a stage: change a stage's Label and Key, and fix the stages that named the old key.
- Delete a playbook — remove one of your own playbooks from its row menu or its page.
The fields of a playbook and a stage are described in the Playbooks reference, and what each persona does in Persona details. How personas and playbooks fit with tasks and epics is in How personas and playbooks work.