retro

Converts team feedback and sprint metrics into a markdown retro with prioritized action items.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often run retrospectives that surface observations but fail to convert them into a small set of clear, owned, and measurable improvements. This Skill structures the retro process, clarifies themes from raw feedback, analyzes sprint performance, and produces a concise markdown summary with prioritized action items and owners so improvements actually get executed.

Core Features & Use Cases

  • Structured Facilitation: Guides context confirmation, selects a retro format (Start/Stop/Continue, 4Ls, Sailboat), and focuses the discussion on root causes and improvements.
  • Feedback Synthesis: Groups sticky-note style feedback, identifies frequent themes and sentiment patterns, and links findings to sprint metrics and blockers.
  • Outcome Delivery: Produces a ready-to-share markdown retro report including sprint goal status, key themes, and 2-3 specific, assignable action items with owners, deadlines, and success metrics.
  • Use Case: Run this when finishing a sprint to convert team feedback and velocity data into a prioritized list of improvements to track in the next iteration.

Quick Start

Run a retrospective for the last sprint using the attached feedback and velocity chart to produce a markdown summary with 2-3 prioritized action items, owners, and dates.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I convert sprint retrospective feedback into actionable items?

To convert sprint retrospective feedback into actionable items, group raw team feedback into themes, analyze sprint velocity and blockers, and output 2-3 prioritized action items with assigned owners, deadlines, and success metrics.

What is the best way to run a post-mortem that surfaces root causes?

A structured post-mortem facilitation clarifies themes from raw feedback, focuses discussion on root causes, and links findings to sprint metrics to recommend measurable improvements rather than just listing observations.

How do I facilitate a sprint retro using Start Stop Continue or 4Ls formats?

Facilitate a sprint retro by selecting a format like Start/Stop/Continue, 4Ls, or Sailboat, then guide context confirmation and focus the team discussion on identifying root causes and continuous improvement.

Can I generate a markdown retrospective report from sprint metrics and feedback notes?

Yes, you can generate a ready-to-share markdown retrospective report by reading provided sprint metrics, feedback notes, and previous retro actions to summarize performance and output key themes with assigned action items.

Why do retrospective action items often fail to get executed by the team?

Retrospective action items fail when sessions surface observations without converting them into a small set of clear, owned, and measurable improvements, which is why structuring outcome delivery with owners and deadlines is critical.