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.

Pages and organization

Playbooks are made of pages arranged in a hierarchy of parents and children, with breadcrumbs so readers always know where they are. 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.”

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. 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.