post-mortems-retrospectives

Structure blameless post-mortems and retrospectives into actionable follow-up actions.

1.2k|156|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/RefoundAI/lenny-skills --skill post-mortems-retrospectives-refoundai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: post-mortems-retrospectives
Source: https://github.com/RefoundAI/lenny-skills/tree/main/skills/post-mortems-retrospectives
Command: npx skills add https://github.com/RefoundAI/lenny-skills --skill post-mortems-retrospectives-refoundai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Helps teams run effective post-mortems and retrospectives to extract actionable learnings after projects succeed or fail, improving how the organization learns and adapts.

Core Features & Use Cases

  • Structured post-mortems and retrospectives guided by established frameworks to surface lessons.
  • Emphasis on blameless, psychological-safety–driven reflection that socializes learnings across teams.
  • Mechanisms to translate insights into concrete actions, influencing future projects and processes.

Quick Start

Kick off a blameless session with key stakeholders, capture top learnings, and assign concrete follow-up actions to improve future projects.

Frequently Asked Questions about post-mortems-retrospectives

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

FAQPage Schema
How do I run a blameless post-mortem after a project fails?

A blameless post-mortem focuses on process improvement and systemic issues rather than individual faults. You structure the retrospective with key stakeholders to extract actionable insights, enforce psychological safety, and assign concrete follow-through actions to prevent future failures.

What is a blameless retrospective and how does it drive team learning?

A blameless retrospective is a structured team reflection that enforces psychological safety to socialize learnings across teams. It drives organizational learning by translating project outcomes into actionable insights and concrete actions that influence future projects and processes.

How do I turn retrospective insights into concrete process improvements?

To turn retrospective insights into process improvements, you enforce blameless framing to surface lessons, then use follow-through mechanisms to translate those insights into concrete actions assigned to stakeholders, ensuring learnings are applied to future projects.

Can I use this for routine project checkpoints, or only after failures?

You can use this for routine project checkpoints, successes, and failures. The structured retrospectives adapt to various project outcomes, ensuring organizational learning and process improvement happen continuously, not just during post-mortem analysis after a failure.

What's the best way to ensure psychological safety during a post-mortem?

The best way to ensure psychological safety during a post-mortem is to use established frameworks that enforce blameless framing. This structured approach guides stakeholders to focus on systemic learning and process improvement rather than assigning individual blame.