What problem does it solve?
Teams often run retrospectives that surface observations but fail to convert them into a small set of clear, owned, and measurable improvements. This Skill structures the retro process, clarifies themes from raw feedback, analyzes sprint performance, and produces a concise markdown summary with prioritized action items and owners so improvements actually get executed.
Core Features & Use Cases
- Structured Facilitation: Guides context confirmation, selects a retro format (Start/Stop/Continue, 4Ls, Sailboat), and focuses the discussion on root causes and improvements.
- Feedback Synthesis: Groups sticky-note style feedback, identifies frequent themes and sentiment patterns, and links findings to sprint metrics and blockers.
- Outcome Delivery: Produces a ready-to-share markdown retro report including sprint goal status, key themes, and 2-3 specific, assignable action items with owners, deadlines, and success metrics.
- Use Case: Run this when finishing a sprint to convert team feedback and velocity data into a prioritized list of improvements to track in the next iteration.
Quick Start
Run a retrospective for the last sprint using the attached feedback and velocity chart to produce a markdown summary with 2-3 prioritized action items, owners, and dates.