retrospectiva

Runs structured retrospectives after delivery cycles to capture learnings and calibration data.

Updated May 31, 2026
One-click install
npx skills add https://github.com/ithaloazevedo/pm-loadout --skill retrospectiva-ithaloazevedo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retrospectiva
Source: https://github.com/ithaloazevedo/pm-loadout/tree/main/.agents/skills/retrospectiva
Command: npx skills add https://github.com/ithaloazevedo/pm-loadout --skill retrospectiva-ithaloazevedo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often finish delivery increments without systematically capturing what worked, what failed, and how accurate their estimates were, losing valuable learning for continuous improvement. ## Core Features & Use Cases - Cycle Calibration Recording: Logs predicted versus actual ICE scores, effort estimates, and risk assessments to track estimation accuracy over time. - Root Cause Analysis: Applies fishbone diagrams, 5 Whys, and Ohno's 7 wastes framework to diagnose significant problems systemically. - Bias Mitigation: Includes counter-argument checks and hindsight bias detection to prevent post-hoc rationalization in retrospective conclusions. - Use Case: After shipping a feature, run this skill to record the cycle outcome, analyze what went well and poorly using blameless post-mortem format, and update corrections and patterns for future work. ## Quick Start Run a retrospective for the delivery cycle we just completed and capture the key learnings and calibration data.

Frequently Asked Questions about retrospectiva

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

FAQPage Schema
How do I run a retrospective after a product delivery cycle?

Run the retrospective skill after completing a delivery increment. It first records the cycle with predicted versus actual ICE scores and effort, then walks through what went well, what didn't, root cause analysis, and BVSSH dimension checks.

What root cause analysis techniques work for product teams?

This skill combines fishbone (Ishikawa) diagrams for breadth across people, process, product, platform, principles, and pressures, with 5 Whys for depth on the top-ranked cause. It also maps problems to Ohno's 7 wastes before analysis.

How do I track estimation accuracy over multiple delivery cycles?

The skill records predicted ICE scores, effort estimates, and risk assessments alongside actual outcomes in a cycle history file. Calibration summaries accumulate across cycles, prompting a framework health review every 5 cycles.

Does this retrospective format work without Claude-specific tooling?

Yes, the skill supports standalone mode where canvas and persistence references are treated as optional. It delivers the retrospective artifact directly in the conversation and only writes to authorized canonical sources when requested.

How do retrospectives avoid hindsight bias and false patterns?

The skill requires drafting counter-arguments for each major claim and checking whether 'should have seen it' claims were actually predictable from pre-outcome evidence. This prevents manufacturing false patterns from post-hoc rationalization.