retrospective

Generate sprint retrospective reports from git logs and project plans.

23.7k|3.4k|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/Donchitos/Claude-Code-Game-Studios --skill retrospective-donchitos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/Donchitos/Claude-Code-Game-Studios/tree/main/.claude/skills/retrospective
Command: npx skills add https://github.com/Donchitos/Claude-Code-Game-Studios --skill retrospective-donchitos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the generation of comprehensive sprint or milestone retrospectives, transforming raw project data into actionable insights for continuous improvement.

Core Features & Use Cases

  • Data Aggregation: Gathers data from git logs, sprint plans, and previous retrospectives.
  • Performance Analysis: Analyzes completed work, velocity trends, blockers, and estimation accuracy.
  • Actionable Insights: Identifies recurring issues and suggests specific, measurable action items for the next iteration.
  • Use Case: After completing a two-week sprint, use this Skill to automatically generate a retrospective report detailing what went well, what didn't, key blockers, and concrete steps to improve the next sprint.

Quick Start

Use the retrospective skill to generate a retrospective for sprint-3.

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 logs and project plans?

To generate a sprint retrospective, this Skill aggregates git logs, sprint plans, and historical data to identify performance metrics, blockers, and estimation accuracy. It outputs a structured report with actionable improvement items for the next iteration.

What is the best way to analyze team performance metrics after a sprint?

Analyzing team performance metrics is done by evaluating completed work, velocity trends, and estimation accuracy against historical data. The process identifies recurring blockers and technical debt trends to produce specific, measurable action items.

Can I automate retrospective data collection for continuous team improvement?

Automated retrospective data collection is supported natively. The Skill gathers raw project data from git logs and previous plans, transforming it into structured insights without manual entry to facilitate continuous team improvement.

How do I identify technical debt trends and blockers in an agile project?

Identifying technical debt trends and blockers involves analyzing git logs and historical sprint data. The Skill evaluates this aggregated data to pinpoint recurring issues and generate concrete steps for improving the next sprint.

Do I need previous retrospective reports to analyze estimation accuracy?

Previous retrospective reports and sprint plans are used to accurately analyze estimation accuracy. The Skill gathers this historical data alongside git logs to compare planned work with completed work and identify velocity trends.

What actionable insights can I get from an agile milestone analysis?

Actionable insights from agile milestone analysis include specific improvement items for the next iteration. The Skill identifies what went well, what failed, key blockers, and technical debt trends to produce measurable steps for the next sprint.