Playbooks
A playbook is an ordered list of stages. Each stage pairs an expert with a deliverable. Playbooks are marked Preview, and available when your organization's plan includes Playbooks. A new task can then run one of your organization's own playbooks. The built-ins can't be run this way. Without Playbooks on the plan, the Playbooks tab is hidden and the page's address shows Not on your plan.
How playbooks work: How personas and playbooks work. Guides: Run a playbook on a task, Create a playbook, Edit a playbook and Fix a playbook's errors.
Who can do what
| You are | You can |
|---|---|
| Anyone in your organization | Open the list, open any playbook and preview its stages' prompts |
| An Owner or Admin of your organization | Also create, duplicate, edit and delete your organization's playbooks |
If you can't edit playbooks, the page has no New playbook button and no ⋯ row menus, and a playbook opens with the note "You can view this playbook but not edit it."
The Playbooks list
Open it from the sidebar: select Settings, then Playbooks under Customize.

At the top:
| Item | What it does |
|---|---|
| Tree view button | Switches between a flat list and a tree. In the tree, names that use / are grouped as folders, each marked ◈ with its playbook count; a playbook inside one shows the part of its name after the last /, and its ⋯ menu adds Full name. See Group playbooks into folders. |
| New playbook | Starts a new playbook. Requires the org admin role. On a phone it shows as +. |
| Search | Narrows the list to playbooks whose name or description contains what you type. |
A search that matches nothing reads Nothing matches these filters, with Clear filters. Your search and your view stay as you left them the next time you open the tab.
The list has these groups, each heading followed by how many playbooks it holds, such as Built-in 3:
- Built-in: the three playbooks every organization has. They're read-only and carry a lock mark.
- Your playbooks: the playbooks your organization made. This group appears once you have one; until then, Owners and Admins see the list end with "No playbooks of your own yet".
Each row shows:
| Item | Meaning |
|---|---|
| Mark at the start | ✓ valid; ! valid with warnings (the count is in its label); ✕ has errors. Open the playbook to see what to fix. |
| Name | Hover it to read the playbook's description. |
| Lock, after the name | A built-in playbook. Its label reads "Built-in: duplicate it to edit a copy". |
| Stage count | How many stages it has, for example "5 stages". |
| Age | For your own playbooks, how long ago it was last changed. Hover for the exact time. |
| ⋯ | The row menu: Open or Edit, Duplicate, and Delete for your own playbooks. Requires the org admin role. Delete first asks Delete playbook? ("This cannot be undone."); confirm with Delete. |
The built-ins:
| Built-in | What it does |
|---|---|
| Task | One expert does one piece of work. Coder by default; pick another when you start it. |
| Sketch | A UI prototyper draws a quick mockup. |
| Epic | Analyze, design and plan, then build each planned item as its own pull request and review the result. |
On a phone the stage count is hidden. The Preview mark sits on its own line above Search.

The playbook editor
Select a playbook's name to open it. On a wide screen it opens in a pane beside the list:
- ⤢ (Maximize pane) gives the playbook the full width; ⤡ (Restore pane) brings the list back. This browser remembers a maximized pane for every editor, not just playbooks, until you restore it.
- ✕ (Close pane) closes it.
- Hover any of these buttons to read its name.
- Drag the line between the list and the pane to resize them.
On a narrow screen, such as a phone, the playbook opens as a full page instead.

Beside the playbook's name sits the Preview mark, after a lock on a built-in. A built-in opens read-only, with the note "Built-in playbooks are read-only. Duplicate it to edit a copy.", Duplicate at the top for Owners and Admins, and Back at the bottom. For Owners and Admins, your organization's own playbooks open for editing, with Duplicate and Delete at the top and Cancel and Save at the bottom. Delete asks Delete playbook? before it removes anything. Duplicate copies the saved playbook, so it stays off while you have unsaved changes; hover it for "Save or cancel your changes first". Everyone else sees them read-only, with Back at the bottom.

The editor has two tabs, and Save at the bottom saves both:
| Tab | What it holds |
|---|---|
| Playbook | The playbook's own fields and its chain. It opens first. |
| Stages (N) | One card per stage; N is the stage count. |
A change on one tab is kept while you look at the other. Save stays unavailable while the playbook has an error. If a save is still refused, Jaah switches to the tab with the first error, opens its stage card and puts the cursor in the field to fix.

Field explanations
Hover a field's label, or tap it on a phone, to read what the setting does. When there's more to say, the tip ends with More: it opens a fuller explanation and, for a menu, what each option does. The stage fields and the facts set by the deliverable carry the same tips.

The playbook fields
| Field | Meaning |
|---|---|
| Name | Required. Unique within your organization. Shown in the new task's Playbook menu. |
| Full Auto | On or Off: the default for whether the stages may stop to ask questions. |
| Default seniority | Junior, Mid or Senior: the seniority every stage uses unless it sets its own. It decides the model tier (Low, Standard or High). |
| Description | Optional. Shown under the name in the new task's Playbook menu, and when you hover the name in the list. |
The chain
Chain draws the stages in order. When some stages run once for each planned item, the chain groups them into Prepare, Build × N (the stages that repeat for each item) and Finish. Otherwise it's a single row.
Stage fields
The Stages tab lists the stages as cards, in order. Expand all opens every card; Collapse all closes them. The button shows only when there are two or more stages. On a playbook you can edit, Add stage below the cards adds a new stage at the end, with Asks questions set to When Full Auto is off.

Each stage is a card. Its header shows the stage number and label, then its expert, deliverable and tier, for example "Planner × Plan · High tier". Select ▸ (Expand stage) to open a card and ▾ (Collapse stage) to close it. On your organization's own playbooks, Owners and Admins also see ↑ and ↓ to move the stage, and Remove. Remove asks Remove stage? first, naming the stage. The dialog lists the stages that wait for it or are created by it, which will need fixing, or reads Nothing depends on it. Confirm with Remove. Until you save, Cancel at the bottom of the editor still undoes it. On a playbook you can only read, an open card lists each field's value as text instead of a field to change.
On a narrow card, in the pane beside the list or on a phone, Preview prompt shows as 👁 and Remove as 🗑. Hover 👁 for its name.


| Field | Meaning |
|---|---|
| Label | Required. The stage's name, shown in the chain and on the card. |
| Key | Required. A short ID other stages use to refer to this one: lowercase letters, digits and _, unique in the playbook. On a stage you add, the key follows the Label as you type it ("Review" gives review) until you type a key yourself. Other stages' Created by and Waits for follow the new key. |
| Expert | Always this expert, set in Which expert; or User selects: the person who starts the playbook picks from the Allowed experts, with a Default expert. |
| Deliverable | What the stage hands back: Pull request, Document, Mockup, Plan or Review. When Expert is User selects, it reads Follows the expert. |
| Seniority | Playbook default, Junior, Mid or Senior. |
| Created | When the playbook starts, or By an earlier Plan stage, named in Created by. |
| Runs | Once, or Once for each planned item. |
| Waits for | Nothing, Every earlier stage, or The stages chosen, ticked in Stages it waits for. |
| Asks questions | When Full Auto is off, or Never asks. |
| May file | Shown only for deliverables that can create other work, such as a Plan. Tick what the stage may create, such as The stage that runs once for each planned item and The finish stage. |
| Extra instructions | Optional text added to the stage's instructions. |
The experts are Coder, Analyst, Architect, Planner, Reviewer, UI prototyper, Researcher, Test optimizer, Repo Wizard, Translator and Marketer.
Set by the deliverable
These facts follow from the stage's expert, deliverable and seniority. You can't edit them directly.
| Fact | Meaning |
|---|---|
| Ends when | What finishes the stage, for example "Ends when its pull request merges"; a Review stage reads "Ends when its findings are uploaded". |
| Mode | Can change code, or Read-only. |
| Model tier | Low, Standard or High, from the stage's seniority. |
| Receives | The documents it gets from the stages it waits for: PRD, Architecture, both (such as PRD, Architecture on the Epic's Plan stage), or Nothing. |
| Hands off | The document it passes on: an Analyst's Document hands off a PRD, an Architect's an Architecture. Nothing for the rest. |
When Expert is User selects, the card shows Model tier and Receives once, then lists each allowed expert with its deliverable, mode, when it ends and what it hands off.
Errors and warnings
Jaah checks a playbook every time you change it. An error appears on the field it belongs to and in red on the stage card. A problem that belongs to the whole playbook appears at the top of the page. Errors stop you from saving; warnings don't.
Unsaved changes
When you edit or create a playbook, leaving it with changes you haven't saved (with Cancel, a link, the sidebar or the browser's Back) opens Unsaved changes: This playbook has changes that have not been saved. Save them before leaving?
| Button | What it does |
|---|---|
| Cancel | Closes the dialog and keeps you in the editor with your changes. |
| Discard | Leaves without your changes. |
| Save | Saves your changes, then leaves. If saving fails, you stay in the editor. |
A read-only playbook never asks, and neither does Delete.
Preview prompt
Preview prompt on each stage card opens Prompt: and the stage's label: the instructions that stage's expert would get, rendered against a sample project. Close shuts it. It shows:
- the model tier, at the top, then "Sample project";
- Expert, when the stage's Expert is User selects, to switch between the allowed experts;
- Full Auto, when the stage asks questions, to compare the prompt with Full Auto on and off;
- System and Task tabs: the expert's standing instructions, and the work it would be given.
How to use it: Preview a stage's prompt.