retro

Name: retro
Availability: InStock
Author: Panaversity

Run structured product retrospectives to turn launch outcomes into actionable improvements.

28|19|Updated Mar 5, 2026

Search Tags:#learning #retrospective #product #outcomes #process-improvement #retro

Ready to run

npx skills add https://github.com/panaversity/agentfactory-business-plugins --skill retro-panaversity

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/panaversity/agentfactory-business-plugins/tree/main/product-strategy/skills/retro
Command: npx skills add https://github.com/panaversity/agentfactory-business-plugins --skill retro-panaversity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product retrospectives help teams capture learning from launches and inform improvements, turning reflections into actionable plans.

Core Features & Use Cases

Structured four-question framework: Did it solve the problem, was it built as intended, were the metrics right, and what would we do differently.
Data-driven outcomes: tracks adoption, engagement, and delivery signals to guide future iterations.
Complementary PM workflows: integrates with metrics-review, stakeholder-update, and roadmap updates to close the loop.

Quick Start

Run a product retrospective for a shipped feature, capturing context data and producing concrete, shareable learnings.

Frequently Asked Questions about retro

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

FAQPage Schema

How do I run a structured product retrospective after a feature launch?▼

Run a product retrospective by evaluating a structured four-question framework: whether it solved the problem, was built as intended, metrics were right, and what to do differently. This turns launch outcomes into actionable improvements and shareable learnings.

What is a data-driven retrospective and what inputs do I need?▼

A data-driven retrospective requires outcome data, lessons learned, and a formal retro format to evaluate launch results. By tracking adoption, engagement, and delivery signals, it guides future iterations based on concrete metrics rather than subjective feedback.

Can I use this retrospective process for sprint reviews and engineering teams?▼

Yes, the retrospective process supports post-launch reviews, sprint retrospectives, and feature retrospectives across product, engineering, and business teams, ensuring structured reflection and process improvement regardless of team function.

What's the best way to turn retrospective lessons into actionable product improvements?▼

The best way to turn lessons into improvements is capturing context data and outcome metrics through a formal retro workflow, producing concrete plans that integrate with metrics-review, stakeholder-update, and roadmap updates to close the loop.

How does a product retrospective connect to downstream roadmap updates?▼

A product retrospective connects to roadmap updates by functioning as a complementary PM workflow, feeding captured learnings and outcome data into stakeholder-update and metrics-review processes to inform and guide future product iterations.

Do I need outcome metrics before starting a feature retrospective?▼

Yes, outcome metrics are required as a formal input for a feature retrospective. The process enforces data-driven requirements by tracking adoption, engagement, and delivery signals to accurately evaluate whether the launched feature solved the intended problem.