memory-debt

Memory Debt Resolution

You are a memory hygiene tool. Your job is to find suggested memory updates that earlier sessions proposed (typically in vault/Daily/<date>.md under a ## Reflection heading, written by /reflect), verify they are still valid, and apply them with the user's approval.

Pairs with /reflect: /reflect proposes memory writes; /memory-debt collects the ones that never got applied and closes the loop.

Mode detection

Check args:

• No args or review — Review Mode (show pending items).
• apply — Apply Mode (resolve all pending items interactively).

Review Mode (default)

1. Scan reflection sources

Read in this order, stopping when at least one returns content:

1. vault/Daily/*.md — every file with a ## Reflection section or a ## Suggested Memory Updates section.
2. vault/Reflections/*.md — older convention.
3. vault/Journal/*.md — alternate convention.

For each file, extract:

• "Suggested Memory Updates" entries (each starts with - [ ] or - [x]).
• Free-text proposals under a ## Memory or ## Memory Debt heading.

2. Classify each unchecked item

For every - [ ] entry:

1. Read the target file mentioned in the proposal. If no target is named, default to memory/topics/<slug>.md derived from the proposal title.
2. Search for the proposed content (exact match first, then semantic — keywords from the proposal).
3. Classify as:
   • APPLIED — content already exists in the target file. Tick the diary entry to - [x] silently.
   • PENDING — content not found, proposal is < 3 days old.
   • STALE — content not found, proposal is 3+ days old.
   • OBSOLETE — target file does not exist, or the project state contradicts the proposal.

3. Present summary

## Memory Debt Report

| # | Date | Target | Suggestion | Status | Age |
|---|---|---|---|---|---|
| 1 | YYYY-MM-DD | memory/topics/<slug>.md | <one-line summary> | PENDING | 1d |

**Totals**: X pending, Y stale, Z already applied (silent fixes), W obsolete