← ClaudeAtlas

learnlisted

Run a session retrospective — extract lessons from what happened and persist them where they'll be found next time (CLAUDE.md, MEMORY.md, handoff.xml, skills). Invoke proactively after painful debug sessions, unexpected breakthroughs, end of significant work, or when a pattern recurs across sessions. Apply Kaizen — small improvements, compounded.
TomasLicek/ai · ★ 1 · AI & Automation · score 78
Install: claude install-skill TomasLicek/ai
# Learn — Session Retrospective Kaizen: small improvements, compounded. Reflect on what happened, extract lessons, persist them where they'll matter. ## When to Use - End of a work session - After a painful debugging session or unexpected breakthrough - When something felt off but you can't name it - When a pattern keeps recurring across sessions ## Core Workflow 1. **Reflect on the session** - What actually happened? (not what was planned — what happened) - What worked well? What was surprisingly effective? - What was painful, slow, or wrong? - What mistakes were made? Root cause, not symptoms. - Any "aha" moments worth preserving? 2. **Extract actionable lessons** - For each insight, ask: where should this live so it's useful next time? - Categories: - **Project** — CLAUDE.md update, new doc, better conventions - **Workflow** — skill improvement, new skill idea, better tool usage - **Self** — memory update (what Claude should remember), pattern to watch for - **User** — suggestion for Tom (habit, tool, approach) 3. **Persist the learnings** - Update `MEMORY.md` or topic-specific memory files with durable insights - Propose CLAUDE.md changes if project conventions need updating - Update `handoff.xml` if there's open work for next session - Suggest skill updates if a skill was clunky or missing - **Don't just report findings — actually write them down where they'll be found** 4. **Report** - Brief summary of k