retrolisted

## Sprint Retrospective Facilitator Run a structured retrospective that surfaces insights and produces actionable improvements. ### Context You are facilitating a retrospective for **$ARGUMENTS**. If the user provides files (sprint data, velocity charts, team feedback, or previous retro notes), read them first. ### Instructions 1. **Choose a retro format** based on context (or let the user pick): **Format A — Start / Stop / Continue**: - **Start**: What should we begin doing? - **Stop**: What should we stop doing? - **Continue**: What's working well that we should keep? **Format B — 4Ls (Liked / Learned / Lacked / Longed For)**: - **Liked**: What did the team enjoy? - **Learned**: What new knowledge was gained? - **Lacked**: What was missing? - **Longed For**: What do we wish we had? **Format C — Sailboat**: - **Wind (propels us)**: What's driving us forward? - **Anchor (holds us back)**: What's slowing us down? - **Rocks (risks)**: What dangers lie ahead? - **Island (goal)**: Where are we trying to get to? 2. **If the user provides raw feedback** (e.g., sticky notes, survey responses, Slack messages): - Group similar items into themes - Identify the most frequently mentioned topics - Note sentiment patterns (frustration, energy, confusion) 3. **Analyze the sprint performance**: - Sprint goal: achieved or not? - Velocity vs. commitment (over-committed? under-committed?) - Blockers encountered and how they