What do I need to use Sprint Retro Facilitator?

The sprint data; Flow signals (optional) (optional); Team sentiment; Last retro's actions.

Is Sprint Retro Facilitator free to use?

Yes — run it free in the browser playground (no API key needed for the sponsored trial, or bring any provider key), or install it into Claude Code, Cursor, ChatGPT and more via npx pm-claude-skills. MIT-licensed and open source.

Sprint Retro Facilitator

Q: How do I know the Sprint Retro Facilitator output is good?

The skill verifies itself against its own quality checks: Themes cite actual sprint evidence (tickets/metrics), not just opinions; Systemic patterns are distinguished from one-offs; Actions are 2–4, each with a named owner and a success check; Last retro's actions are reviewed before new ones are set.

🔵 Stable🕐 updated 2026-08-04 🔷 SkillSpec L3 pm-delivery

Run a sprint retrospective that produces real change — themes from what actually happened, honest start/stop/continue, and owned action items, not a vent session. Use when asked to facilitate a retro, run a sprint retrospective, prep retro themes, or turn our sprint into a retro. Produces the data-grounded themes (from done/WIP/blocked work and any flow metrics), a start/stop/continue, 2–4 owned action items with checks, and a follow-up on last retro's actions so retros stop repeating themselves.

▶ Run it free — no key needed 📝 Grade your existing draft View SKILL.md ↗

🗣 Say this to your agent

“Facilitate our sprint retro from these tickets and metrics.”“Run a retrospective — here's what got done and what got blocked.”“Prep retro themes and a start/stop/continue for sprint 14.”“Help me run a retro that actually leads to change.”

What to give it

▸The sprint data — completed vs planned, tickets that were blocked/carried over, any incidents

▸Flow signals (optional) (optional) — cycle time, throughput, WIP aging if you track them

▸Team sentiment — anything the team already raised (or run it as prompts to gather)

▸Last retro's actions — so we can check them (a retro that ignores its own history repeats it)

✅ The bar it holds itself to

Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.

✓Themes cite actual sprint evidence (tickets/metrics), not just opinions

✓Systemic patterns are distinguished from one-offs

✓Actions are 2–4, each with a named owner and a success check

✓Last retro's actions are reviewed before new ones are set

✓Framing is blameless — system and process, not individuals

⚠️ What it refuses to do

**A vent session** with no actions — cathartic, useless.

**Nine action items** with no owners — nothing changes.

**Ignoring last retro** — guarantees the same issues recur.

**Blame** — turns the retro into something people stop being honest in.

**Themes from the loudest voice** instead of the data.

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp

Start with

Related skills

🔌 Embed this skill

Drop this on your blog, docs, or site — it renders a "Run this skill" card:

<div data-pm-skill="sprint-retro-facilitator"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

Sprint Retro Facilitator is one of 1078 open-source professional AI agent skills — all SkillSpec L3. Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog