sprint-retro-facilitator
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.
Profile →npx skills add mohitagw15856/pm-claude-skills --skill sprint-retro-facilitator --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Sprint Retro Facilitator Retros fail two ways: they become a feelings-dump with no actions, or they generate actions no one owns and nothing changes — so next sprint has the same complaints. This grounds the retro in what actually happened (the tickets, the blockers, the metrics), pulls themes from evidence rather than the loudest voice, and produces a small number of *owned* actions — then holds last retro's actions accountable so the loop actually closes. ## What This Skill Produces - **Evidence-grounded themes** — patterns drawn from the sprint's done/WIP/blocked work and flow signals, not vibes - **Start / Stop / Continue** — concrete, tied to the themes - **2–4 action items** — each with an owner and a "how we'll know it worked" check (fewer, real ones beat a long list) - **Last retro's follow-up** — did the previous actions happen, and did they help? ## Required Inputs Ask for these if not provided: - **The sprint data** — completed vs planned, tickets that were blocked/carried over, any incidents - **Flow signals (optional)** — cycle time, throughput, WIP aging if you track them - **Team sentiment** — anything the team already raised (or run it as prompts to gather) - **La
- What This Skill Produces
- Required Inputs
- Framework: A Retro That Changes Something
- Output Format
- Retro — Sprint [n]
- Themes (from the data)
- Start / Stop / Continue
- Actions (owned)
- Quality Checks
- Anti-Patterns
- Example Trigger Phrases
What does the sprint-retro-facilitator skill do?
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.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill sprint-retro-facilitator --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.