Audit Transcripts for Learnings

Retrospective audit of past Claude Code sessions. Extracts reusable patterns from transcripts in a chosen scope and date window, then walks the user through each one inline — promote to active config, reject, refine, or skip — in a single conversation.

When to use

• After a sprint, project phase, or month of work — to surface what changed about how you work that should be encoded.
• When the user says "audit my transcripts", "what should I be capturing", "review my last N weeks", or similar.
• When repeated corrections or workflows feel familiar and worth formalising.

When NOT to use

• For analysing skill usage (which skills you do/don't invoke) — that is a separate audit.
• For deep code review or planning — wrong tool.

Protocol

1 — Always ask scope