skills.rest
cvillamarp-lgtm
cvillamarp-lgtmCOMMUNITY
Explore all skills by this author →
GitHub

post-mortems-retrospectives

Structure blameless post-mortems and retrospectives to document insights and follow-up actions.

Updated Mar 15, 2026
Search Tags:#learning#process-improvement#team-learning#blameless#retrospectives#post-mortems
One-click install
npx skills add https://github.com/cvillamarp-lgtm/skillspodcast --skill post-mortems-retrospectives-cvillamarp-lgtm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: post-mortems-retrospectives
Source: https://github.com/cvillamarp-lgtm/skillspodcast/tree/main/skills/post-mortems-retrospectives
Command: npx skills add https://github.com/cvillamarp-lgtm/skillspodcast --skill post-mortems-retrospectives-cvillamarp-lgtm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Help teams run blameless post-mortems and retrospectives to surface actionable learning after projects.

Core Features & Use Cases

  • Structured framework for conducting post-mortems and retrospectives that emphasize learning over blame.
  • Guidance to frame failures and successes, set learning objectives, and socialize insights across the organization.
  • Use cases include post-launch reviews, incident retrospectives, and quarterly retrospectives to identify blockers and opportunities for improvement.
  • Deep-dive into guest insights and best practices from leading product thinkers to continuously improve team learning loops.

Quick Start

Run a 60-minute retrospective session following the framework to surface learnings and assign follow-up actions.

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 failure?▼

Run a blameless post-mortem by following a structured framework to surface actionable learning instead of assigning fault. This approach helps teams document insights, identify blockers, and institutionalize follow-through after project failures or incidents.

What is the best way to structure team learning during a quarterly retrospective?▼

The best way to structure team learning during a quarterly retrospective is to apply frameworks from leading product thinkers. This guides you in setting learning objectives, framing outcomes, and identifying opportunities for process improvement.

Can I use this retrospective framework for successful product launches too?▼

Yes, you can use this retrospective framework for successful product launches. It applies to reviews of both successes and failures, helping teams socialize insights and institutionalize follow-through across product and engineering initiatives.

How long does a typical retrospective session take to extract learnings?▼

A typical retrospective session takes about 60 minutes to run. Following the structured framework during this timeframe allows you to surface learnings and assign follow-up actions effectively.

Does this approach require specific tools to document insights and follow-through?▼

No specific tools are required as dependencies. The framework provides guidance to structure learning sessions, document insights, and institutionalize follow-through without mandating external platforms or integrations.

Related Skills

Explore More Product & Management Skills→
blakeoxblakeox

postmortem

Reconstruct incident timelines and perform root cause analysis from logs.

Community
Advanced
yknothingyknothing
1

retrospective

Convert incident timelines and postmortem reports into owner-assigned, time-boxed improvement actions.

Community
Intermediate
Ethical-AI-SyndicateEthical-AI-Syndicate
1

retrospective-action-tracker

Track retrospective action items and detect recurring systemic patterns.

Official
Intermediate
shishishishi
3

scrum-event-sprint-retrospective

Guide teams through a five-phase Sprint Retrospective and record actions in scrum.ts.

Community
Basic