Reviews Retros Reflection

Facilitates structured team reflection through retrospectives, post-mortems, after-action reviews, and weekly/quarterly reviews, producing root cause analysis and SMART action items with psychological safety. Use when conducting sprint retrospectives, project post-mortems, weekly reviews, quarterly reflections, after-action reviews (AARs), or when user mentions "retro", "retrospective", "what went well", "lessons learned", "reflection", or "how can we improve".

200 stars 25 forksOther Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add lyndonkl/claude

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add lyndonkl/claude --skill reviews-retros-reflection
Manual install
git clone --depth 1 https://github.com/lyndonkl/claude.git /tmp/claude
mkdir -p ~/.claude/skills
cp -r /tmp/claude/skills/reviews-retros-reflection ~/.claude/skills/reviews-retros-reflection

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Reviews, Retros & Reflection

## Table of Contents
1. [Workflow](#workflow)
2. [Retrospective Formats](#retrospective-formats)
3. [Common Patterns](#common-patterns)
4. [Guardrails](#guardrails)
5. [Quick Reference](#quick-reference)

## Workflow

Copy this checklist and track your progress:

```
Retrospective Progress:
- [ ] Step 1: Set the stage (context, psychological safety)
- [ ] Step 2: Gather data (what happened)
- [ ] Step 3: Generate insights (why it happened)
- [ ] Step 4: Decide actions (what to change)
- [ ] Step 5: Close and follow up (commit, track)
```

**Step 1: Set the stage**

Define period/scope, review previous action items, establish psychological safety (Prime Directive: "everyone did best job given knowledge/skills/resources/context"). For quick reviews → Use [resources/template.md](resources/template.md). For complex team retros → Study [resources/methodology.md](resources/methodology.md).

**Step 2: Gather data**

Collect facts about period: metrics (velocity, bugs, incidents), events (launches, blockers, decisions), sentiment (team energy, morale). See [Retrospective Formats](#retrospective-formats) for collection methods.

**Step 3: Generate insights**

Identify patterns, root causes, surprises. Ask "why?" to move from symptoms to causes. Use [resources/methodology.md](resources/methodology.md) for root cause techniques (5 Whys, fishbone diagrams, timeline analysis).

**Step 4: Decide actions**
Read the full skill on GitHub

Details

Skill name
reviews-retros-reflection
Path
skills/reviews-retros-reflection/SKILL.md
Repo updated
1 September 2026

FAQ

What does the Reviews Retros Reflection skill do?

Facilitates structured team reflection through retrospectives, post-mortems, after-action reviews, and weekly/quarterly reviews, producing root cause analysis and SMART action items with psychological safety. Use when conducting sprint retrospectives, project post-mortems, weekly reviews, quarterly reflections, after-action reviews (AARs), or when user mentions "retro", "retrospective", "what went well", "lessons learned", "reflection", or "how can we improve".

How do I install the Reviews Retros Reflection skill?

Claude Code plugin: /plugin marketplace add lyndonkl/claude. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Reviews Retros Reflection popular?

It lives in lyndonkl/claude, which has 200 GitHub stars and 25 forks.

Related skills

Abstraction Concrete Examples

200

lyndonkl/claude

Builds structured abstraction ladders that translate high-level principles into concrete, actionable examples across 3-5 levels. Bridges communication gaps, reveals hidden assumptions, and tests whether abstract ideas work in practice. Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documentation, decomposing complex problems into actionable steps, or bridging strategy-execution gaps.

Testing & QA25

Academic Letter Architect

200

lyndonkl/claude

Guides the creation of evidence-based academic recommendation letters, reference letters, and award nominations that combine concrete examples, meaningful comparisons, and genuine enthusiasm. Use when writing recommendation letters for students, postdocs, or colleagues, or when user mentions recommendation letter, reference, nomination, letter of support, endorsement, or needs help with strong advocacy and comparative statements.

Research & Science25

Adr Architecture

200

lyndonkl/claude

Documents significant architectural and technical decisions with full context, alternatives considered, trade-offs analyzed, and consequences understood. Creates a decision trail that helps teams understand why decisions were made. Use when choosing between technology options, making infrastructure decisions, establishing standards, migrating systems, or when user mentions ADR, architecture decision, technical decision record, or decision documentation.

Software Development25

Show Me Your Work

100

adriannoes/awesome-agentic-ai

Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result). Local by default; commit it when a reviewer needs the trail to trust the result. Use for /show-me-your-work, autonomous or multi-phase runs, or work a human reviews after stepping away.

OtherIn 2 lists27

Recall

100

adriannoes/awesome-agentic-ai

Reconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents), then hand back a tight current-state brief. Use for 'recall my work on X', 'catch me up', 'what have I been working on', 'where did I leave off', before starting or resuming work.

OtherIn 2 lists27

Tag By Topic

200

lyndonkl/claude

Assigns 1-4 topic tags to a seed body from the controlled vocabulary in substacker shared-context/topic-ledger.md. Prevents tag sprawl at small-corpus scale by requiring existing-tag match or logged addition. Uses keyword + title match; logs near-miss candidates to pending-tags. Use after format normalization and before dedupe. Trigger keywords — tag, topics, categorize, classify, taxonomy, controlled vocabulary, topic ledger.

Other25

Browse the most popular Claude skills, all other skills, or write your own with the skills generator.