Playbooks

Playbooks are your organization’s knowledge base, a wiki for how the work is done. Where skills define what good looks like, playbooks teach people how to get there. If you’ve used a wiki, playbooks will feel familiar, so this page focuses on the few things worth knowing.

Skills and playbooks are linked many-to-many. A skill can point to several playbook pages, and the same page can be referenced by multiple skills, since doing one thing well often draws on more than one skill:

flowchart LR
  subgraph Skills
    S1["Run a standup"]
    S2["Coach a teammate"]
    S3["Plan a sprint"]
  end
  subgraph Playbook pages
    P1["Facilitation basics"]
    P2["Kanban board hygiene"]
    P3["Giving feedback"]
  end
  S1 --> P1
  S1 --> P2
  S2 --> P1
  S2 --> P3
  S3 --> P2

Pages and organization

Playbooks are made of pages arranged in a hierarchy of parents and children. Organize by topic, team, or process, whatever matches how people look for guidance.

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 “how” sits right next to the “what.”

[!TIP] Writing pages doesn’t have to feel manual. Connect an AI tool over MCP and have it draft pages for you, especially by pulling from the other sources your AI is already connected to, so existing knowledge becomes a playbook in a few prompts.

Supported formatting

Content is Markdown under the hood, so the usual syntax works. The key pieces:

• Headings, bold/italic, lists, quotes, and links: standard Markdown.
• Internal links: type [[ to search for and insert a link to another playbook page.
• Images: paste or drag them straight into the page.
• Code blocks: fenced blocks, with syntax highlighting.
• Callouts: GitHub-style alerts, e.g. > [!NOTE] or > [!TIP].
• Mermaid diagrams: a fenced code block tagged mermaid renders as a diagram. See the Mermaid syntax docs for the full set of diagram types and syntax. For example, this:

```mermaid
flowchart LR
  Draft --> Review --> Published
```

renders as:

flowchart LR
  Draft --> Review --> Published

Access restriction

By default a page is visible to everyone in your organization. You can restrict a page by role so sensitive guidance stays with the right people. 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 guidance 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.