retro

retro is a product-management skill that facilitates a structured sprint retrospective. It solves the problem of running retros that meander or produce no follow-through by guiding a facilitator through surfacing what went well, what did not, and a short list of prioritized, owned, and dated action items. If the user provides sprint data, velocity charts, team feedback, or previous retro notes, the skill reads them first to ground the session.

The skill offers three retrospective formats to fit the context: Start/Stop/Continue, the 4Ls (Liked/Learned/Lacked/Longed For), and Sailboat (Wind/Anchor/Rocks/Island). It can take raw feedback such as sticky notes, survey responses, or Slack messages and group similar items into themes, identify frequently mentioned topics, and note sentiment patterns. It then analyzes sprint performance (goal achievement, velocity versus commitment, blockers, and collaboration patterns) and generates a small set of two to three prioritized action items in a table with owner, deadline, and success metric. Finally it produces a markdown retro summary that captures sprint performance, key themes, action items, and carry-over status from the previous retro. The guidance deliberately caps action items so they actually get done and keeps the tone constructive rather than blame-oriented.

Target users are product managers, scrum masters, engineering leads, and agile teams who want a repeatable, structured retrospective. It is entirely a documentation and facilitation aid that outputs markdown, with no code execution or external integrations.