retro

Generate structured retrospectives from git, GitHub, and planning data.

9|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/koolamusic/claudefiles --skill retro-koolamusic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/koolamusic/claudefiles/tree/main/skills/retro
Command: npx skills add https://github.com/koolamusic/claudefiles --skill retro-koolamusic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents project knowledge loss by turning completed phases, sprints, and milestones into structured retrospectives that expose failures, decisions, risks, and lessons instead of relying on incomplete memory or informal summaries.

Core Features & Use Cases

  • Structured Retrospectives: Generates consistent 10-section retrospectives with findings, decisions, metrics, risks, learnings, artifacts, and stakeholder summaries.
  • Multi-Source Analysis: Combines project planning data, git history, GitHub activity, and user input to build evidence-based retrospectives.
  • Use Case: A development team finishing a major migration can use this Skill to document what happened, identify recurring risks, and create a stakeholder-friendly report for future phases.

Quick Start

Use the retro skill to generate an honest retrospective for the most recently completed phase of this project.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I generate a sprint retrospective from git history and GitHub activity?

You can generate a retrospective by combining project planning data, git history, and GitHub activity to build an evidence-based report. This process captures project outcomes, failures, and decisions into a structured format for stakeholders.

What is the best way to document project failures and decisions after a milestone?

The best way to document project failures and decisions is through structured retrospectives that expose risks and lessons learned. This prevents project knowledge loss by replacing incomplete memory with consistent, stakeholder-ready summaries.

Can I create a stakeholder report from manual project context without a planning system?

Yes, you can create a stakeholder report using manual context input. The Skill applies validation rules to generate complete retrospectives even without automated planning systems or specific git integrations.

Does the retrospective generation process require specific project management tools?

No, the retrospective generation process works with git, GitHub, planning systems, or manual context. It uses provider-based data collection and configuration handling to accommodate various project management setups.

How do I structure a project review to include metrics, risks, and artifacts?

Structure a project review using a consistent 10-section format covering findings, decisions, metrics, risks, learnings, artifacts, and stakeholder summaries. This ensures all critical retrospective elements are captured systematically.