Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | 23% | 0% |
| case-02 | ✗→✓ | ▲ Improved | 68% | 0% |
| case-03 | ✗→✓ | ▲ Improved | -5% | 0% |
| case-08 | ✗→✓ | ▲ Improved | 24% | 0% |
| case-11 | ✗→✓ | ▲ Improved | 61% | 0% |
Run a structured retrospective that surfaces insights and produces actionable improvements.
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.
Format A — Start / Stop / Continue:
Format B — 4Ls (Liked / Learned / Lacked / Longed For):
Format C — Sailboat:
| Priority | Action Item | Owner | Deadline | Success Metric | |---|---|---|---|---| | 1 | Specific, actionable improvement] | Name/Role] | Date] | How we'll know it worked] |
## Sprint X] Retrospective — Date]
### Sprint Performance
### Key Themes
### Action Items
### Carry-over from Last Retro
Save as markdown. Keep the tone constructive — the goal is improvement, not blame.
Other measured skills in the registry, with their headline benchmark lift.