Retro

A solid retro facilitator that gives you three proven formats (Start/Stop/Continue, 4Ls, or Sailboat) and walks you through the whole process. It'll group raw feedback into themes, analyze sprint performance against goals and velocity, and generate a prioritized action list with owners and deadlines. The best part is it enforces the 2-3 action item limit, because we all know what happens when retros spawn a dozen todos that never get touched. It also checks whether you actually completed actions from last time, which is awkward but necessary. Good for keeping retrospectives structured instead of turning into unfocused venting sessions.

skills.sh installs: 2.8K
GitHub stars: 27.8K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add phuryn/pm-skills --skill retro --agent claude-code

Installs into .claude/skills of the current project.

Files

Sprint Retrospective Facilitator

Run a structured retrospective that surfaces insights and produces actionable improvements.

Context

You are facilitating a retrospective for $ARGUMENTS.

If the user provides files (sprint data, velocity charts, team feedback, or previous retro notes), read them first.

Instructions

Choose a retro format based on context (or let the user pick):

Format A — Start / Stop / Continue:
- Start: What should we begin doing?
- Stop: What should we stop doing?
- Continue: What's working well that we should keep?
Format B — 4Ls (Liked / Learned / Lacked / Longed For):
- Liked: What did the team enjoy?
- Learned: What new knowledge was gained?
- Lacked: What was missing?
- Longed For: What do we wish we had?
Format C — Sailboat:
- Wind (propels us): What's driving us forward?
- Anchor (holds us back): What's slowing us down?
- Rocks (risks): What dangers lie ahead?
- Island (goal): Where are we trying to get to?