retro

Facilitate structured sprint retrospectives and generate prioritized action items with owners and deadlines.

25.0k|2.7k|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/phuryn/pm-skills --skill retro-phuryn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/retro
Command: npx skills add https://github.com/phuryn/pm-skills --skill retro-phuryn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of conducting sprint retrospectives, ensuring that teams identify key learnings and create actionable improvements.

Core Features & Use Cases

  • Facilitates structured retrospectives: Guides users through common retrospective formats (Start/Stop/Continue, 4Ls, Sailboat).
  • Analyzes sprint performance: Assesses sprint goal achievement, velocity, and blockers.
  • Generates prioritized action items: Creates clear, actionable steps with owners and deadlines.
  • Use Case: After a sprint, use this Skill to gather team feedback, identify what went well and what could be improved, and define 2-3 concrete action items for the next sprint.

Quick Start

Run a sprint retrospective using the Start/Stop/Continue format for the last sprint.

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?

A structured sprint retrospective guides your team through formats like Start/Stop/Continue, 4Ls, or Sailboat to identify key learnings. It analyzes sprint performance metrics to generate actionable improvements for continuous team development.

How do I ensure sprint retrospective action items are actually completed?

To ensure action items are completed, define each step with clear owners and specific deadlines. Generating prioritized, actionable steps during the retrospective ensures accountability for continuous team improvement in the next sprint.

Can I analyze sprint performance metrics like velocity and blockers during an agile retrospective?

Yes, you can analyze sprint performance by assessing sprint goal achievement, team velocity, and identified blockers. Evaluating these metrics during an agile retrospective helps pinpoint specific areas needing team improvement.

What retrospective formats can I use to gather agile team feedback?

You can use common retrospective formats like Start/Stop/Continue, 4Ls, and Sailboat to gather agile team feedback. These structured formats help teams identify what went well, what to improve, and define concrete action items.

Do I need to define action item owners and deadlines for a successful sprint retrospective?

Yes, defining action items with clear owners and deadlines is required for a successful sprint retrospective. This continuous team improvement process ensures the 2-3 concrete steps identified are actually executed in the next sprint.

What is the best way to facilitate a retrospective for a completed agile sprint?

The best way to facilitate a retrospective for a completed agile sprint is using a structured format like Start/Stop/Continue. This process gathers team feedback, assesses sprint goal achievement, and generates prioritized action items for improvement.