retrospective

Analyze sprint data to generate structured retrospective reports with metrics.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/dawn840705/claude-code-game-studios --skill retrospective-dawn840705
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/dawn840705/claude-code-game-studios/tree/main/skills/retrospective
Command: npx skills add https://github.com/dawn840705/claude-code-game-studios --skill retrospective-dawn840705

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates a sprint or milestone retrospective by analyzing completed work, velocity, blockers, and patterns. Produces actionable insights for the next iteration.

Core Features & Use Cases

  • Analyze sprint/milestone data to produce a structured retrospective report, including metrics like completion, velocity trend, blockers, and technical debt status.
  • Compare planned vs actual work, identify carryovers, unplanned work, and action items for the next iteration.
  • Reuse or reference previous retrospectives to identify recurring issues and track improvement.

Quick Start

Generate a sprint retrospective for sprint-12 using the latest production sprints data and milestone data if applicable.

Frequently Asked Questions about retrospective

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

FAQPage Schema
How do I auto-generate a sprint retrospective from git logs and velocity data?▼

To auto-generate a sprint retrospective, the tool analyzes production sprints, git logs, and milestone data. It calculates velocity trends and identifies blockers to produce a ready-to-save retrospective template.

What metrics are included in an agile sprint retrospective report?▼

An agile sprint retrospective report includes metrics for work completion, velocity trends, and technical debt status. It also compares planned versus actual work to identify carryovers and unplanned tasks.

Can I compare planned vs actual work to identify sprint carryovers and blockers?▼

Yes, you can compare planned versus actual work to identify sprint carryovers and blockers. The analysis highlights unplanned work and generates specific action items for the next iteration.

Does this tool work with production sprints and milestone data for milestone assessments?▼

Yes, this tool works directly with production sprints and milestone data for milestone assessments. It uses git logs and completed work records to derive actionable insights for future iterations.

How do I track recurring blockers across multiple sprint retrospectives?▼

You can track recurring blockers by reusing or referencing previous sprint retrospectives. This process identifies recurring issues over time and tracks improvements across iterations.

What is the best way to analyze unplanned work and technical debt in a sprint review?▼

The best way to analyze unplanned work and technical debt in a sprint review is by evaluating completion metrics and blocker patterns. This yields actionable insights and structured action items for the next iteration.