Lessons Learned

Conduct post-incident reviews to document lessons learned and implement process improvements preventing recurrence.

48 stars 10 forksOther Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sethdford/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sethdford/claude-skills --skill lessons-learned
Manual install
git 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-learned

Personal 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**:
Read the full skill on GitHub

Details

Skill name
lessons-learned
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

Browse the most popular Claude skills, all other skills, or write your own with the skills generator.