Run team retrospectives with action plans

Facilitate structured sprint retrospective with action items

Structured retrospectives when teams need to convert raw feedback into specific, executable improvements while maintaining psychological safety.

• · sprint number and date range
• · sprint goal (what was attempted)
• · team feedback (sticky notes, survey, Slack messages, or raw list)
• · velocity data (committed vs. completed points)
• · blocker list (what slowed us down)
• · previous retro action items (status: Done/In Progress/Not Started)

• · retro summary markdown with format: Sprint [X] Retrospective — [Date]
• · sprint performance: Goal (Achieved/Partial/Missed), Velocity (committed vs completed)
• · key themes (grouped feedback, sentiment analysis)
• · prioritized action items: [Action] — [Owner] — [By date]
• · carry-over status: previous actions tracked

• · Sprint data (goal, dates, velocity)
• · Team feedback collected (in some form — doesn't need to be formal)

• · More than 3 action items (won't get done)
• · Action items are vague ('improve communication' instead of 'do daily standups at 10am')
• · No owner assigned per action
• · No deadline specified (open-ended commitments)
• · Previous retro actions not tracked/revisited (retro not closing loops)
• · Sentiment patterns ignored (frustration/energy signals missed)
• · Tone is blaming instead of constructive

• · Three format options provided (Start/Stop/Continue, 4Ls, Sailboat)
• · Feedback grouping and sentiment analysis named
• · Velocity tracking (committed vs completed point comparison)
• · Action item specificity: [Action] — [Owner] — [By date] — [Success metric]
• · Carry-over tracking (previous actions reviewed)
• · 2–3 action item limit enforced (realistic commitment)
• · Constructive tone emphasis