Skip to main content
skill CX Codex

reviews-retros-reflection — Claude Code skill: setup and use

reviews-retros-reflection structures retrospectives, incident post-mortems, and periodic check-ins. Helps teams identify root causes and turn feedback into SMART action items without blame.

no license 113 installs ★ 203 updated 2026-09-01

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add lyndonkl/claude --skill reviews-retros-reflection -a claude-code
Open on GitHub

What reviews-retros-reflection does

The skill walks teams through a five-step retrospective: setting stage context, gathering metrics and events, uncovering root causes, agreeing on fixes, and tracking follow-through. It uses techniques like the 5 Whys and timeline analysis to examine broken processes rather than targeting individual contributors.

Several workshop models are provided depending on available time and team needs. A thirty-minute Start/Stop/Continue session suits routine sprint reviews, while Mad/Sad/Glad helps unpack difficult emotional periods. For quarterly milestones or complex project shutdowns, the methodology suggests the 4Ls framework or the visual Sailboat exercise.

Piling up more than five action items guarantees none will get done. Because of this, the workflow insists on capping follow-ups at three SMART tasks and aiming for an eighty percent completion rate before the next retro. Final meeting quality is verified against resources/evaluators/rubric_reviews_retros_reflection.json with a minimum required score of 3.5.

What it helps with

  • facilitate a sprint retrospective using the Start/Stop/Continue model
  • conduct a blameless post-mortem using timeline and 5 Whys analysis
  • turn retro discussions into one to three assigned SMART actions
  • lead an end-of-project debrief with the 4Ls framework

Example prompts for the agent

  • Help me facilitate a 45-minute sprint retrospective using Mad/Sad/Glad.
  • Let's analyze yesterday's production outage and trace root causes with 5 Whys.
  • Structure our quarterly reflection using the 4Ls approach.

How to install reviews-retros-reflection

1Skills CLI (Vercel)

npx skills add lyndonkl/claude --skill reviews-retros-reflection -a claude-code

2Manually: put the files in place

~/.claude/skills/reviews-retros-reflection/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/reviews-retros-reflection/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about reviews-retros-reflection

How do I install reviews-retros-reflection in Claude Code?

Run npx skills add lyndonkl/claude --skill reviews-retros-reflection -a claude-code. The file installs locally to ~/.claude/skills/reviews-retros-reflection/SKILL.md.

What is reviews-retros-reflection used for?

It guides engineering teams through sprint retrospectives, post-mortems, and recurring reviews. The skill keeps discussions structured around root cause analysis while maintaining psychological safety.

How many action items should a retro produce?

The skill enforces a limit of one to three SMART actions with explicit owners. Tracking requires completing over 80% of these tasks before the next review session.

Similar skills

All skills for Notes, tasks and projects →

From the same set49

The whole set →
constraint-based-creativity constraint-based-creativity — a skill that makes the model invent inside tight limits, such as a small budget or a fixed format, so brainstorming stops circling the same answers. CX Codex +1 115installs translation-reframing-audience-shift translation-reframing-audience-shift rewrites content for a different audience: technical docs to business cases, strategy to action steps, expert text to plain language. CX Codex +1 115installs meta-prompt-engineering The meta-prompt-engineering skill turns unclear prompts into structured instructions with a defined role, task steps, constraints, and quality checks. Use it when an agent’s responses vary between runs. CX Codex +1 114installs systems-thinking-leverage systems-thinking-leverage turns a tangled problem into a mapped system with ranked intervention points, built on feedback loops and Meadows' leverage ladder. CX Codex +1 114installs causal-inference-root-cause causal-inference-root-cause — a skill that pushes an agent through a five-step causal investigation, so the answer to why something happened comes with a mechanism and a tested alternative. CX Codex +1 110installs security-threat-model security-threat-model guides threat modeling across system components using STRIDE methodology, trust boundary maps, and defense-in-depth principles before audits or releases. CX Codex +1 109installs discovery-interviews-surveys discovery-interviews-surveys is a Claude Code skill for planning user interviews and surveys to test product assumptions and uncover customer problems, before building or when exploring why people switch products. CX Codex +1 109installs project-risk-register project-risk-register — a skill for identifying, assessing, and prioritizing project risks using probability-impact scoring. Assigns owners and mitigation plans, then tracks risk evolution throughout the project lifecycle. CX Codex +1 108installs

Project sponsors

Companies that keep this analytics open