Back to Skills
Operations

Sprint Retro Facilitator

Structures sprint retrospectives with prompts, synthesis, and action items

/sprint-retro-facilitator

Time Saved

1 hr → 10 min

Compared to doing it manually

Slash Command

/sprint-retro-facilitator

Type this in Claude to run the skill

The Problem

Retros become repetitive complaint sessions or get skipped entirely. Action items from last retro? Nobody remembers. The same issues come up sprint after sprint.

What You Get

  • ✓Structured retro notes
  • ✓Categorized feedback (good/bad/change)
  • ✓Patterns across retros identified
  • ✓3-5 concrete action items with owners
  • ✓Follow-up on previous retro items

How to use this skill

  1. 1Start your free trial — all 70 skills are included
  2. 2Set up your company context with /welcome
  3. 3Type /sprint-retro-facilitator in Claude to run the skill

Best For

Sprint endingsProject post-mortemsTeam health checksProcess improvement

Related Skills

Customer Success Playbook

/customer-success-playbook

Create CS playbooks with plays for onboarding, adoption, renewal, and expansion.

Incident Post-Mortem

/incident-post-mortem

Writes a blameless incident post-mortem with root cause analysis

Process Documentation

/process-documentation

Documents team processes with quick reference checklists and detailed steps

Team Health Check

/team-health-check

Run structured team health checks to surface what is working and what is not.

Frequently Asked Questions

Use a structured format (Start/Stop/Continue, 4Ls, etc.). Ensure everyone speaks. Focus on actionable improvements, not venting. Limit to 3-5 action items and assign owners.

45-60 minutes for a 2-week sprint. Shorter sprints = shorter retros. If you're going over, you're probably discussing too many topics. Prioritize and park the rest.

Start free trial