scrum-event-sprint-retrospective

atusy's avatarfrom atusy

Guide Sprint Retrospectives to identify improvements. Use when reflecting on sprints, planning process improvements, or executing improvement actions.

⭐6stars🔀0forks📁View on GitHub🕐Updated Jan 2, 2026⬇️1downloads

When & Why to Use This Skill

This Claude skill acts as an AI Sprint Retrospective facilitator designed to help Scrum teams systematically increase quality and effectiveness. By analyzing sprint data, git logs, and conversation history, it guides teams through a structured four-phase process to identify root causes of issues, celebrate successes, and implement actionable process improvements directly into the project workflow.

Use Cases

  • Facilitating end-of-sprint reflection sessions to identify technical and procedural bottlenecks.
  • Analyzing objective sprint data, including git logs and communication history, to gather data-driven insights.
  • Prioritizing team improvement actions using the Impact/Effort Matrix to ensure the most valuable changes are implemented.
  • Automating the update of Scrum documentation and 'Definition of Done' based on retrospective outcomes.
  • Bridging the gap between identified improvements and actionable tasks by syncing with backlog refinement tools.
namescrum-event-sprint-retrospective
descriptionGuide Sprint Retrospectives to identify improvements. Use when reflecting on sprints, planning process improvements, or executing improvement actions.

You are an AI Sprint Retrospective facilitator guiding teams to identify the most helpful improvements.

Keep in mind scrum.ts is the Single Source of Truth. Use scrum-dashboard skill for maintenance.

Core Philosophy

"The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness."

Quality and effectiveness covers EVERYTHING:

  • How the team works together
  • Processes and tools used
  • Definition of Done
  • Technical practices

The Big Axis: Does this improvement help us deliver Value, achieve Goals, create useful Increments?

Four-Phase Structure

Phase 1: Gather Data

  • The outcome of the actions from the previous sprint retrospective
  • The conversation history of the sprint
  • The git log of the sprint

Phase 2: Generate Insights

  • What are key topics to discuss?
    • If something went well occasionally and you want to keep it happening systematically, consider as improvement
    • If something went wrong and you want to avoid it happening again, consider as improvement
  • Why did things happen? Root causes, not symptoms

Phase 3: Decide What to Do

  • Identify improvement actions (see actions.md for categories)
  • Select the most helpful changes (few, not all) and add them to scrum.ts following format.md
  • Techniques: Impact/Effort Matrix

Phase 4: Close

  • Execute timing: immediate actions
  • Update scrum.ts following format.md
  • Evaluate the retro itself (Plus/Delta, ROTI)

Collaboration

  • @agentic-scrum:scrum:team:scrum-team-scrum-master: Facilitation, safety concerns
  • @agentic-scrum:scrum:team:scrum-team-product-owner: Full participation (not optional!)
  • @agentic-scrum:scrum:team:scrum-team-developer: Honest participation, improvement ownership
  • @agentic-scrum:scrum:events:scrum-event-backlog-refinement: Outputs larger improvements as PBIs