my-retro

Create retrospective summaries from plan and review files with commit log analysis.

Updated May 8, 2026
One-click install
npx skills add https://github.com/mike2ox/my-claude-code-config --skill my-retro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: my-retro
Source: https://github.com/mike2ox/my-claude-code-config/tree/main/skills/my-retro
Command: npx skills add https://github.com/mike2ox/my-claude-code-config --skill my-retro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, yaml, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a structured framework for generating a retrospective summary that captures and analyzes the outcomes of a project or sprint, helping teams reflect on their performance and identify areas for improvement.

Core Features & Use Cases

  • Integrated Analysis: Combines information from plan and review files to provide a holistic view of the project's progress.
  • Summary Generation: Automatically creates a comprehensive summary that outlines the project goals, implementation details, and feedback received.
  • Learning and Insights: Encourages teams to document key learnings and insights for future reference and improvement.

Quick Start

Initiate the retro process by executing the /my-retro command.

Frequently Asked Questions about my-retro

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

FAQPage Schema
How do I generate a sprint retrospective summary from git commit logs?

You can create a comprehensive retrospective summary by executing the /my-retro command. This initiates the analysis of your project's plan and review files to automatically generate a detailed summary of goals, implementations, and received feedback.

Does this retrospective tool require specific file formats for plan and review files?

Yes, the retrospective analysis requires YAML-formatted plan and review files to properly integrate and parse project data. It also depends on Git to extract and analyze the commit logs necessary for comparing planned versus implemented features.

What is the best way to compare planned versus implemented features for a project review?

The best way to compare planned versus implemented features is to use an integrated analysis framework that cross-references your original plan files with actual Git commit logs. This approach categorizes feedback and highlights development discrepancies for improvement planning.

Can I use this tool to categorize team feedback for project closure?

Yes, you can use this Skill for project closure to categorize team feedback. It integrates review files and commit logs to document key learnings and insights, encouraging teams to systematically identify areas for future improvement.

What are the limitations of using YAML files for work summary generation?

The primary limitation is that the work summary generation strictly requires YAML file formats for plan and review inputs, alongside Git for commit log analysis. Without these specific dependencies properly configured, the integrated retrospective analysis cannot be generated.