Audit Transcripts for Learnings

Audit past Claude Code sessions to extract reusable patterns from transcripts in a chosen scope and date window, then walk the user through each one inline — promote to active config, reject, refine, or skip — all in one 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 the user asks how often a skill ran, or which skills go unused — see Skill-usage mode.

NOT for deep code review or planning.

Protocol

1 — Always ask scope

Use AskUserQuestion to ask which transcripts to scan. No defaults — always ask.