Menu

Individual skill

retro-facilitator

Structures raw sprint retro notes into themes and concrete actions. Use after a retro when raw sticky-note-style input (what went well/poorly/to try) needs to become a clean summary with follow-through.

skills/productivity/retro-facilitator/SKILL.md

Read pinned source

Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
27
Repository last updated
Aug 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Purpose

Turn raw retro input (a scattered list of what went well, what didn't, and ideas to try) into a structured summary with clustered themes and concrete, ownable action items — so retros produce follow-through instead of just catharsis.

## When to Use

- After a sprint/iteration retro, with raw notes (sticky notes, a shared doc, verbal notes) that need structuring.
- A team's retros tend to surface the same complaints repeatedly with no visible action — worth using this to force clustering and concrete actions.

## What to Analyze / Do

1. **Cluster related raw items into themes** — several individually-worded complaints about "too many meetings," "context switching," "no focus time" likely cluster into one theme (interruption/focus-time issues), not three separate items.
2. **Separate went-well from went-poorly from ideas-to-try** clearly.
3. **Convert the most significant themes into concrete action items** — not every theme needs an action (some are just useful signal), but recurring or high-impact ones should get one.