consolidate-knowledgelisted

Use when a body of captured journal entries from many sessions should be distilled into durable, higher-level guidance — cluster related entries, synthesize the one generalization each cluster supports, promote only the reinforced and specific ones into long-lived guidance, and reconcile supersession when newer evidence overrides older. Triggers on "consolidate my journals", "what patterns emerged across these sessions", "distill these notes into guidance", "what have we learned over time", "promote the durable insights", "synthesize my entries into wisdom", or running "/consolidate-knowledge". This is the downstream pass that journaling-sessions feeds — journaling captures raw entries one session at a time, this consolidates many of them across sessions. Not for capturing a single session (use journaling-sessions), not for a one-off summary, and distinct from consolidating your agent memory files.
grimaldost/craft-collection · ★ 2 · AI & Automation · score 71

Install: claude install-skill grimaldost/craft-collection

# Consolidate Knowledge Distill a corpus of raw journal entries into **durable, higher-level guidance** — the pass that turns many specific captures into a few reinforced generalizations. `journaling-sessions` produces the raw input (one idea per entry, reasoning inline, anti-patterns hunted); this clusters those entries and promotes the patterns that have earned it. The bar is not "summarize the journals" but: *a future session, retrieving this cold, gets a generalization it can act on that no single entry stated — and that the base model would not have volunteered.* ## The pipeline — run in order 1. **Gather** the entries in scope — by area, by date range, or the whole corpus. Read them; do not work from titles. By default the entries are the journal files `journaling-sessions` writes under `docs/journal/` (or a store's `target_store` `path` when one is set). Also read the **prior promoted guidance** first — the durable layer this pass appends to, by default `docs/journal/guidance.md` (a store's configured guidance path wins when one is set) — so what already exists is known before anything new is synthesized. Record the scope as an explicit **Inputs** line — entry count, sessions, date range — the same way `feedback-triage` records the reports a triage covers. 2. **Reconcile already-promoted first.** A generalization this corpus supports may already be in the durable layer from an earlier consolidation. Open the output with an **"Already pr