pm-retrospect

Triage sprint observations and tensions to validate PM coordination decisions.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/LopeWale/amplLABS --skill pm-retrospect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-retrospect
Source: https://github.com/LopeWale/amplLABS/tree/main/.claude/skills/pm-retrospect
Command: npx skills add https://github.com/LopeWale/amplLABS --skill pm-retrospect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps product teams challenge assumptions by systematically triaging sprint observations and tensions, turning evidence into actionable insights and proposals to improve PM coordination and outcomes.

Core Features & Use Cases

  • Triages observations and tensions from sprint coordination to surface durable patterns and decision gaps.
  • Generates concrete proposals for process improvements aligned with collected evidence.
  • Triggers on commands like /pm-retrospect or "review observations" to load context and drive iterative improvements.

Quick Start

Start the PM retrospective flow by running the PM retrospective to perform drift checks, triage observations, and generate improvement proposals.

Frequently Asked Questions about pm-retrospect

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

FAQPage Schema
How do I run an evidence-driven product management retrospective?

To run an evidence-driven PM retrospective, triage sprint observations and tensions to validate coordination decisions, applying drift checks and pattern detection to generate actionable process improvement proposals.

What is the best way to triage sprint observations and tensions?

The best way to triage sprint observations is to systematically validate accumulated evidence against PM coordination decisions, using drift checks and pattern detection to surface durable workflow patterns and decision gaps.

How do sprint retrospectives validate PM coordination decisions?

Sprint retrospectives validate PM coordination decisions by challenging assumptions through triaging accumulated evidence, detecting behavioral drift, and identifying durable patterns in product management workflows.

Can I generate concrete process improvement proposals from sprint tensions?

Yes, you can generate concrete process improvement proposals by triaging sprint tensions and observations, applying pattern detection to uncover decision gaps, and aligning proposals with collected evidence.

When do I need to apply drift checks during a sprint retrospective?

You need to apply drift checks during a sprint retrospective when reviewing observations to validate PM coordination decisions against accumulated evidence and surface durable workflow patterns.

Why should product teams challenge assumptions in sprint retrospectives?

Product teams should challenge assumptions in sprint retrospectives to systematically triage observations and tensions, turning accumulated evidence into actionable insights that improve PM coordination and outcomes.