Playbooks

A playbook is a reusable method: when it applies, what information it needs, the steps to follow, the moments that need approval, and what counts as done. The agent reads the playbook before it starts and follows it. Playbooks are how a firm’s methodology, templates and sign-off rules become the default way the agent works.

Built-in playbooks

superglue ships with four playbooks that cover the common workstreams:

Playbook	When it applies
Start a project	Set up a client project from connected email or from your description
Migrate data	Plan or carry out a migration, define mappings and transformations, validate the result
Build an integration	Build tools that read, write, or move data, one-off or recurring
Create an MCP server	Expose selected tools to an MCP client such as Claude or Langdock

They appear on the session start screen. Select one, or describe the task and let the agent match it. Built-in playbooks are read-only. To adapt one, ask the agent to copy it into a new playbook and change the copy.

Write your own

Select New playbook under Brain › Playbooks and describe the method to the agent, or ask the agent to draft one from a completed engagement: “Turn the way we ran the Contoso vendor migration into a playbook for GP to Intacct migrations.”

A playbook has these parts:

• Name: a recognizable workstream, such as “GP to Intacct: vendor and AP migration”.
• Scope: when the playbook applies. The agent matches requests against it. Name the systems, the action or the recurrence.
• Prerequisites: what must be in place before work starts, such as system access, source files and client decisions. The agent checks the project’s files first and asks you for whatever is still missing in one message.
• Phases: the steps of the method in order, each with a title and its activities, owners and outputs.
• Deliverables: what the work produces, such as a field mapping, a reconciliation report or a cutover runbook.
• Sign-off: who approves the result and what they check, for example “The client approves the reconciliation report before cutover.” The agent stops at each sign-off.

Preview shows the playbook as a formatted method page in your organization’s design system. Source edits each section as plain text. Download saves it as PDF or Word in the same branding, or as Markdown, so you can hand it to a colleague or a client.

Name the tools, connections and Brain files a phase uses in that phase, and say when the agent should read each file. Naming them gives context and does not restrict the agent from other permitted resources.

i

Keep decisions, completion checks and approval requirements in the playbook text. Put long reference material in Brain files. The agent reads the playbook in full before every run, so a focused playbook is followed more reliably than a long one.

Improve playbooks from real work

After a run, ask the agent what it would change. When a session revealed a reusable correction, such as a code translation the target always needs, the agent proposes adding it. Corrections that apply to one client stay in that project; corrections that apply to the method go into the playbook.

The playbook editor has an agent sidebar. Ask it to tighten wording, add an approval step, or reconcile the playbook with a newer template.

Share playbooks with the team

Playbooks are organization resources and follow the same access rules as tools and connections. Give every consultant Viewer access to the firm’s playbooks, and Editor access to the people who own the methodology. See Role-based access control.