reviews-retros-reflection

Facilitate structured retrospective sessions using formats like Start/Stop/Continue and 5 Whys.

142|20|Updated Oct 22, 2025
One-click install
npx skills add https://github.com/lyndonkl/claude --skill reviews-retros-reflection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviews-retros-reflection
Source: https://github.com/lyndonkl/claude/tree/main/skills/reviews-retros-reflection
Command: npx skills add https://github.com/lyndonkl/claude --skill reviews-retros-reflection

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps teams and individuals systematically learn from past experiences, identify areas for improvement, and foster a culture of continuous growth.

Core Features & Use Cases

  • Structured Reflection: Facilitates retrospectives, post-mortems, and reviews using various proven formats (Start/Stop/Continue, 4Ls, etc.).
  • Actionable Insights: Guides users through root cause analysis to move beyond symptoms to actionable solutions.
  • Use Case: After a challenging project sprint, use this Skill to conduct a retrospective, identify what went well, what could be improved, and define concrete action items for the next sprint to prevent recurring issues.

Quick Start

Use the reviews-retros-reflection skill to conduct a sprint retrospective using the Start/Stop/Continue format.

Frequently Asked Questions about reviews-retros-reflection

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

FAQPage Schema
How do I conduct a sprint retrospective to identify lessons learned?

Conduct a sprint retrospective by using structured formats like Start/Stop/Continue or 4Ls to guide team reflection. This process helps identify what went well, what to improve, and generates actionable insights for continuous improvement.

What is the best way to run a root cause analysis during a post-mortem?

Run a root cause analysis during a post-mortem by applying techniques like 5 Whys and timeline analysis. These methods move your team beyond surface-level symptoms to uncover actionable solutions and prevent recurring issues.

When should I use Mad/Sad/Glad versus 4Ls for team reflection?

Use Mad/Sad/Glad for team reflection when focusing on emotional dynamics, and use 4Ls when categorizing lessons into Liked, Learned, Lacked, and Longed for. Both formats drive continuous improvement through structured feedback.

Can I track progress on action items generated from a retrospective?

Yes, you can track progress on action items generated from a retrospective. The structured reflection process is designed to define concrete action items and monitor them to ensure continuous growth across future sprints.

Does this retrospective format work for individual reflection as well as team sessions?

Yes, this retrospective format works for individual reflection as well as team sessions. It facilitates structured learning for both individuals and teams to identify areas for improvement and foster a culture of continuous growth.