skills.rest
LordKuper
LordKuperCOMMUNITY
Explore all skills by this author →
GitHub

retrospective

Generate structured markdown sprint retrospectives from git history and project data.

Updated Mar 26, 2026
Search Tags:#retrospective#blockers#agile#velocity#sprint#team-learning#action-items
One-click install
npx skills add https://github.com/LordKuper/agentic-game-studio --skill retrospective-lordkuper
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/LordKuper/agentic-game-studio/tree/main/.claude/skills/retrospective
Command: npx skills add https://github.com/LordKuper/agentic-game-studio --skill retrospective-lordkuper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

An automated, data-driven way to generate sprint or milestone retrospectives from project activity, helping teams surface actionable improvements without manual synthesis.

Core Features & Use Cases

  • Analyze completed work, velocity, blockers, and patterns to generate structured insights.
  • Compare planned vs actual work, track TODO/FIXME trends, and surface recurring issues.
  • Use Case: A team runs a sprint; the skill analyzes git history and task data to produce a concise retrospective with concrete actions.

Quick Start

Generate a data-driven retrospective for the specified sprint or milestone using the latest project activity.

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 project data?▼

To generate a sprint retrospective, the skill analyzes git history and task data from .ags/project directories to compare planned work against actual completed work, tracking velocity and blockers to produce a structured markdown report.

What is a data-driven agile retrospective and how does it surface blockers?▼

A data-driven agile retrospective analyzes completed work, velocity metrics, and historical blockers to identify recurring patterns. It compares planned versus actual sprint outcomes to surface actionable improvements for the team.

Can I use this skill for milestone reviews instead of regular sprint planning?▼

Yes, you can use this skill for milestone reviews. It applies to both sprint planning and milestone reviews by parsing milestone data, tracking TODO/FIXME trends, and comparing plans to reality to generate structured insights.

What's the best way to track recurring blockers and velocity trends across sprints?▼

The best way to track recurring blockers and velocity trends is by analyzing completed work and historical patterns from git history. This surfaces recurring issues and compares planned versus actual work to generate actionable improvements.

Does this automated retrospective tool require any external dependencies?▼

No, this automated retrospective tool requires no external dependencies. It directly reads project activity and sprint data from local .ags/project directories and git history to ground its insights without needing additional packages.

What sections are included in the structured markdown retrospective output?▼

The structured markdown retrospective output includes dedicated sections for what went well, what went poorly, identified blockers, and next actions. These sections are generated by parsing sprint data and comparing plans to reality.

Related Skills

Explore More Software Engineering Skills→
LordKuperLordKuper

milestone-review

Generates milestone progress reviews with quality metrics and go/no-go recommendations.

Community
Advanced
brand6brand6

retrospective

Extract sprint data into a structured markdown retrospective with actionable improvements.

Community
Advanced
imgamerimgamer

retrospective

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

Community
Advanced
legioncodeinclegioncodeinc
72

retrospective-stinger

Convert team feedback sessions into structured behavior-change workflows.

Official
Advanced