Run data-grounded sprint retros
retro-analysisskillsetup L1★327
mohitagw15856/pm-claude-skills ↗What it does
Generate sprint retrospectives grounded in data patterns
Best for
Teams that need to stop debating what happened in retros and focus on solutions grounded in sprint data.
Inputs
- · Sprint tickets (planned vs. completed)
- · Carry-over tickets with reasons
- · Reopened tickets count
- · Unplanned work incidents
- · Sprint velocity vs. historical average
Outputs
- · Sprint retrospective brief with metrics
- · 3 data-specific Start/Stop/Continue prompts
- · 1 concrete, measurable experiment for next sprint
Preconditions
- · Ticket tracking system with completion and carry-over data
- · Access to sprint velocity baseline
Failure modes
- · Prompts become generic if not rooted in this sprint's data
- · Experiment is too vague to measure in one sprint
- · Does not identify which ticket types cause blockers
Trust signals
- · Explicit validation step checking prompts are sprint-specific, not recycled
- · Carry-over analysis tied to ticket type and root cause
- · Experiment is testable with a specific success metric
- · Data observations explicitly separated from blame