retro

Facilitate structured sprint retrospectives and generate prioritized action items.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/runchr-com/pm-skills-gemini --skill retro-runchr-com
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/runchr-com/pm-skills-gemini/tree/main/.gemini/skills/retro
Command: npx skills add https://github.com/runchr-com/pm-skills-gemini --skill retro-runchr-com

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of conducting sprint retrospectives, ensuring that teams identify what went well, what needs improvement, and generate actionable steps with clear ownership and deadlines.

Core Features & Use Cases

  • Facilitates structured retrospectives: Offers multiple formats (Start/Stop/Continue, 4Ls, Sailboat) to suit different team needs.
  • Analyzes sprint performance: Evaluates sprint goal achievement, velocity, blockers, and collaboration.
  • Generates prioritized action items: Creates specific, measurable, achievable, relevant, and time-bound (SMART) action items.
  • Summarizes retro outcomes: Provides a concise markdown summary of the retrospective.
  • Use Case: After a challenging sprint, use this Skill to guide the team through a retrospective, identify key issues, and define concrete steps to improve the next sprint.

Quick Start

Run a retrospective for the 'AI Meeting Summarizer' project.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I run a structured sprint retrospective to identify team improvements?

To run a structured sprint retrospective, use a format like Start/Stop/Continue, 4Ls, or Sailboat to guide team reflection on sprint goals, velocity, and blockers. This process analyzes sprint performance and generates prioritized SMART action items with clear ownership and deadlines.

What is the best retrospective format for analyzing sprint performance and blockers?

The best retrospective format depends on team needs: Start/Stop/Continue for direct feedback, 4Ls for broad categorization, or Sailboat for visualizing blockers and drivers. Each format supports analyzing sprint goals, velocity, and collaboration patterns to drive continuous improvement.

How do I generate prioritized action items from an agile retrospective?

To generate prioritized action items from an agile retrospective, analyze sprint performance, blockers, and collaboration patterns. The process creates specific, measurable, achievable, relevant, and time-bound (SMART) action items with clear ownership and deadlines to ensure team accountability.

Can I summarize retrospective outcomes in markdown for my agile team?

Yes, you can summarize retrospective outcomes in markdown. The process provides a concise markdown summary of the retrospective, capturing what went well, what needs improvement, and the generated action items to document team reflections and drive continuous improvement.

When do I need to use a structured retrospective process for sprint improvement?

You need a structured retrospective process for sprint improvement after completing a sprint, especially a challenging one. It helps evaluate sprint goal achievement, velocity, and collaboration patterns to identify key issues and define concrete steps to improve the next sprint.