Generate a structured retrospective focused on learning and actionable improvements.
Quick Reference
- Input: Sprint data (goal, completed/not completed), team feedback, metrics.
- Output: Retrospective document with action items.
- Sections: What Went Well, What Didn't, Action Items, Metrics, Kudos.
- Rule: Every "what didn't" needs an action item with an owner.
HARD-GATE
DO NOT fabricate feedback — only include input the team actually provided.
DO NOT skip action items — every "what didn't" must have at least one action.
DO assign an owner and timeline to every action item.
Core Process
- Gather — sprint data (goal met? completed/not completed tickets), team feedback, relevant metrics.
- Categorize:
- What Went Well — wins, effective practices, things to continue.
- What Didn't — blockers, bottlenecks, process issues, surprises.
- Kudos — shout-outs and recognition.
- Identify themes — group related feedback into themes rather than listing raw comments.
- Draft action items — specific, owned, time-bound. Use the template in RETROSPECTIVE_TEMPLATE.md if available; otherwise use the minimal template below.
- Review — verify every "what didn't" maps to an action item.
Output Style
Use RETROSPECTIVE_TEMPLATE.md when bundled.
Section order: header → What Went Well → What Didn't → Action Items → Metrics → Kudos. Use English unless the user requests otherwise. Every "what didn't" maps to an action item with Owner, Timeline, and Linked Issue.
Integration
| Skill | When to chain |
|---|---|
| plan-sprint | Review the sprint plan vs what was actually delivered |
| generate-status-report | Include retrospective insights in the next status report |
work-router with project-manager intent |
Focus the retrospective on delivery follow-through; it does not select a separate persona |