Menu

Individual skill

sprint-retro-facilitator

Structures and facilitates sprint retrospectives with a timeboxed agenda, format selection, anti-blame ground rules, and owned action items that actually close. Use when someone asks "help me run our retro", "our retros produce the same actions every sprint", "what format should this retrospective use", or "how do I get the team to say what they're really thinking". Do NOT use for incident postmortems with a timeline and root-cause analysis - use postmortem-writer instead. For diagnosing chronic team dysfunction beyond one sprint, use team-health-check; for planning the next sprint's scope, use sprint-planning.

skills/sprint-retro-facilitator/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 6, 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)
24
Repository last updated
Oct 13, 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

# Sprint Retro Facilitator

Most retros produce the same three actions every sprint and close none of them, which teaches the team that speaking up changes nothing - the most expensive lesson a team can learn. This skill forces specificity, surfaces the issues people are actually thinking, and ends with someone's name on every action.

## Inputs to collect

Before the session, gather:

1. Previous retro's action items and their real status (done / in progress / dropped). Non-negotiable - see Step 1.
2. Sprint facts: what shipped, what slipped, any incidents. Facts anchor discussion away from vibes.
3. Team mood signal, if you have one (a one-question pulse, or your own read). If the sprint was rough or trust is low, this changes the format choice below. Label your read as a guess if it is one.
4. Session length. Default 60 minutes maximum; 45 is better. Below 30, cut the discussion topics to one, not the timeboxes.

## Choose the format