scrum-event-sprint-retrospective

Facilitate sprint retrospectives and update scrum.ts with improvement actions.

8|Updated Dec 29, 2025
One-click install
npx skills add https://github.com/atusy/agentic-scrum --skill scrum-event-sprint-retrospective-atusy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scrum-event-sprint-retrospective
Source: https://github.com/atusy/agentic-scrum/tree/main/claude-plugins/agentic-scrum/skills/scrum-event-sprint-retrospective
Command: npx skills add https://github.com/atusy/agentic-scrum --skill scrum-event-sprint-retrospective-atusy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides AI-assisted Sprint Retrospectives to surface actionable improvements and ensures learnings are translated into concrete updates to the Scrum artifacts, notably scrum.ts.

Core Features & Use Cases

  • Gather Data: collect sprint outcomes, conversation history, and the sprint git log to surface what happened.
  • Generate Insights: identify key topics, root causes, and potential improvements.
  • Decide What to Do: propose concrete actions, prioritize them, and update scrum.ts following format.md.
  • Close: capture outcomes (Plus/Delta, ROTI) and plan timely follow-ups with DoD alignment.

Quick Start

Prompt the AI to guide your team through a Sprint Retrospective, collecting data, generating insights, and selecting actions to update scrum.ts.

Frequently Asked Questions about scrum-event-sprint-retrospective

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an agile sprint retrospective that produces concrete improvement actions?

A sprint retrospective gathers sprint outcomes and conversation history to generate insights, identify root causes, and define concrete actions for team improvement.

How do I update scrum.ts with retrospective actions following format.md?

You update scrum.ts by proposing concrete actions during the retrospective, prioritizing them, and formatting the updates according to format.md to maintain your single source of truth.

Can I use conversation history and git logs to identify agile retrospective insights?

Yes, sprint retrospectives can collect conversation history and the sprint git log as data sources to surface what happened, identify key topics, and generate root cause insights for team improvement.

What is the best way to enforce a Definition of Done for sprint retrospective actions?

The best way to enforce a Definition of Done for retrospective actions is to close the retrospective by capturing outcomes, planning timely follow-ups, and aligning the proposed actions with the DoD requirements.

Does this sprint retrospective process support capturing Plus/Delta and ROTI outcomes?

Yes, the sprint retrospective process supports capturing Plus/Delta and ROTI outcomes during the close phase to evaluate the meeting effectiveness and document the team's continuous improvement feedback.