bvandeusenandClaude Opus 5.5
a72a422534
CI & Build / Python lint (push) Successful in 13s
CI & Build / Plugin hooks (push) Successful in 16s
CI & Build / TypeScript typecheck (push) Successful in 56s
CI & Build / integration (push) Successful in 1m38s
CI & Build / Python tests (push) Failing after 1m59s
CI & Build / Build & push image (push) Skipped
Until now only the tool arguments knew moments existed. The guidance surfaces described rules as reached by resemblance alone: - using-scribe: a short reflex paragraph and a new reference file, moments.md. It covers reading "at <moment>, reached by <action>", the reply held once at reply.report, map_action / unmap_action offered in one line, and the step 7 proposal line answered with judge_rule_moments. - writing-records: asks WHEN a rule applies as well as what it is about. A rule, preference or process about a point in the work gets moments=[...] as it is written, and the trigger stays as the net. - missed-retrieval: a missed WHEN is mounted or mapped, not reworded. A misfire is unmounted or unmapped. - _INSTRUCTIONS: one clause (list_moments; mount rules about WHEN), 1594 of 1600 chars. - static context: injected lines include the rules mounted on a moment that was reached. - test_guidance_ownership: three owned topics, so the text cannot quietly drop out. Plugin minted. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
36 lines
2.0 KiB
Markdown
36 lines
2.0 KiB
Markdown
# Scribe — Claude Code adapter
|
|
|
|
This session is connected to **Scribe**, the operator's system of record for
|
|
their work, through the `scribe` MCP tools. How to work with Scribe is stated
|
|
once, in the **`using-scribe`** skill: reach for it at the start of the session
|
|
and whenever you are unsure what Scribe expects. Each tool's contract is in its
|
|
description, and the process skills (writing-plans, reporting-back,
|
|
reusing-code, systematic-debugging, verification, brainstorming,
|
|
shape-accounting) carry their arcs.
|
|
|
|
What only Claude Code needs said:
|
|
|
|
- **Keep one copy — in Scribe, not Claude Code's local memory.** Claude
|
|
Code's local memory is `CLAUDE.md` and auto-memory: the operator's rules,
|
|
plans and project notes go to Scribe instead, and using-scribe says how
|
|
Scribe works alongside them.
|
|
- **Lines injected beside your work are retrieval.** When the operator sends a
|
|
message, and before a write or a command, Scribe may add rules, preferences,
|
|
notes and prior art that resemble what you are doing — and, when a tool call
|
|
or the reply ending a turn reaches a moment of work, the rules mounted on
|
|
it. Open the ones that apply; using-scribe says what a quiet turn means and
|
|
how to correct a moment that fired wrongly.
|
|
- **Compact at clean seams.** Because work is recorded as you go, a compaction
|
|
is safe once in-flight state is logged. After finishing a block of work in a
|
|
long session, log it to Scribe, then tell the operator it's a good moment to
|
|
`/compact` and name what you logged. You can't run it yourself; suggest it at
|
|
seams, not every turn.
|
|
- **When the operator wraps up, hand off first.** Log where each task you
|
|
worked stands before the session ends; the plugin releases your claims at
|
|
session end, but only you can say what happened (using-scribe, "Hand off").
|
|
- **Stored Processes arrive as skills** (`scribe-proc-*`), refreshed at session
|
|
start. After a Process is added or edited, `/scribe:sync` makes it available
|
|
straight away.
|
|
- **If the Scribe tools are unavailable, say so** rather than silently falling
|
|
back to local notes.
|