Chief of Staff Get started

In your folder: brain/playbooks/explore.md

Rendered from release 0.24.0, the version the download installs. This page is generated from the shipped file and says exactly what your copy says.

Playbook: Explore (connect the dots)

Turns Chief of Staff's Anticipate mandate (brain/role/charter.md, brain/role/principles.md) into a workflow: mine memory/ for relationships the principal hasn't connected yet, and surface the ones worth acting on. Runs on /explore or when the principal asks "what am I missing / connect the dots". Distinct from memory-lint.md (which checks memory is correct) — explore looks for insight.

Ground everything in stored memory. Never invent a connection — if the link isn't supported by what's actually written, don't claim it.

Scope

Explore all of memory/ by default; if $ARGUMENTS names a person, project, or theme, center the exploration there. Start from memory/index.md, then read the pages.

Find the connections

Scan for entities or topics that appear across multiple files but aren't directly linked, e.g.:

  • A person who recurs in several projects but has no stated role in one of them.
  • Two projects that share an owner, a dependency, a deadline, or a risk — but neither page mentions the other.
  • A decision (decisions.md) or commitment (commitments.md) that bears on a project or person not cross-referenced.
  • A stated preference or sensitivity that's relevant to an upcoming meeting or open decision.
  • A risk or blocker in one place that threatens a goal recorded elsewhere.

Produce

Deliver in this turn — bottom line first (brain/role/voice.md): the single most useful connection, then a short ranked list. For each connection:

  1. The link — the two (or more) things and how they connect, citing the memory files.
  2. The insight — why it might matter (a risk to flag, a person to loop in, a dependency to sequence, a question to ask).
  3. What would confirm it — the fact or source that would validate the hunch (and whether it's already in memory or a gap to fill).

Pick the few most interesting connections, not every pair — signal over volume. If nothing non-obvious surfaces, say so honestly.

After

  • Offer to act on confirmed connections: add cross-reference links between the related pages (standard markdown links, per brain/schemas/memory-file.md), create a new page if a theme deserves one, or turn an insight into a commitment/decision to track. Apply only on the principal's OK, and update memory/index.md for anything you add.
  • If a connection reveals a gap (something worth knowing but not recorded), flag it and suggest what would fill it (a note to capture, a question to answer).
  • Ledger. Append one explore line to memory/ledger.md — the run and the connection(s) surfaced (brain/schemas/capture-rules.md → "Action ledger").