retrospective

Name: retrospective
Availability: InStock
Author: wsman

Analyze sprint artifacts and git logs to generate retrospective reports.

18|5|Updated Nov 25, 2025

Search Tags:#retrospective #blockers #action items #velocity #sprint #milestone #git log

Ready to run

npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill retrospective-wsman

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/wsman/MY-DOGE-MICRO/tree/main/.agents/skills/retrospective
Command: npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill retrospective-wsman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns completed sprint or milestone work into a clear retrospective, so teams can understand what shipped, what slipped, what blocked progress, and what to change next.

Core Features & Use Cases

Analyzes planned work against actual commits and deliverables to measure completion, carryover, and scope changes.
Reviews blockers, estimation accuracy, velocity trends, and technical-debt signals such as TODO and FIXME patterns.
Produces action items and process improvements for the next iteration, making it useful for sprint closeouts, milestone reviews, and engineering process audits.

Quick Start

Ask the retrospective skill to analyze sprint 5 and draft a retrospective with metrics, blockers, trends, and next-step actions.

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 and commit history?▼

Sprint retrospective analysis compares planned tasks against actual git log commits and repository artifacts. This process produces completion metrics, carryover analysis, estimation accuracy, and actionable recommendations for the next iteration.

What is included in a milestone retrospective report for engineering teams?▼

A milestone retrospective report includes completion metrics, carryover analysis, scope changes, blocker reviews, and velocity trends. It also evaluates estimation accuracy and identifies technical-debt signals by analyzing TODO and FIXME patterns in the codebase.

Can I analyze estimation accuracy and velocity trends from prior sprint artifacts?▼

Yes, you can analyze estimation accuracy and velocity trends by comparing prior sprint artifacts and planned work against actual deliverables. This requires reading project plans and prior retrospectives to measure performance and identify process improvements.

Does the retrospective analysis detect technical-debt signals like TODO and FIXME comments?▼

Yes, retrospective analysis detects technical-debt signals by scanning for TODO and FIXME patterns in the repository. It reviews these code-comment trends alongside blockers and velocity metrics to recommend process improvements for the next iteration.

What's the best way to identify blockers and carryover tasks for a sprint closeout?▼

The best way to identify blockers and carryover is analyzing completed sprint work against actual commits and deliverables. This comparison measures completion, reveals scope changes, and produces actionable next-iteration recommendations for sprint closeouts.

Do I need project plans and prior retrospectives to generate engineering process audits?▼

Yes, generating engineering process audits requires reading project plans, git logs, and prior retrospectives. Comparing these planned tasks against actual delivery provides the metrics and carryover analysis needed for actionable audit results.