What problem does it solve? Solo developers repeatedly make the same mistakes across sessions because insights from PM feedback, errors, and discovered patterns are never systematically captured. This Skill structures how lessons learned are recorded, stored, and reapplied so knowledge persists across work sessions. ## Core Features & Use Cases - Dual Storage System: Permanent rules go into CLAUDE.md Section 11 for project-wide patterns, while session-specific learnings are appended to each session log. - Trigger-Based Recording: Activates on PM feedback, discovered errors, useful patterns, session wrap-ups, or explicit user requests like "record this lesson". - Standardized Template: Captures situation, cause, solution, and a concrete prevention rule for each lesson with a dated format. - Use Case: After a PM requests revisions because a version promotion skipped the quality checklist, record the lesson with a rule requiring checklist completion before any v0.x to v1.0 promotion, then review it at the start of future sessions. ## Quick Start Ask the assistant to record a lesson learned from the current session, including the situation, cause, solution, and a prevention rule for CLAUDE.md.