Playbooks
A playbook is a prompt fragment + a list of tool names. Think of it as a self-contained capability: “I know how to book appointments, and to do that I need these three tools available.”Why bundle tools and prompt?
Because the prompt and the tool list have to agree. A “book an appointment” prompt is useless if thebook_appointment tool isn’t
available. Wrapping them together as a playbook prevents the
“prompt mentions a tool that doesn’t exist” bug and makes capabilities
composable.
Built-in vs custom
Same model as tools:is_default = true for shipped playbooks,
custom ones can be created, updated, and deleted.

