Agent skill

post-mortems-retrospectives

Help users run effective post-mortems and retrospectives. Use when someone is reviewing a project that succeeded or failed, wants to establish learning practices, is dealing with failure aftermath, or needs to improve team learning loops.

majiayu000534★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill post-mortems-retrospectives-refoundai-lenny-skills-2 --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/analysis/post-mortems-retrospectives-refoundai-lenny-skills-2/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Post-mortems & Retrospectives Help the user run effective post-mortems and retrospectives that drive genuine learning using frameworks from 11 product leaders. ## How to Help When the user asks for help with post-mortems or retrospectives: 1. **Understand the context** - Ask whether this is after a failure, a success, or a routine checkpoint 2. **Set the right tone** - Help them frame the exercise as learning-focused rather than blame-focused 3. **Structure for insights** - Guide them toward formats that surface actionable learnings 4. **Ensure follow-through** - Help them create mechanisms to act on what they learn ## Core Principles ### Pre-mortems need kill criteria Annie Duke: "A pre-mortem is only effective if it results in 'kill criteria' - pre-determined signals that will trigger a pivot or shutdown." Identify early signals that a project is failing during the pre-mortem and pre-commit to specific actions if those signals are met. ### Reframe failure as growth Carole Robin: "The acronym is A-F-O-G, another F-ing... Another Fucking Opportunity for Growth. My question, when something has gone wrong or a person has experienced a failure, my first question is always, so what d

What's inside
Steps it walks through
  1. How to Help
  2. Core Principles
  3. Pre-mortems need kill criteria
  4. Reframe failure as growth
  5. Call them retrospectives, not post-mortems
  6. Institutionalize learning reviews
  7. Grade OKRs for learning, not performance
  8. Make it blameless
  9. Questions to Help Users
  10. Common Mistakes to Flag
  11. Deep Dive
  12. Related Skills
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the post-mortems-retrospectives skill do?

Help users run effective post-mortems and retrospectives. Use when someone is reviewing a project that succeeded or failed, wants to establish learning practices, is dealing with failure aftermath, or needs to improve team learning loops.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill post-mortems-retrospectives-refoundai-lenny-skills-2 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going