菜单
The live note-taker — summarize the current session's decisions and open threads on demand or at checkpoints, and (in a bureau workspace) append them to the session's running minute. Use when running bureau:note, or when the user asks to take a note / minute this / summarize where we are.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | scribe |
| description | The live note-taker — summarize the current session's decisions and open threads on demand or at checkpoints, and (in a bureau workspace) append them to the session's running minute. Use when running bureau:note, or when the user asks to take a note / minute this / summarize where we are. |
| argument-hint | [--workspace <name>] |
file-session files the minutes after a session; the scribe writes them during it, so the
record's fidelity doesn't depend on end-of-session memory. It is the minute-taker; the filed
minute is its notes cleaned up.
file-session later finalizes it).On demand (bureau:note, or the user asking) or at natural checkpoints — a decision made,
a direction changed, a milestone reached. Not after every turn: constant summaries bury the
signal. Capture inflection points, not heartbeats.
bureau.json; default bureau). If none, produce the summary for
the user and stop (ephemeral mode) — do not error.logbook/<YYYY>/<MM>/<safe-session-id>.md, the same file file-session finalizes), under a
timestamped checkpoint heading. Never rewrite earlier notes or other sessions' entries.status: logbook — raw material, never canon. The
scribe never writes dossiers.file-session consolidates them.This skill covers ONLY live note-taking into the logbook (or an ephemeral summary). It does
not finalize the entry (file-session), not distil to cabinets (compile), and not
read the canon to answer questions (recall / bureau:query). It is invoked by bureau:note
and by the SessionStart (post-compaction) hook's re-grounding flow.
Orientation for the bureau plugin — the records-office model, the capture → compile → review gate, the trust tiers, the crew, and which bureau: command serves which intent. Read this FIRST before using any bureau: command, or whenever working in a repo that has a bureau workspace (a canon/ directory + a BUREAU.md), so you draw on the project's canon instead of re-deriving or guessing.
Write a faithful, append-only minute for an AI session — intent, decisions, changed files, open threads, and a transcript pointer. Use when filing a session into a bureau workspace (e.g. via bureau:file-session), or when the user asks to record/minute the current session.
Distil minutes into consistency-checked dossiers — the canonical SSOT — writing provenance links back to the sessions that introduced each claim. Use when running bureau:compile, or when the user asks to turn the logbook into canon / update the cabinets / build the knowledge base from sessions.
Sweep the dossiers for semantic inconsistencies that the press's structural check cannot see — free-text contradictions, superseded claims, undocumented gaps, and vocabulary drift. Use when running bureau:lint, before a milestone, or when the user asks to check the canon for contradictions / consistency / drift.
Answer from the bureau canon with citations and trust tiers — read dossiers as memory, honor each page's status, and never present an unverified claim as fact. Use when running bureau:query, or when the user asks what the project knows / what was decided / what the canon says about something.
The human double-check gate for AI-written memory. Show every cabinet claim not yet approved — with its provenance and automatic check result — and let the human promote it to canonical or reject it. Use when running bureau:review, or when the user asks to approve / vet / sign off on what the AI wrote to memory before it is trusted as fact.