sprint-retrospective

Facilitate structured sprint retrospectives using formats like Start-Stop-Continue, Mad-Sad-Glad, and 4Ls.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/supercent-io/skills-template --skill sprint-retrospective
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-retrospective
Source: https://github.com/supercent-io/skills-template/tree/main/.agent-skills/sprint-retrospective
Command: npx skills add https://github.com/supercent-io/skills-template --skill sprint-retrospective

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of conducting effective sprint retrospectives, ensuring teams can identify areas for improvement, foster collaboration, and drive continuous enhancement.

Core Features & Use Cases

  • Facilitates Retrospective Formats: Supports popular formats like Start-Stop-Continue, Mad-Sad-Glad, and 4Ls.
  • Action Item Generation: Helps in defining clear, actionable steps for improvement.
  • Use Case: After a challenging sprint, use this Skill to guide the team through a Mad-Sad-Glad retrospective, identify key pain points like deployment risks, and generate action items to address them in the next sprint.

Quick Start

Guide the team through a Start-Stop-Continue retrospective and document the outcomes.

Frequently Asked Questions about sprint-retrospective

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

FAQPage Schema
How do I facilitate a structured sprint retrospective for my agile team?

Facilitate a structured sprint retrospective by guiding your agile team through established formats like Start-Stop-Continue, Mad-Sad-Glad, or 4Ls to identify improvements and generate actionable items in a blame-free environment.

What is the Start-Stop-Continue format for team improvement?

The Start-Stop-Continue retrospective format asks agile teams to identify new practices to start, inefficient activities to stop, and successful workflows to continue, ensuring clear follow-up actions for team improvement.

When should I use a Mad-Sad-Glad retrospective instead of 4Ls?

Use a Mad-Sad-Glad retrospective after a challenging sprint to capture team emotions and identify key pain points, whereas 4Ls focuses on liked, learned, lacked, and longed-for elements for broader continuous enhancement.

Can I use this retrospective facilitation approach for any scrum team scale?

Yes, this retrospective facilitation approach supports any scrum team scale by maintaining a blame-free environment, structuring feedback through agile methodologies, and defining clear actionable steps for the next sprint.

What is the best way to generate actionable items from a project management retrospective?

The best way to generate actionable items from a project management retrospective is to use structured agile methodologies that identify specific team improvements and assign clear follow-up tasks for the next sprint.