Retro

What Is This?

Overview

The Retro skill provides a structured framework for running sprint retrospectives that produce real, actionable outcomes. Rather than letting retrospectives drift into unfocused conversation, this skill guides a facilitator through a proven format: identifying what went well, surfacing what did not, and converting team feedback into prioritized action items with clear owners and deadlines. The result is a retrospective that respects everyone's time and drives measurable improvement.

Retrospectives are one of the most valuable ceremonies in agile development, yet they are frequently mismanaged. Teams often leave retros with vague intentions instead of concrete commitments. The Retro skill addresses this by imposing a consistent structure that keeps discussion focused and ensures every identified problem has a path to resolution.

This skill integrates with AI-assisted workflows, allowing facilitators to prompt an AI agent to help synthesize team input, group themes, suggest action item owners, and draft follow-up summaries. It is particularly useful for distributed teams where a human facilitator cannot always manage all inputs simultaneously.

Who Should Use This

• Scrum Masters and Agile Coaches who run retrospectives regularly and want a repeatable, structured format that scales across multiple teams.
• Engineering Managers who facilitate retros for their direct reports and need to convert team sentiment into trackable improvement tasks.
• Product Managers who participate in or lead retrospectives and want to ensure product-related feedback is captured and acted upon.
• Team Leads in non-engineering contexts such as marketing or operations teams adopting sprint-based workflows.
• New facilitators who are learning how to run effective retros and need a guided structure to follow.
• Developers and individual contributors who want to self-facilitate a personal or small-team retrospective without a dedicated Scrum Master.

Why Use It?

Problems It Solves

• Retrospectives that produce no actionable outcomes, leaving teams with the same recurring issues sprint after sprint.
• Unstructured discussions that allow dominant voices to steer conversation away from critical problems.
• Missing ownership on action items, where tasks are identified but no one is accountable for completing them.
• Lack of prioritization, where teams attempt to fix ten things at once and accomplish none of them.
• Poor documentation, where retro insights are lost between sprints and never reviewed.

Core Highlights

• Structured three-part format covering what went well, what did not, and action items.
• Prioritized action item output with assigned owners and deadlines.
• AI-assisted synthesis of team feedback into grouped themes.
• Consistent format that works for in-person and remote teams.
• Produces a written summary suitable for team documentation or project management tools.
• Encourages psychological safety by separating observation from blame.
• Scales from small two-person teams to large cross-functional groups.

How to Use It?

Basic Usage

Invoke the Retro skill by providing the sprint context as an argument. A typical prompt structure looks like this:

Use the retro skill for Sprint 24, backend API team, two-week sprint ending Friday.

The skill will then guide the session through each phase, prompting for input and organizing responses.

Specific Scenarios

Scenario 1: Post-incident retrospective. After a production outage, use the Retro skill to structure a blameless post-mortem. Feed in the incident timeline and ask the skill to map events to the went-well and did-not-go-well categories before generating action items.

Scenario 2: Quarterly retrospective. For a longer review covering an entire quarter, provide a summary of completed sprints and key metrics. The skill will aggregate themes across multiple sprints and surface systemic issues.

Real-World Examples

A team struggling with repeated deployment failures used the Retro skill to identify that the root cause was inconsistent environment configuration. The action item generated was: "Standardize staging environment setup, owner: DevOps lead, deadline: next sprint."

A remote team used the skill to synthesize async feedback collected in a shared document, grouping 30 individual comments into five prioritized themes before the live session.

When to Use It?

Use Cases

• End of every sprint in a Scrum or Kanban workflow.
• After a major release or product launch.
• Following a production incident or significant team conflict.
• Onboarding a new team to agile practices.
• Quarterly or annual team health reviews.
• When a team is experiencing repeated delivery problems with no clear resolution.
• When a new facilitator is taking over retrospective responsibilities.

Important Notes

Requirements

• A defined sprint or time period to reflect on.
• Participant input collected before or during the session.
• A project management tool or document for recording action items.