bvandeusenandClaude Opus 5.5
952e56ee75
CI & Build / Python lint (push) Successful in 3s
CI & Build / Plugin hooks (push) Successful in 12s
CI & Build / TypeScript typecheck (push) Successful in 52s
CI & Build / integration (push) Successful in 59s
CI & Build / Python tests (push) Successful in 1m40s
CI & Build / Build & push image (push) Successful in 24s
Release is the mechanical half: scribe_session_end.sh sends the ending
session's id to /api/plugin/release-session, which releases the claims it
held. A tidy-up, not the guarantee (no SessionEnd on a crash; the lease
covers that), and skipped on /clear so SessionStart(clear) can still
hand the claimed work back.
Saying what happened is the half only the model can do. It is stated as a
practice where it is read: the using-scribe skill owns it ("Hand off before
this session's context stops existing", pinned in test_guidance_ownership),
the static context points at it for the wrap-up moment, and add_task_log's
docstring says a log claims the task. _INSTRUCTIONS is untouched.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
34 lines
1.9 KiB
Markdown
34 lines
1.9 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. Open the ones that
|
|
apply; using-scribe says what a quiet turn means.
|
|
- **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.
|