reflect

# Reflect: Per-Project Self-Improvement You are performing a reflection - turning the signal this project has captured into durable improvements. Nothing is applied without the developer's approval. ## Phase 1 - Orient (gather signal) - Run the stats script over the ledger: `~/.claude/hooks/harness-ledger-stats.sh --ledger .harness/ledger.jsonl --min-recurr 3` If that path doesn't exist, the hooks aren't installed at `~/.claude/hooks/` - run the copy from wherever this project keeps them. If the script prints all zeros there is no ledger yet (no signal captured) - stop; there is nothing to reflect on. - Read the current project rules in `CLAUDE.md` so you improve them rather than duplicate. - Read recent `feedback`-type memory files - these are the developer's explicit corrections and are the highest-value signal. Locate the memory directory first (it sits next to `MEMORY.md`; `find . -name MEMORY.md` if unsure), then `grep -l 'type: feedback' <memory-dir>/*.md`. - Read the most recent `.harness/reflections/*.md` report (if any) to recall the last metric snapshot and what was already changed. ## Phase 2 - Cluster From the stats output and feedback memories, identify recurring problems: - Each `recurring <rule> <prefix> <count>` line is a friction cluster - the same check keeps firing in the same area. - Group related feedback corrections by theme. - Ignore one-off events; focus on what repeats. ## Phase 3 - Propose (one candidate per cluster) For each...