retrospective

Generate structured markdown sprint retrospectives from git history and plan data.

1|Updated May 5, 2026
One-click install
npx skills add https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios --skill retrospective-xganqaq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios/tree/main/.claude/skills/retrospective
Command: npx skills add https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios --skill retrospective-xganqaq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents teams from repeating the same mistakes by converting messy sprint or milestone outcomes into a structured, data-backed retrospective with concrete next-step action items.

Core Features & Use Cases

  • Sprint/Milestone retrospective generation: Produces a complete retro including metrics, velocity trend, blockers, estimation accuracy, carryover analysis, and follow-up.
  • Plan vs reality analysis: Compares the sprint/milestone plan with actual git commits to identify completed, modified, carried over, added, and removed work.
  • Technical debt trend scanning: Counts TODO/FIXME/HACK signals to help assess whether debt is growing or shrinking and spot recurring issues.
  • Actionable output with writing step: Presents results and then saves the retrospective to the appropriate production/ path after user confirmation.

Quick Start

Run the retrospective skill for a specific sprint by providing the argument sprint-N, for example: invoke retrospective with sprint-3 to generate and optionally save the sprint 3 retrospective.

Frequently Asked Questions about retrospective

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

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

To generate a sprint retrospective from git history, the skill compares your sprint plan with actual git commits to identify completed, modified, and carried over work, then produces a structured markdown file.

What is plan vs reality analysis in a sprint retrospective?

Plan vs reality analysis in a sprint retrospective compares planned sprint tasks against actual git commits to identify completed, modified, carried over, added, and removed work.

How do I track technical debt trends during a sprint analysis?

You track technical debt trends during sprint analysis by scanning the git history for TODO, FIXME, and HACK signals to assess whether debt is growing or shrinking over the period.

Do I need existing sprint plans to run a milestone retrospective?

Yes, you need existing sprint or milestone plans maintained in the production directory, as the retrospective requires loading plan data to compare against actual git commits.

Can I save the retrospective output directly to my project directory?

Yes, after presenting the retrospective results, the skill can save the structured markdown file directly to the production/sprints or production/retrospectives path after user confirmation.

What's the best way to analyze velocity trends and blockers for a completed sprint?

The best way to analyze velocity trends and blockers is by inspecting prior retrospectives and actual git history to produce a structured report with metrics, estimation accuracy, and carryover analysis.