retro-analysis

# Retrospective Analysis Skill Generate a data-grounded retrospective brief that separates facts from feelings, so the team spends retro time on solutions rather than debating what happened. ## Required Inputs Ask the user for these if not provided: - **Sprint tickets: planned vs. completed** - **Carry-over tickets and reasons** (if known) - **Tickets reopened after closing** (quality signal) - **Any incidents or unplanned work** (scope creep signal) - **Sprint velocity vs. historical average** (trend context) ## Process 1. Calculate: completion rate, carry-over rate, unplanned work percentage 2. Identify patterns: which ticket types were most likely to carry over? Which caused blockers? 3. Note any process or communication breakdowns visible in the data 4. Prepare 3 "Start / Stop / Continue" prompts based on the data — not generic, specific to this sprint 5. Suggest 1 concrete experiment for the next sprint based on the biggest friction point 6. **Validate** — Confirm each prompt is specific to this sprint (not a recycled generic prompt), and that the recommended experiment is concrete and measurable ## Output Structure ### Sprint [Number] Retrospective Brief **By the Numbers:** - Planned: [n] tickets | Completed: [n] | Carry-over: [n] | Completion rate: [%] - Unplanned work: [n] tickets ([%] of capacity) - Velocity: [points] vs. [average] average **What the Data Suggests:** [2-3 observations grounded in the numbers above] **Discussion Prompts:** - Start: [specific ...