retro

Document post-deployment lessons with owners, dates, and follow-up steps.

15|6|Updated Jan 5, 2026
One-click install
npx skills add https://github.com/lionbenjamin/agent-templates --skill retro-lionbenjamin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/lionbenjamin/agent-templates/tree/main/skills/retro
Command: npx skills add https://github.com/lionbenjamin/agent-templates --skill retro-lionbenjamin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reflect on completed work to capture lessons, improve workflows, and drive continuous team learning.

Core Features & Use Cases

  • Structured reflection prompts to guide post-mortems and ensure consistency across teams.
  • Emphasis on systemic improvements, quality over speed, and actionable recommendations for documentation and processes.
  • Use Case: After delivering a feature, run a retro to extract insights, assign owners, and update workflows to prevent repeat mistakes.

Quick Start

Run a retro review after feature deployment and document what went well, what went wrong, and concrete improvements with owners and due dates.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I document lessons learned after feature deployment to reduce repeat failures?

To document lessons learned after feature deployment, run a structured retrospective that captures what went well, what went wrong, and actionable improvements with assigned owners and due dates.

What is the best way to structure a team retrospective for continuous process improvement?

The best way to structure a team retrospective for process improvement is using structured reflection prompts that enforce systemic recommendations, distinct dates, and specific owners within the documentation.

Can I use this retrospective process to enforce follow-up steps and team alignment across multiple teams?

Yes, you can use this retrospective process to enforce follow-up steps and team alignment across multiple teams by ensuring consistency through structured reflection prompts and actionable recommendations.

How do I run a post-mortem that assigns owners and due dates to workflow improvements?

To run a post-mortem that assigns owners and due dates, document what went well, what went wrong, and concrete workflow improvements, ensuring the process enforces distinct dates and follow-up steps.

When should I run a retrospective to capture lessons learned from completed work?

You should run a retrospective to capture lessons learned immediately after feature deployment or completing work, allowing your team to extract insights and update workflows to prevent repeat mistakes.