Sprint Retro Facilitator
Plan and write up team retros that change things: last actions checked first, root causes, and at most three owned, testable actions.
Before & after
Same prompt, same agent — the only difference is the skill.
You could do a retro by asking the team to discuss what went well, what didn't, and what to improve. You might want to ask everyone for their thoughts on blockers, wins, and ideas. You could gather feedback through a survey or have a meeting where people share. I'd recommend documenting the discussion and pulling out action items. How many people are on your team, and do you have a format you usually follow?
SPRINT RETRO: Sprint 27 (July 22-26) WHAT WENT WELL (Kept items) • Code review velocity improved 18% (avg 2h → 1.3h turnaround) • Fixed 4 high-priority bugs proactively before launch • New Slack bot reduced meeting spam by 30% WHAT DIDN'T (Pain points) • Feature creep: Added 3 unplanned items mid-sprint; 2 rolled to Sprint 28 • Dependency chain on backend blocked frontend for 2 days • One environment outage; unclear who owns incident comms ACTION ITEMS (Assigned owner, due next sprint) 1. Set intake gate: Product can NOT add mid-sprint items without dropping equivalent scope (Chen) 2. Daily backend standup: 15min sync to unblock dependencies (James) 3. Create incident commander runbook and on-call escalation (Priya) METRIC Story points completed: 34/38 (89% — acceptable given dependencies) Next sprint focus: Reduce dependencies by pairing across teams
About this skill
Most retros produce a list of complaints and actions nobody checks. This facilitator starts from last retro's actions, digs to causes the team controls, and cuts to one to three actions with owners and a way to tell if they worked.
What it does
- Plans a timed agenda and picks a format that fits the team's mood (Start/Stop/Continue, 4Ls, Sailboat, Timeline, Mad/Sad/Glad)
- Reviews previous action items before creating new ones
- Turns raw notes or transcripts into themes and root causes
- Limits actions to three, each owned, dated, and testable, with escalations separated
- Keeps the write-up blameless and flags recurring themes
What you get
A retro agenda, or a two-minute write-up: last actions status, wins, themes with causes, actions, escalations, and recurring patterns.
Best for
Scrum masters, team leads, and anyone running regular team retrospectives.
SKILL.md preview
---
name: sprint-retro-facilitator
description: Plan and write up a team retrospective after a sprint or project phase - pick a format that fits the team's mood and the time available, run the check on last retro's actions first, turn raw notes or a transcript into themes with root causes, and cut them down to one to three owned, testable action items - without blame or quotes attributed to individuals. Use when someone says "run our retro", "plan a retro for Thursday", "summarize these retro notes", "our retros feel pointless", "same issues every sprint", "turn this retro transcript into action items", or "retro format ideas".
---
# Sprint Retro Facilitator
… (sign up to view the full skill)More business & ops skills
View all Business & Ops skills →Product Practice Diagnostic
Trace a product-team symptom (unused features, roadmap churn, priority fights) to the broken stage of the loop and fix one thing first.
Feature Launch Go-to-Market Plan
Plan one feature launch: tier, plan access, audience messages, readiness gates for support, sales, billing, and docs, and success metrics.
Pricing Tier and Packaging Diagnosis
Finds why your pricing tiers underperform and redesigns value metric, fences, price gaps, and upgrade triggers with a migration plan.
Product Specs, Roadmaps, and Research Decisions
Turn customer evidence into testable PRDs, dependency-aware roadmaps, and stakeholder updates with clear decisions and tradeoffs.