skills.rest
nmrtn
nmrtnCOMMUNITY
Explore all skills by this author →
GitHub

pm-retro

Analyze ROADMAP.md NOW items against git commits and generate a RETRO.md report.

42|2|Updated Mar 28, 2026
Search Tags:#git#planning#retrospective#roadmap#project-management#commit-history
One-click install
npx skills add https://github.com/nmrtn/nanopm --skill pm-retro-nmrtn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm-retro
Source: https://github.com/nmrtn/nanopm/tree/main/pm-retro
Command: npx skills add https://github.com/nmrtn/nanopm --skill pm-retro-nmrtn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PM retrospectives help product teams understand how NOW items tracked in ROADMAP.md align with the actual commits since the last roadmap run. It surfaces what shipped, what drifted, and what to carry forward to the next cycle, closing the planning loop and improving forecasting.

Core Features & Use Cases

  • Compare ROADMAP.md NOW items to git history to determine what was delivered, drift, and gaps.
  • Surface drift, gaps, and carry-forward items to inform the next roadmap.
  • Generate a machine-readable RETRO.md summary that can be committed and shared across the team.
  • Integrate with /pm-roadmap to refresh priorities and plan the next cycle.

Quick Start

Run /pm-retro to generate a retrospective for your current project.

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 project retrospective by mapping git commits to a roadmap?▼

Generate a retrospective by running the command to read ROADMAP.md NOW items and inspect git commit history since the last roadmap commit, producing a .nanopm/RETRO.md report summarizing shipped work, drift, and carry-forward items.

What is a commit-based retrospective for product management?▼

A commit-based retrospective analyzes git commit messages against planned ROADMAP.md NOW items to surface what shipped, what drifted, and what gaps to carry forward to the next cycle, closing the planning loop and improving forecasting.

Does the retrospective tool require any specific dependencies to analyze git history?▼

No dependencies are required to analyze git history and generate the retrospective report. The tool directly reads ROADMAP.md and inspects commit messages natively to map delivered work against planned items.

Can I use this retrospective report to plan my next project cycle?▼

Yes, the retrospective report identifies drift, gaps, and carry-forward items from your git history to inform the next roadmap. It integrates with /pm-roadmap to refresh priorities and plan the next cycle.

What's the best way to track roadmap drift using git history?▼

The best way to track roadmap drift is comparing ROADMAP.md NOW items against actual commit messages since the last roadmap commit, which surfaces gaps and drift in a machine-readable RETRO.md summary for team sharing.

Related Skills

Explore More Product & Management Skills→
jugrajsinghjugrajsingh
1

changelog

Generates Keep a Changelog formatted changelogs from git commit history since the last tag.

Community
Intermediate
tapaniatapania
5

5d-reflect

Capture completed work learnings into a formal Iteration Retrospective.

Community
Basic
indranilbanerjeeindranilbanerjee
726

qbr-plan

Aggregate campaign performance data into a 12- to 15-slide QBR presentation.

Community
Advanced
drvossdrvoss
42

sprint-retro

Generate a markdown sprint retrospective report from Copilot CLI session history and Git metrics.

Community
Intermediate