retrospective

Generate sprint or milestone retrospectives from git log data.

Updated May 24, 2026
One-click install
npx skills add https://github.com/LeKay/ai-game --skill retrospective-lekay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/LeKay/ai-game/tree/main/.claude/skills/retrospective
Command: npx skills add https://github.com/LeKay/ai-game --skill retrospective-lekay

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of generating a sprint or milestone retrospective, providing a comprehensive analysis of completed work, identifying blockers, and suggesting improvements for the next iteration.

Core Features & Use Cases

  • Automated Retrospective Generation: Analyzes completed work, velocity, blockers, and patterns.
  • Actionable Insights: Provides actionable insights for the next iteration.
  • Use Case: Run this skill after a sprint or milestone to quickly review the period, identify areas for improvement, and plan the next steps.

Quick Start

Use the 'retrospective' skill to generate a sprint retrospective for the last 2 weeks.

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 log data?

To generate a sprint retrospective from git log data, you can use an automated tool that analyzes completed work, velocity, and blockers to provide actionable insights for the next iteration.

What is automated milestone review and how does it work?

Automated milestone review analyzes completed work, velocity tracking data, and blockers to identify patterns, providing actionable insights for planning the next iteration.

Can I use velocity tracking to identify blockers from my last sprint?

Yes, velocity tracking data can be analyzed alongside completed work and blockers to identify patterns and generate actionable insights for your next iteration.

Do I need sprint or milestone data access to run a retrospective analysis?

Yes, you need access to sprint or milestone data and the ability to execute commands like git log to generate a comprehensive retrospective analysis.

What's the best way to analyze sprint blockers and completed work?

The best way to analyze sprint blockers and completed work is using an automated retrospective tool that identifies patterns and suggests improvements for the next iteration.

Why does my milestone review not show actionable insights for the next iteration?

Your milestone review may not show actionable insights if the analysis lacks access to complete sprint data or cannot execute commands like git log to analyze blockers and patterns.