memory-audit

# Memory audit — the surgical one-file pass This is the **cap-trip response**, not the daily ritual. `/memory-kit:close-session` runs every session and captures; this runs when the hot cache has actually outgrown itself and something must LEAVE it. Keeping them separate is the point: a daily ritual that also has to do surgery becomes a ritual people skip. **Always pause for approval before writing.** The user talks; you write — including here. ## Inputs - `.claude/memory/MEMORY.md` — read in full. - `knowledge/concepts/*.md` — filenames + first 5 lines, for duplicate detection (the directory may not exist yet; the first move creates it). - `context/handoffs/` — to confirm a session narrative already lives there → **drop**, not move. ## Step 1 — classify every section Scan by `## ` heading. For each, count lines and mark exactly one action: | Mark | When | |---|---| | `move (create)` | a settled pattern (confirmed on 3+ distinct dates) with >25 lines of reference detail | | `move (merge)` | same, but a concept article on the topic already exists | | `drop` | a per-session chronicle — it already lives in a handoff; distil at most one settled line | | `update in-place` | stale: names a deleted file, a closed ticket, a superseded decision | | `simplify` | true and useful, but three times longer than it needs to be | | `keep` | earns its lines | ## Step 2 — the move plan (a table, never prose) | # | Section | Lines | Action | Target | Reason | |---|---|---|---|---|---| ...