pm-retro

Summarize iteration retrospectives into prioritized action items and markdown reports.

46|8|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/konglong87/superPM --skill pm-retro-konglong87
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-retro
Source: https://github.com/konglong87/superPM/tree/main/skills/03-growth-iteration/pm-retro
Command: npx skills add https://github.com/konglong87/superPM --skill pm-retro-konglong87

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Iteration retrospectives often become vague discussions without measurable outcomes or clear action items, so team improvements stall.

Core Features & Use Cases

  • Iteration goals recap & achievement evaluation: Reconcile planned vs. actual completion using structured inputs.
  • KPT-based team feedback collection: Capture Keep / Problem / Try items from the team to ground discussion in concrete observations.
  • Root-cause analysis & action planning: Run 5 Whys on the top problem and convert conclusions into prioritized owners, deadlines, and next-iteration targets—then generate a formal retro report document.

Quick Start

Use pm-retro after an iteration ends to compile a KPT-based retro, perform root-cause analysis, and generate an iteration retro report with action items.

Frequently Asked Questions about pm-retro

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

FAQPage Schema
How do I run an iteration retrospective that produces actionable improvement items?

To turn iteration wrap-ups into actionable improvements, evaluate goal achievement, collect KPT feedback, perform 5 Whys root-cause analysis, and generate a markdown report with prioritized action items under docs/.

How does KPT feedback collection work in a team retro?

KPT feedback collection in a team retro captures Keep, Problem, and Try items from the team to ground retrospective discussions in concrete observations and measurable team process improvements.

What is the best way to find the root cause of iteration problems?

The best way to find the root cause of iteration problems is running a 5 Whys analysis on the top identified problem, converting conclusions into prioritized owners and deadlines for the next iteration.

Can I use this retrospective process for both engineering and product teams?

Yes, this retrospective process supports post-iteration wrap-ups across product, engineering, design, QA, and operations teams when synthesizing goals, product metrics, and team feedback.

How do I convert retrospective lessons learned into a formal report?

Convert retrospective lessons learned into a formal report by completing interactive goal assessment, KPT collection, and root-cause analysis to generate a formal markdown retro report document under docs/.