# Sprint Retrospective Facilitation

> Sprint Retrospective Facilitation

- Skill: `sairam0424/sprint-retrospective-facilitation` (Agent Skill)
- Install (CLI): `npx skillmds@latest add sairam0424/sprint-retrospective-facilitation`
- Raw SKILL.md: https://api.skillmd.com/api/skills/sairam0424/sprint-retrospective-facilitation/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: sairam0424 (https://skillmd.com/u/sairam0424)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/sairam0424/sprint-retrospective-facilitation

---


# Sprint Retrospective Facilitation

## When this skill activates

This skill activates when planning, facilitating, or improving sprint retrospectives.
It provides multiple retrospective formats, facilitation techniques for psychological
safety, action item design principles, and pattern detection across retros to drive
continuous team improvement.

## Mandatory actions when this skill is active

### Before

1. **Select format based on team state** — Rotate formats to prevent staleness. Choose
   based on what the team needs right now (celebration, problem-solving, future-focus).
2. **Prepare the space** — Set up the board/template, send pre-retro prompts if using
   async input, confirm time-box with team.
3. **Review previous retro actions** — Check completion status of last retro's action
   items. This is the first agenda item every time.

### During

4. **Retrospective formats (rotate these):**

   - **4Ls (Liked / Learned / Lacked / Longed-for):**
     Balanced format covering positives and gaps. Good default.
     Liked = what went well; Learned = new insights; Lacked = what was missing;
     Longed-for = wishes for the future.

   - **Sailboat:**
     Visual metaphor. Wind = forces helping us; Anchor = forces slowing us;
     Rocks = risks ahead; Island = our goal/destination.
     Good for teams needing to name risks they have been avoiding.

   - **Timeline:**
     Map sprint events chronologically, then discuss emotions/energy at each point.
     Good for sprints with many events or high drama.
     Reveals patterns in when energy drops or rises.

   - **Start / Stop / Continue:**
     Simple and direct. Start = new practices to try; Stop = practices hurting us;
     Continue = practices working well. Good for action-oriented teams.

   - **Mad / Sad / Glad:**
     Emotion-focused. Good for teams that need to process feelings before solutions.
     Validates that emotions are legitimate data.

5. **Facilitation principles:**
   - **Psychological safety first** — Explicitly state: "This is a blame-free zone.
     We are examining the system, not judging individuals."
   - **Equal voice** — Use silent writing before discussion. Prevents loud voices from
     dominating. Everyone contributes before anyone speaks.
   - **Time-box per section** — Strict timekeeping. Brainstorm (10 min), group/vote
     (5 min), discuss top items (25 min), actions (10 min).
   - **Dot-voting** — Each person gets 3 votes. Discuss only the top-voted items.
     This prevents discussing everything superficially.
   - **Facilitator does not contribute** — The facilitator manages process, not content.
     If the facilitator has opinions, they participate as a team member and delegate
     facilitation.

6. **Action item design (SMART):**
   - **Specific** — "Add integration test for payment flow" not "improve testing"
   - **Measurable** — Clear definition of done
   - **Assigned** — One owner (not "the team")
   - **Realistic** — Achievable within next sprint
   - **Time-boxed** — Due date before next retro
   - Maximum 3 action items per retro (more = none get done)

7. **Pattern detection across retros:**
   - Track themes that recur across multiple retros.
   - If the same issue appears 3+ times, it is systemic — escalate to leadership or
     dedicate a sprint to fixing it.
   - Maintain a "retro theme tracker" showing issue frequency over time.
   - Celebrate patterns that disappear (proof that retros drive improvement).

8. **Team health signals to monitor:**
   - Participation level (are people engaged or checked out?)
   - Action item completion rate (are retros driving change?)
   - Theme recurrence (are the same problems persisting?)
   - Energy/morale trend (is the team trajectory improving?)
   - Psychological safety indicators (are people raising hard topics?)

### After

9. **Publish retro summary** — Share action items and key themes with the team within
   24 hours. Keep it brief.
10. **Track action items** — Add to sprint backlog or team board. Review completion at
    next retro opening.
11. **Rotate facilitator** — Different person each sprint builds shared ownership of
    team improvement.
12. **Evolve the process** — If retros feel stale, try a new format. If attendance
    drops, investigate why. The retro itself should improve over time.

## Self-check before task completion

- [ ] Previous retro action items reviewed for completion status
- [ ] Format selected intentionally (not just defaulting to the same one)
- [ ] Psychological safety explicitly established at the start
- [ ] Equal voice mechanisms used (silent writing, voting)
- [ ] Discussion time-boxed with strict facilitation
- [ ] Maximum 3 SMART action items generated
- [ ] Each action item has a single owner and due date
- [ ] Recurring themes identified and tracked
- [ ] Summary published within 24 hours