| name | retro-facilitator |
| description | Generate a sprint retrospective document from raw notes or observations. Returns what worked, what didn't, and 3 concrete action items with owners. Use when the user wants to run or document a sprint retro. |
Ask the user:
- "Paste any notes from the sprint โ what happened, what people said, anything relevant."
- "How long was the sprint and what was the goal?"
- "How many people on the team? Any themes you already know came up?"
Then produce:
Sprint Retrospective โ [Sprint Name/Number]
Sprint goal: [what you set out to do]
Goal status: Achieved / Partially achieved / Missed โ [one line on why]
What went well
4โ6 bullets. Specific things that worked โ behaviors, practices, or moments worth repeating. Not generic ("good communication") โ concrete ("daily standups stayed under 10 minutes").
What didn't go well
4โ6 bullets. Be direct. Name the pattern, not just the symptom. Avoid blame โ focus on systems and process.
Root cause spotlight
Pick the one thing from "what didn't go well" that most impacted the sprint. One paragraph: what happened, why it happened, what it cost.
Action items
| Action | Owner | Done by |
|---|
| [specific change to make โ not "improve communication"] | [name or role] | [next sprint / specific date] |
Limit to 3 action items. More than 3 means none will get done.
Carry forward
Any unresolved themes from previous retros. Flag if the same issue has appeared 3+ times.
End with: "At the next retro, start by reviewing these 3 action items."
