bvandeusenandClaude Opus 5.5
c5eeec471f
CI & Build / Python lint (push) Successful in 3s
CI & Build / Plugin hooks (push) Successful in 14s
CI & Build / TypeScript typecheck (push) Successful in 53s
CI & Build / integration (push) Successful in 1m2s
CI & Build / Python tests (push) Failing after 1m26s
CI & Build / Build & push image (push) Skipped
Step 3 of the Scribe -> Grimoire rename. - Plugin `grimoire` in marketplace `grimoire-plugin`, MCP server key `grimoire`, so tools reach a session as mcp__plugin_grimoire_grimoire__*. - hooks/scribe_* -> hooks/grimoire_*, their shell functions and the TMPDIR ledgers with them; SCRIBE_URL / SCRIBE_TOKEN / SCRIBE_HOOK_DIR / SCRIBE_LEDGER_DIRS -> GRIMOIRE_*; the project marker is `.grimoire`. - skills/using-scribe -> using-grimoire, /grimoire:sync, stored processes arrive as grimoire-proc-<slug>; moment_actions names them the same way. - Migration 0124 rewrites stored skill names (rule_moments, rule_moment_judgments, moment_mappings) from scribe:/scribe-proc- to grimoire:/grimoire-proc-, so a rule mounted on a skill keeps firing. - Settings' install commands and MCP-only defaults, the docs and the tests follow. - scripts/check_plugin.py drops the smoke event for a report-check hook that has no file in plugin/hooks. Kept on purpose: the secret-sealing label, and the names that let backups written as Scribe restore and be counted. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
36 lines
2.1 KiB
Markdown
36 lines
2.1 KiB
Markdown
# Grimoire — Claude Code adapter
|
|
|
|
This session is connected to **Grimoire**, the operator's system of record for
|
|
their work, through the `grimoire` MCP tools. How to work with Grimoire is stated
|
|
once, in the **`using-grimoire`** skill: reach for it at the start of the session
|
|
and whenever you are unsure what Grimoire 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 Grimoire, 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 Grimoire instead, and using-grimoire says how
|
|
Grimoire works alongside them.
|
|
- **Lines injected beside your work are retrieval.** When the operator sends a
|
|
message, and before a write or a command, Grimoire 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-grimoire 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 Grimoire, 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-grimoire, "Hand off").
|
|
- **Stored Processes arrive as skills** (`grimoire-proc-*`), refreshed at session
|
|
start. After a Process is added or edited, `/grimoire:sync` makes it available
|
|
straight away.
|
|
- **If the Grimoire tools are unavailable, say so** rather than silently falling
|
|
back to local notes.
|