engram-digestlisted
Install: claude install-skill techtheist/engram
# Engram digest — ingest an existing project
Digestion turns a codebase that predates its memory graph into a first graph. It is **explicit and opt-in**: it runs only when the user asks, never automatically. One digestion is a bounded pass, audibly reported at the end — the opposite of the engram skill's silent trickle capture.
**The target is the current working tree** — the code and docs that exist *now* on this branch. Git history is supporting material only (the *why* behind what you see), never a deep crawl of old commits. And Engram is **reasoning memory, not a code map**: digest the decisions, constraints, and gotchas the code embodies — not its structure, which the code itself already records. Quality over coverage; a good first digest is dozens of well-linked nodes, not hundreds of thin ones.
## Procedure
**0. Preflight.** The `engram` MCP tools must be available (if not, the repo isn't wired — run `engram-alpha setup`, or the plugin's `/engram:setup`, and stop). Agree the scope with the user if they gave one ("just the backend"); default is the whole tree. **A near-empty tree** (fresh scaffold, no docs, no real code) **has nothing to digest — say so and stop**; never pad a graph to have something to show. Choose the ingest session id now: `digest-<YYYY-MM-DD>` — **every write in this pass carries it** (see Session marking).
**1. Recall first.** Call `brief` (or read the injected one). If the graph already has nodes, digestion tops up: `search` each area before