Playbooks

Playbooks hold your organization’s protocols and procedures: how the work is done. Where skills define what correct performance looks like, Playbook pages teach people how to get there, for example your discrete-trial teaching procedure, your prompt hierarchy, or how to write a session note. You find them under Playbooks in the side menu.

Skills and Playbook pages are linked many-to-many. A skill can point to several pages, and the same page can be referenced by several skills, since one procedure often supports more than one task:

flowchart LR
  subgraph Skills
    S1["Implement discrete-trial teaching"]
    S2["Implement prompting and prompt fading"]
    S3["Write session notes"]
  end
  subgraph Playbook pages
    P1["DTT procedure"]
    P2["Prompt hierarchy"]
    P3["Session note guidelines"]
  end
  S1 --> P1
  S1 --> P2
  S2 --> P2
  S3 --> P3

Pages and organization

Playbooks are made of pages arranged in a hierarchy of parents and children. Organize them the way your staff look for guidance: by program type, by clinic, or by stage of a session.

Each page can be Published, kept as a Draft while you work on it, or Archived when it’s no longer current. Only published pages appear in search.

Writing pages

Pages are written in a rich editor: select text for a floating formatting bar, or type / for a block menu. You can link a page from a skill’s description so the procedure sits right next to the skill it teaches.

Tip

You don’t have to write every page by hand. Connect an AI tool over MCP and have it draft pages for you, for example from the protocols and training documents you already have, so existing material becomes Playbook pages in a few prompts.

Supported formatting

Pages are Markdown underneath, with the same vocabulary as every editor in Behaview: headings, lists and checklists, quotes, tables, callouts, syntax-highlighted code, images, Mermaid diagrams, [[ links to other Playbook pages, and @ mentions. Supported Formatting covers the lot.

Access restriction

By default a page is visible to everyone who can open Playbooks. You can restrict a page by role so some guidance stays with the right people, such as a page for BCBAs only. Access cascades: restricting a parent page restricts its children too. If someone can see a child page but not its parent, the parent still appears as a placeholder so the structure stays coherent.

Search

Full-text search runs across your published pages, so people find a procedure by what it’s about rather than where it lives; draft and archived pages are excluded. Often the most direct route is from the work itself: a skill links straight to the page that teaches it.