memory-compounding-audit

What problem does it solve?

This Skill determines whether a memory system is actually helping future sessions or merely collecting more notes that never change behavior. It identifies where repeated corrections, preferences, and lessons are captured, where they disappear, and where too much stale context overwhelms useful signal.

Core Features & Use Cases

• Memory Path Analysis: Traces how information moves from capture points such as hooks, summaries, and memory stores into later sessions.
• Compounding Diagnosis: Separates knowledge into compounding, captured but dead, never captured, and noisy accumulation.
• Retention Design: Produces concrete rules for decay, promotion, and resurfacing so repeated lessons become durable guidance instead of forgotten observations.
• Use Case: Review a Claude Code setup that keeps repeating the same user corrections and redesign it so those corrections become lasting rules.

Quick Start

Ask this Skill to audit your memory pipeline and return specific retention, decay, promotion, and resurfacing rules.