skills.rest
dnkrow
dnkrowCOMMUNITY
Explore all skills by this author →
GitHub

retrospective

Generate sprint or milestone retrospectives from git history and plan files.

1|Updated May 15, 2026
Search Tags:#retrospective#technical debt#velocity analysis#sprint planning#action items#git log#project metrics
One-click install
npx skills add https://github.com/dnkrow/skill --skill retrospective-dnkrow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/dnkrow/skill/tree/main/claude-global/retrospective
Command: npx skills add https://github.com/dnkrow/skill --skill retrospective-dnkrow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams turn messy sprint and milestone outcomes into a structured retrospective with clear metrics, trends, blockers, and concrete next actions.

Core Features & Use Cases

  • Sprint/milestone retrospective generation: Uses planned work (from plan files) and actual work (from git history) to produce a data-backed retrospective.
  • Existing retrospective update vs regenerate: Detects prior retrospectives for the same period and lets you update sections or start fresh with archiving.
  • Carryover, technical-debt, and follow-up analysis: Compares plan vs deliverables, checks TODO/FIXME trends, and verifies whether previous action items were completed.

Quick Start

Run the retrospective skill for a sprint by providing the argument sprint-3 to generate a retrospective using the relevant plan files and the last two weeks of git 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 using git log history and plan files?▼

To generate a sprint retrospective, provide a sprint identifier as an argument to parse planned tasks and inspect git log history for the period. The skill compares plan definitions against actual delivery evidence to output metrics, velocity trends, and action items to a production file path.

Can I update an existing retrospective instead of regenerating it completely?▼

Yes, the skill detects prior retrospectives for the same sprint period by file globbing. You can choose to update specific sections of the existing retrospective or start fresh by archiving the old file and generating a new one.

How does technical debt analysis work when reviewing sprint deliverables?▼

Technical debt analysis works by comparing planned work against actual git history deliverables and checking TODO and FIXME trends in the codebase. This identifies carryover work and verifies whether action items from previous sprints were completed.

What inputs do I need to run a milestone readiness check with velocity analysis?▼

You need YAML frontmatter inputs containing plan definitions and a milestone or sprint identifier argument. The skill uses these inputs alongside git log inspection for the specified period to calculate project metrics and velocity trends for the milestone readiness check.

Does this skill work for both sprint planning and milestone retrospectives?▼

Yes, the skill applies to both sprint-status workflows and milestone readiness checks. It uses the same mechanism of comparing plan files against git history to produce structured retrospectives with metrics, blockers, and next action items for either context.

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
sumilee-pcusumilee-pcu

retrospective

Correlate git commit history with planned tasks to generate structured retrospective reports.

Community
Advanced
emcconnellemcconnell

retrospective

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

Community
Advanced
solace-illsolace-ill

retrospective

Generate markdown retrospectives from sprint data and git history.

Community
Advanced