retrospective

Generate sprint or milestone retrospectives from plan data and repository trends.

Updated Dec 22, 2024
One-click install
npx skills add https://github.com/imgamer/AILearn --skill retrospective-imgamer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/imgamer/AILearn/tree/main/game-studios/Claude-Code-Game-Studios-e375f/.claude/skills/retrospective
Command: npx skills add https://github.com/imgamer/AILearn --skill retrospective-imgamer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams systematically convert completed sprint or milestone work into clear, data-backed lessons learned and prioritized improvements for the next iteration.

Core Features & Use Cases

  • Existing-retro detection and update vs. fresh generation: Locates prior retrospectives for the same sprint/milestone and either updates them with new data or archives the old one before starting fresh.
  • Sprint/milestone data loading with completion truth: Reads sprint or milestone plans and prioritizes production/sprint-status.yaml as the authoritative completion source, falling back to markdown scanning when needed.
  • Trend and quality signals from the repo: Uses Git history and codebase signals (TODO/FIXME/HACK counts) to surface velocity trends, recurring issues, and technical-debt direction.
  • Decision-ready output: Produces an end-to-end retrospective including metrics, blockers, estimation accuracy, carryover analysis, and 3–5 concrete action items with owners and deadlines.

Quick Start

Generate a sprint retrospective for sprint 7 by running the retrospective skill with the argument sprint-7.

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 existing milestone data?▼

Generating a sprint retrospective involves parsing planned work, loading completion status from sprint-status.yaml, scanning Git history for TODO/FIXME/HACK trends, and outputting a markdown file with metrics, blockers, and action items.

What is estimation accuracy analysis in agile retrospectives?▼

Estimation accuracy analysis compares planned sprint work against actual completion status to calculate velocity trends, identify carryover, and surface recurring blockers for the next iteration.

Can I use sprint-status.yaml as the ground truth for agile retrospective completion data?▼

Yes, sprint-status.yaml is prioritized as the authoritative completion source for agile retrospectives, falling back to markdown scanning only when needed to verify actual completion status and calculate velocity metrics.

How do I track technical debt trends from git history for a milestone retrospective?▼

Tracking technical debt trends involves scanning Git history and the codebase for TODO, FIXME, and HACK counts to surface recurring issues, velocity trends, and technical-debt direction within your milestone retrospective.

Does the retrospective skill update existing retrospectives or create new ones?▼

The retrospective skill detects existing markdown retrospectives for the same sprint or milestone and either updates them with new data or archives the old one before generating a fresh file with current metrics and action items.

What do I need to run an agile retrospective and get action items with owners?▼

You need sprint or milestone plan data, optionally a sprint-status.yaml file for completion truth, and repository access for Git analytics to generate a retrospective with 3-5 concrete action items including assigned owners and deadlines.