pm-retro

Generate structured sprint retrospectives from PMContext and team feedback.

1|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/Wcof/PMSkill --skill pm-retro-wcof
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-retro
Source: https://github.com/Wcof/PMSkill/tree/main/skills/delivery/pm-retro
Command: npx skills add https://github.com/Wcof/PMSkill --skill pm-retro-wcof

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams run a structured retrospective when iteration feedback, delivery artifacts, and process signals are scattered across PMContext and project outputs. It turns vague reflections or complaint-heavy reviews into concrete themes, prioritized action items, and reusable lessons that can improve the next cycle.

Core Features & Use Cases

  • Structured retrospective generation: Produces one of three retrospective formats: Start/Stop/Continue, 4Ls, or Sailboat.
  • Theme aggregation from evidence: Groups raw feedback into recurring themes, adds frequency and sentiment, and uses workflow artifacts when direct feedback is missing.
  • Action-oriented follow-through: Creates prioritized action items with owner, due date, and measurable threshold so outcomes are executable rather than aspirational.
  • Knowledge loop closure: Writes reusable experience and learning records back into PMContext so future planning and delivery can benefit from past iteration insights.
  • Use case: After a sprint or product iteration, a PM can use this Skill to review PRD, sketch, loop artifacts, and team comments, then produce a clear retro report with top issues, next actions, and reusable team operating rules.

Quick Start

Ask the AI to run pm-retro for your latest iteration and generate a retrospective with grouped themes, prioritized action items, and PMContext learnings.

Frequently Asked Questions about pm-retro

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

FAQPage Schema
How do I generate a structured sprint retrospective from scattered feedback and iteration artifacts?

To generate a sprint retrospective, this Skill aggregates iteration artifacts and team feedback into recurring themes with sentiment labeling, then produces a structured retro report using Start/Stop/Continue, 4Ls, or Sailboat formats.

What is the best way to turn vague sprint review feedback into prioritized action items?

The best way to turn vague feedback into prioritized action items is by clustering comments into recurring themes by frequency, then assigning each item a specific owner, due date, and measurable success metric.

Can I run a delivery postmortem using workflow artifacts when direct team feedback is missing?

Yes, you can run a delivery postmortem using workflow artifacts. The Skill groups available PRD, sketch, and loop artifacts into themes to compensate when direct team feedback is missing.

How does capturing iteration learning in PMContext improve future sprint planning?

Capturing iteration learning in PMContext improves future sprint planning by writing reusable experience and team operating rules back into the context, closing the knowledge loop for subsequent delivery cycles.

Do I need a specific retrospective format like 4Ls or Sailboat to analyze iteration feedback?

No, you do not need a specific format. The Skill supports agile review scenarios using Start/Stop/Continue, 4Ls, or Sailboat formats, allowing you to choose the structure that best fits your iteration reflection.