solo-lessons-learned

Records project lessons, patterns, and prevention rules into CLAUDE.md and session logs.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/cjrain-12505614/solo-forge-marketplace --skill solo-lessons-learned-cjrain-12505614
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: solo-lessons-learned
Source: https://github.com/cjrain-12505614/solo-forge-marketplace/tree/main/solo-forge-v0.6.0/skills/solo-lessons-learned
Command: npx skills add https://github.com/cjrain-12505614/solo-forge-marketplace --skill solo-lessons-learned-cjrain-12505614

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about solo-lessons-learned

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I record lessons learned in a Claude Code project?▼

Invoke the skill with a request like "record this lesson" and provide the situation, cause, solution, and prevention rule. Permanent project-wide rules are written to CLAUDE.md Section 11, while session-specific learnings go into the session log.

When should lessons learned be captured during development?▼

Capture lessons after PM feedback requests revisions, when you discover an error in your work, when you find an efficient pattern, at session end, or whenever explicitly requested. Recording immediately prevents losing context about why the issue occurred.

What is the difference between permanent and session lesson records?▼

Permanent records in CLAUDE.md Section 11 cover project-wide patterns, repeatable error-prevention rules, and process standards. Session records hold context-specific tips valid only for that work session and are later reviewed for possible promotion.

How are recorded lessons applied in future sessions?▼

At the start of each session, read CLAUDE.md Section 11 to review accumulated rules, identify which apply to the current task, and follow them to avoid repeating past mistakes.

What format should a lesson learned entry follow?▼

Each entry uses a dated heading with four fields: situation describing what happened, cause explaining why, solution describing the fix, and a bolded rule stating the concrete prevention or reuse guideline.