compoundlisted

Harvest what this session learned so future sessions inherit it. Only knowledge that compounds gets written; every write is approved by the user first. ## 1. Scan the session Sweep the whole session for candidates: corrections the user made and preferences they stated, conventions that emerged, gotchas and root causes uncovered, approaches that failed and why, domain terms coined or clarified ("we call this X, not Y"), and workflow friction a procedure could remove. ## 2. Apply the quality bar For each candidate, two questions: would this change a future agent's behavior in a different session, and is it non-obvious and stable? Any "no" → discard. This bar is the defence against the eager-auto-memory failure mode: session-specific trivia — in-flight task state, one-off values, things any agent would infer anyway — must die here. If nothing clears the bar, say so in one line and stop. ## 3. Route each survivor 1. **Project `AGENTS.md`** — durable _shared_ preferences and conventions, cheap enough to always load. Domain terms go in its glossary section; when the glossary outgrows `AGENTS.md`, propose graduating it to a `CONCEPTS.md` file. 2. **`docs/solutions/`** — problem-shaped learnings: root cause, gotcha, what didn't work. One small file per solved problem, per [`solutions-format.md`](solutions-format.md). Expensive knowledge, loaded on demand. 3. **Project-local rules** — path-scoped project conventions, when the project uses rules files. 4. **Skills** —