bvandeusenandClaude Opus 5.5
07e21c7ff9
CI & Build / Plugin hooks (push) Successful in 15s
CI & Build / Python lint (push) Successful in 2s
CI & Build / TypeScript typecheck (push) Successful in 54s
CI & Build / integration (push) Failing after 1m53s
CI & Build / Python tests (push) Successful in 2m39s
CI & Build / Build & push image (push) Skipped
- enter_project carries a `family` key, but only when the project has something to answer: counts of unassessed, owed and to-recheck answers, each with the list_family_adoptions call that lists it. It shows on every entry, never by platform touch: entry is when work is chosen, and an unanswered idea is otherwise invisible. - Retrieval: a widened project search (include_global_kinds) now also reaches the canon ideas on the project's platforms. It also reaches their references in the project's languages, or all of them when none matches. An off-platform project gets none, and the plain project filter (the duplicate gate) is unchanged. - Closing a task returns `family_owed`, the owed answers filed while it was open, and the report cue asks for them to be named. - New plugin skill family-canon (moment work.record) covers when to evaluate a promotion, answering in order, what counts as a reason, the precedent reflex and the conflict order. _INSTRUCTIONS, create_note, create_snippet, classify_shapes and reporting-back point at it. The plugin version is minted. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2.1 KiB
2.1 KiB
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, family-canon) 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.mdand 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
/compactand 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:syncmakes it available straight away. - If the Scribe tools are unavailable, say so rather than silently falling back to local notes.