skills.rest
imclab
imclabOFFICIAL
Explore all skills by this author →
Website𝕏@TheIMCLabGitHub

retrospective

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents your sprint or milestone team from repeating the same issues by turning completed work into a data-backed retrospective and concrete next-iteration actions.

Core Features & Use Cases

  • Sprint/milestone retrospective generation: Produces a structured retrospective for either a sprint or a milestone using plan vs. actuals.
  • Velocity, completion, and carryover analysis: Compares planned vs. actual tasks and effort, detects carryover items, and summarizes trend changes.
  • Blockers, technical debt signals, and follow-up: Identifies blockers, evaluates TODO/FIXME/HACK trends, and carries forward prior action items into measurable status updates.
  • Use Case: After finishing a two-week sprint, generate a retrospective that highlights what went well, what failed against estimates, what caused delays, and the 3–5 most important next actions with owners and deadlines.

Quick Start

Run the retrospective skill with sprint 14 by invoking it as: retrospective sprint-14.

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

Generate a sprint retrospective by parsing plan files and git history to compare planned tasks against actual commits. This computes velocity trends and identifies blockers, producing a structured retrospective artifact for the milestone.

What is the best way to track technical debt signals across completed sprints?▼

Track technical debt signals by evaluating TODO, FIXME, and HACK trends within the codebase during the retrospective. This identifies recurring patterns and generates follow-up action items with assigned owners to resolve the technical debt.

Can I analyze carryover tasks and velocity trends for milestone planning?▼

Yes, analyze carryover tasks by comparing planned effort estimates against actual delivered outcomes. The retrospective computes completion metrics and summarizes velocity trend changes to inform your next sprint planning.

How do I extract blocker analysis and action items from a completed iteration?▼

Extract blocker analysis by comparing planned goals against actual delivered commits to identify what caused delays. The process generates three to five concrete action items with owners and deadlines to prevent recurring sprint issues.

Do I need prior retrospective artifacts to analyze sprint velocity and completion?▼

No, the process locates or initializes retrospective artifacts automatically if none exist. It reads plan files and git history to compute current metrics while carrying forward prior action items into measurable status updates.

Related Skills

Explore More Product & Management Skills→
polsegupolsegu

retrospective

Generate sprint retrospectives by comparing plans against git commit history.

Community
Advanced
akillnessakillness
40

sprint-retrospective

Facilitate structured sprint retrospectives with Start-Stop-Continue, Mad-Sad-Glad, or 4Ls templates.

Community
Intermediate
jtvarisjtvaris

sprint-plan

Generate sprint plans from milestones, velocity, and design backlog.

Community
Intermediate
jasonmichaelbell78-creatorjasonmichaelbell78-creator

add-debt

Append a debt item to .planning/DEBT_LOG.md as a markdown table row.

Community
Basic