skills.rest
polsegu
polseguCOMMUNITY
Explore all skills by this author →
Website𝕏@Polsegu11GitHub

retrospective

Generate sprint retrospectives by comparing plans against git commit history.

Updated Apr 10, 2026
Search Tags:#git#retrospective#velocity#sprint#milestone#action-items#technical-debt
One-click install
npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill retrospective-polsegu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/polsegu/Claude-Code-Game-Dev/tree/main/.claude/skills/retrospective
Command: npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill retrospective-polsegu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the synthesis of sprint or milestone outcomes into a clear, data-backed retrospective so teams can learn from what happened and plan measurable improvements rather than relying on vague recollections.

Core Features & Use Cases

  • Plan vs. Reality Analysis: Compares sprint or milestone plans against commit history and completed tasks to identify carried-over work, scope changes, and unplanned additions.
  • Metrics & Trends: Calculates completion rates, velocity trends, TODO/FIXME/HACK counts, and follow-up on previous action items to reveal recurring process issues.
  • Actionable Outputs: Produces a formatted retrospective with prioritized action items, owners, and deadlines and can save the report into the production documentation folder.
  • Use Case: After finishing sprint-7, run this Skill to generate a retrospective that highlights the top blocker, estimation variances, and 3 prioritized actions for the next sprint.

Quick Start

Invoke the retrospective skill for sprint-7 to analyze plans and commits, summarize metrics and blockers, and prompt to save the generated retrospective to production.

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

Generate a sprint retrospective by comparing milestone plan files in production/ against git commits to detect unplanned work, measure velocity, and surface recurring blockers. The analysis produces a formatted report with prioritized action items and owners.

Can I compare planned sprint tasks against actual git commits to find scope changes?▼

Yes, comparing planned sprint tasks against git commit history identifies carried-over work, scope changes, and unplanned additions. This plan-versus-reality analysis reveals estimation variances and highlights tasks that deviated from the original milestone scope.

How does velocity trend calculation work for game development milestones?▼

Velocity trend calculation works by analyzing completed work from milestone plans and commit history over multiple sprints. It measures completion rates, tracks velocity trends across iterations, and counts TODO, FIXME, and HACK markers to reveal recurring process issues.

Do I need sprint plan files in a specific directory to run a retrospective?▼

Yes, you need sprint or milestone plan files located in the production/ directory. The retrospective analysis reads these plans alongside git commit history for the covered period, and optionally writes the generated retrospective file back to production.

What's the best way to track technical debt and action items across game development sprints?▼

Track technical debt and action items by analyzing TODO, FIXME, and HACK counts in the codebase alongside sprint velocity data. The retrospective generates prioritized action items with owners and deadlines, following up on previous items to surface recurring issues.

Can the retrospective output be saved directly into the production documentation folder?▼

Yes, the retrospective output can be saved directly into the production documentation folder. With optional write permission, the generated report containing metrics, blockers, and prioritized actions is stored alongside your milestone plan files for future reference.

Related Skills

Explore More Product & Management Skills→
Euraika-LabsEuraika-Labs
14

retrospective

Generate sprint or milestone retrospectives from plans, git commits, and outcomes.

Official
Intermediate
MichaelSolatiMichaelSolati

retrospective

Compile and analyze sprint retrospective data from project artifacts into structured reports.

Community
Advanced
WindXRanWindXRan

retrospective

Generate sprint or milestone retrospectives from plans, completion status, and Git history.

Community
Intermediate
emcconnellemcconnell

retrospective

Generate structured Markdown retrospectives from sprint plans and git commit history.

Community
Advanced