retrospective

Generate structured team retrospective documents with action items and learnings.

4|3|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/yohayetsion/product-org-os --skill retrospective-yohayetsion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/yohayetsion/product-org-os/tree/main/product-org-plugin/skills/retrospective
Command: npx skills add https://github.com/yohayetsion/product-org-os --skill retrospective-yohayetsion

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of conducting effective team retrospectives by providing a structured framework to identify what went well, what didn't, capture learnings, and define actionable improvements.

Core Features & Use Cases

  • Structured Retrospective Generation: Creates comprehensive retrospective documents covering goals, context, successes, challenges, learnings, and action items.
  • Mode Flexibility: Supports creating new retrospectives, updating existing ones, or finding past retrospectives.
  • Context Integration: Facilitates saving learnings to a context registry for continuous improvement and updating assumptions.
  • Use Case: After a product launch, use this skill to run a retrospective to analyze the launch process, identify what worked well and what could be improved for future launches, and document key learnings.

Quick Start

Run a retrospective for the recent Q3 product launch.

Frequently Asked Questions about retrospective

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

FAQPage Schema
How do I run a structured retrospective to identify process improvements?

To run a structured retrospective, this skill analyzes project goals, deliverables, and participant feedback to generate actionable insights. It creates documents covering successes, challenges, learnings, and action items to drive continuous team improvement.

What is the best way to capture lessons learned after a project launch?

Capturing lessons learned is best handled by generating a retrospective document that analyzes the launch process. This skill defines actionable improvements and saves key learnings into a persistent context registry for future reference.

Can I update existing retrospective documents instead of creating new ones?

Yes, you can update existing retrospective documents. This skill supports mode flexibility, allowing you to create new retrospectives, update existing ones with new feedback, or find past retrospectives to track progress.

How do team retrospectives integrate learnings into a continuous learning loop?

Team retrospectives integrate learnings by saving captured insights directly into a persistent context registry. This updates project assumptions and ensures that past challenges inform future process improvements across the team.

What participant feedback do I need to provide for a team improvement retrospective?

You need to provide participant feedback alongside project goals and deliverables. The skill requires analyzing these inputs to accurately identify what went well, what challenges arose, and what actionable improvements should be tracked.