source-command-distill-sessions

name	source-command-distill-sessions
description	L5 — analyze recent sessions and propose refinements to AGENTS.md (writes a proposal, applies nothing).

source-command-distill-sessions

Use this skill when the user asks to run the migrated source command distill-sessions.

Command Template

🧬 Distill sessions (propose)

Analyze the recent session history and propose improvements to AGENTS.md — but apply nothing. This is the review step; /distill-apply materializes it.

1. Get a compact digest of the last N sessions instead of reading the raw logs [ADR-0027]: node contextkit/tools/scripts/session-digest.mjs --last N (N from contextkit/config.json → l5.distill.observeWindow, default 10), newest first. Reason over the digests; open a full file in contextkit/memory/sessions/ only when a digest flags a pattern you must inspect verbatim.
2. Look for recurring signals: corrections the user gave repeatedly, rules re-explained across sessions, conventions that emerged but aren't written down, friction that a AGENTS.md rule would prevent, and decisions that should be promoted to an ADR.
3. Promotion gate (≥3 occurrences) [ADR-0065]: only propose a pattern as a new AGENTS.md rule once it has 3+ evidenced occurrences across the digests. Below that threshold, record it as an observation in the proposal (a candidate to watch), not a rule — a one-off correction is noise, not a standard. Cite the occurrences that clear the bar.
4. Draft a concrete diff to AGENTS.md (and note any ADRs worth creating). Prefer small, high-signal additions over bloat — AGENTS.md must stay short.
5. Write the proposal to .distillation-proposal.md (gitignored) with: the evidence (which sessions, what pattern, occurrence count), the proposed AGENTS.md edits as a clear before/after, a separate Observations list for sub-threshold patterns, and any suggested ADRs.
6. Summarize to the user and tell them to review it, then run /distill-apply to commit the change. Do not edit AGENTS.md in this command.