Retro

Name: Retro
Author: phuryn

phuryn/pm-skills

1.9k installs
24.9k repo stars
Updated July 3, 2026
phuryn/pm-skills

retro facilitates structured sprint retrospectives with actionable improvement items.

About

The retro skill runs structured sprint retrospectives that surface insights and produce actionable improvements. It supports Start/Stop/Continue and 4Ls (Liked, Learned, Lacked, Longed For) formats based on team context or user preference. Facilitators read provided sprint data, velocity charts, feedback, or prior retro notes when available. Output includes prioritized action items with owners and deadlines rather than vague themes. Use when running retros, reflecting on sprints, creating action items from team feedback, or learning effective retro facilitation patterns. Start/Stop/Continue and 4Ls retrospective format options Reads sprint data, velocity charts, and prior retro notes when provided Produces prioritized action items with owners and deadlines Structured facilitation rather than unstructured venting sessions Activates for sprint reflection and continuous improvement planning retro facilitates structured sprint retrospectives with actionable improvement items Retro summary with chosen format, insights, and prioritized actions with owners User runs a retro, reflects on a sprint, or needs retro action items Scrum masters and PMs facilitating sprint o

Start/Stop/Continue and 4Ls retrospective format options.
Reads sprint data, velocity charts, and prior retro notes when provided.
Produces prioritized action items with owners and deadlines.
Structured facilitation rather than unstructured venting sessions.
Activates for sprint reflection and continuous improvement planning.

Retro by the numbers

1,871 all-time installs (skills.sh)
+76 installs in the week ending Aug 5, 2026 (Skillselion tracking)
Ranked #272 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
Security screen: LOW risk (skills.sh audit)
Data as of Aug 5, 2026 (Skillselion catalog sync)

At a glance

retro capabilities & compatibility

Capabilities: format selection · sprint data intake · insight facilitation · action item prioritization · owner assignment
Use cases: planning · project management

From the docs

What retro says it does

Run a structured retrospective that surfaces insights and produces actionable improvements.

SKILL.md

npx skills add https://github.com/phuryn/pm-skills --skill retro

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/skills/phuryn/pm-skills/retro.svg)](https://skillselion.com/skills/phuryn/pm-skills/retro)

Installs	1.9k
repo stars	★ 24.9k
Security audit	3 / 3 scanners passed
Last updated	July 3, 2026
Repository	phuryn/pm-skills ↗

How do I run a retrospective that produces owned action items, not just discussion?

Facilitate structured sprint retrospectives with formats, insights, and prioritized action items with owners and deadlines.

Who is it for?

Scrum masters and PMs facilitating sprint or iteration retrospectives.

Skip if: Annual strategy offsites without sprint delivery context.

When should I use this skill?

User runs a retro, reflects on a sprint, or needs retro action items.

What you get

Retro summary with chosen format, insights, and prioritized actions with owners.

retro summary
prioritized action item list
improvement themes

Files

SKILL.mdMarkdownGitHub ↗

Sprint Retrospective Facilitator

Run a structured retrospective that surfaces insights and produces actionable improvements.

Context

You are facilitating a retrospective for $ARGUMENTS.

If the user provides files (sprint data, velocity charts, team feedback, or previous retro notes), read them first.

Instructions

1. Choose a retro format based on context (or let the user pick):

Format A — Start / Stop / Continue:

Start: What should we begin doing?
Stop: What should we stop doing?
Continue: What's working well that we should keep?

Format B — 4Ls (Liked / Learned / Lacked / Longed For):

Liked: What did the team enjoy?
Learned: What new knowledge was gained?
Lacked: What was missing?
Longed For: What do we wish we had?

Format C — Sailboat:

Wind (propels us): What's driving us forward?
Anchor (holds us back): What's slowing us down?
Rocks (risks): What dangers lie ahead?
Island (goal): Where are we trying to get to?

2. If the user provides raw feedback (e.g., sticky notes, survey responses, Slack messages):

Group similar items into themes
Identify the most frequently mentioned topics
Note sentiment patterns (frustration, energy, confusion)

3. Analyze the sprint performance:

Sprint goal: achieved or not?
Velocity vs. commitment (over-committed? under-committed?)
Blockers encountered and how they were resolved
Collaboration patterns (what worked, what didn't)

4. Generate prioritized action items:

Priority	Action Item	Owner	Deadline	Success Metric
1	[Specific, actionable improvement]	[Name/Role]	[Date]	[How we'll know it worked]

Limit to 2-3 action items (more won't get done)
Each must be specific, assignable, and measurable
Reference previous retro actions if available — were they completed?

5. Create the retro summary:

   ## Sprint [X] Retrospective — [Date]

   ### Sprint Performance
   - Goal: [Achieved / Partially / Missed]
   - Committed: [X pts] | Completed: [Y pts]

   ### Key Themes
   1. [Theme] — [summary]

   ### Action Items
   1. [Action] — [Owner] — [By date]

   ### Carry-over from Last Retro
   - [Previous action] — [Status: Done / In Progress / Not Started]

Save as markdown. Keep the tone constructive — the goal is improvement, not blame.