retrospective

Name: retrospective
Availability: InStock
Author: easonlao

Generate sprint retrospectives from plan files and git history.

Updated Apr 25, 2026

Search Tags:#retrospective #technical debt #sprint planning #action items #git log #velocity trend #blocker analysis

Ready to run

npx skills add https://github.com/easonlao/jiazi-game --skill retrospective-easonlao

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/easonlao/jiazi-game/tree/main/.claude/skills/retrospective
Command: npx skills add https://github.com/easonlao/jiazi-game --skill retrospective-easonlao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the guesswork of retrospectives by analyzing what was planned versus what was actually delivered, surfacing blockers and recurring patterns, and converting them into concrete improvements for the next iteration.

Core Features & Use Cases

Sprint/milestone retrospective generation: Builds a complete retrospective covering metrics, velocity trend, blockers, carryovers, technical debt signals, and summary.
Data-driven analysis: Compares plan files and commit history, and inspects TODO/FIXME/HACK trends to identify systemic issues.
Actionable output: Produces a focused set of prioritized next-iteration action items with owners and deadlines, then saves the result to the appropriate production path.

Quick Start

Run the retrospective skill for sprint 5 by saying: retrospective sprint-5.

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 planned work?▼

To generate a sprint retrospective, the skill compares your plan files against actual git commit history to analyze completion, velocity trends, and blockers, producing actionable next steps with owners and deadlines.

What is the best way to track technical debt signals during a sprint post-mortem?▼

Tracking technical debt signals during a sprint post-mortem involves scanning your codebase for trends in TODO, FIXME, and HACK counts to identify systemic issues and inform actionable improvements for the next iteration.

Can I merge an existing retrospective file with new sprint data?▼

Yes, you can merge an existing retrospective file with new sprint data by parsing arguments and optionally merging the current analysis with prior records before saving the final markdown output to the correct production path.

Does sprint planning analysis support engineering teams needing measurable, non-blaming insights?▼

Sprint planning analysis supports engineering teams by comparing planned work against actual delivery to surface blockers and recurring patterns, converting them into measurable, non-blaming insights for continuous improvement.

How do I assign owners and deadlines to action items after a milestone retrospective?▼

To assign owners and deadlines to action items after a milestone retrospective, the skill produces a focused set of prioritized next-iteration tasks extracted from git history and blocker analysis, ensuring clear accountability.

What should I do if my sprint retrospective is not capturing carryover work accurately?▼

If your sprint retrospective is not capturing carryover work accurately, verify that the skill is correctly parsing your plan files and scanning git log history to compare planned versus actual delivered work.