Playbooks
The way-of-working instructions attached to a flow: how your best person would do the task.
A playbook is the instruction injected before a model sees a request. It's where judgment lives: the difference between a model that answers a prompt and a model that does a task the way your company actually wants it done.
Playbooks are reusable across flows. "Reviewer" is used by any flow where something needs checking without being approved outright. "Writer" is used anywhere the output needs to sound like your company, not like a generic assistant.
A good playbook has a boundary
The most useful line in most playbooks is what the task should never do on its own: "never promise refunds or timelines," "do not approve or merge," "do not modify files." Capable models do more than asked if nothing tells them where to stop.
Reviewer
Review for correctness, tests, and risk. Leave specific,
actionable comments. Do not approve or merge. Report
judgment calls.Playbooks never appear to the person running the flow. They only shape the output. See the Writing a good playbook guide in Resources for a worked walkthrough.