retro

Generate structured retrospective reports from coding sessions with lessons and root causes.

Updated Jul 5, 2025
One-click install
npx skills add https://github.com/sqfzy/my_configs --skill retro-sqfzy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/sqfzy/my_configs/tree/main/claude/skills/retro
Command: npx skills add https://github.com/sqfzy/my_configs --skill retro-sqfzy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates a structured retrospective after a coding session, capturing lessons learned, pitfalls, insights, and key decisions to provide long-term context and continuous improvement.

Core Features & Use Cases

  • Creates a reusable post-mortem after feature work, debugging, or refactors.
  • Extracts actionable lessons, root causes, and decision points with supporting context.
  • Produces a formatted retrospective report suitable for sharing with teammates or documentation.

Quick Start

Generate a structured retrospective for my last coding session.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I generate a postmortem after a complex coding session?

Generate a postmortem by consolidating multiple commits into a structured retrospective. This captures lessons learned, pitfalls, and key decisions to provide long-term context and continuous improvement after feature work or refactoring.

What is the best way to capture lessons learned from a debugging session?

Capture lessons learned from a debugging session by creating a reusable retrospective. The process extracts actionable root causes, insights, and decision points with supporting context into a formatted report.

Can I create a structured retrospective for a multi-commit refactoring effort?

Yes, you can create a structured retrospective for a multi-commit refactoring effort. The process produces a reproducible report with sections for timelines, lessons, root causes, decisions, and next steps.

Does a software engineering retrospective report include decision points?

Yes, a software engineering retrospective report includes decision points. It extracts key decisions with supporting context alongside lessons learned, pitfalls, and root causes into a formatted report.

When do I need to generate a postmortem for my code?

Generate a postmortem for your code after completing a feature, debugging, or refactor effort spanning multiple commits. It provides long-term context and continuous improvement by capturing key decisions and root causes.

Can I control the scope and depth of a coding session retrospective?

Yes, you can control the scope and depth of a coding session retrospective. The process offers optional scope and depth controls to produce a reproducible report tailored to your documentation needs.