Lessons Learned
Conduct post-incident reviews to document lessons learned and implement process improvements preventing recurrence.
Install
/plugin marketplace add sethdford/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sethdford/claude-skills --skill lessons-learnedgit clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/security/incident-response/skills/lessons-learned ~/.claude/skills/lessons-learnedPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Lessons Learned Conduct post-incident reviews to document lessons learned and drive improvements. ## Context You are a senior incident response manager facilitating lessons-learned sessions for $ARGUMENTS. Lessons-learned sessions extract knowledge from incidents and drive improvements. Without proper review, organizations repeat the same mistakes. Effective reviews are blameless, focus on systems not people, and result in actionable improvements. ## Domain Context - **Blameless Culture**: Focus on systems/processes, not individual blame; encourages honesty and learning - **Timing**: Conduct within 1-2 weeks of incident (while details are fresh); not months later - **Participants**: Those involved in response (security, ops, management); sometimes external facilitator - **Outcomes**: Action items, process improvements, monitoring enhancements, documentation updates ## Instructions 1. **Prepare for Session**: - **Timing**: Schedule within 1-2 weeks (while memories are fresh, but after immediate recovery) - **Participants**: Incident commander, responders, business stakeholders, optionally external facilitator - **Pre-Session Materials**: Timeline of incident, logs, RCA findings, metrics (MTTD, MTTR, impact) - **Ground Rules**: Blameless; focus on learning; no recriminations; psychological safety essential - **Facilitator**: Neutral person (not directly involved) leads; ensures constructive tone 2. **Review Incident Timeline**:
Details
- Skill name
lessons-learned- Repository
- sethdford/claude-skills
- Path
security/incident-response/skills/lessons-learned/SKILL.md- License
- MIT
- Repo updated
- 11 March 2026
FAQ
What does the Lessons Learned skill do?
Conduct post-incident reviews to document lessons learned and implement process improvements preventing recurrence.
How do I install the Lessons Learned skill?
Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Lessons Learned popular?
It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.
Related skills
A B Test Design
48sethdford/claude-skills
Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
A B Test Design Pm
48sethdford/claude-skills
Analytics and experimentation skill for product managers.
Abuse Case Design
48sethdford/claude-skills
Design abuse cases (negative use cases) showing how attackers misuse system features. Use when identifying attacks that exploit intended functionality or business logic flaws.
Log Aggregation
48sethdford/claude-skills
ELK Stack, structured logging, log query patterns, and centralized log management.
Jobs to Be Done
48sethdford/claude-skills
Map user Jobs-to-Be-Done with functional, emotional, and social dimensions plus outcome expectations. Use when reframing product decisions around user motivations rather than features.
Log Analysis
48sethdford/claude-skills
Parsing logs, correlation analysis, reconstructing timeline of failures.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.