skills.rest
WindXRan
WindXRanCOMMUNITY
Explore all skills by this author →
GitHub

retrospective

Generate sprint or milestone retrospectives from plans, completion status, and Git history.

Updated Apr 4, 2026
Search Tags:#retrospective#blockers#process improvement#action items#velocity tracking#git log#sprint analysis
One-click install
npx skills add https://github.com/WindXRan/y3td --skill retrospective-windxran
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/WindXRan/y3td/tree/main/.claude/skills/retrospective
Command: npx skills add https://github.com/WindXRan/y3td --skill retrospective-windxran

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the effort and guesswork of writing sprint or milestone retrospectives by turning plans, completion status, and code-trend signals into a structured, actionable document.

Core Features & Use Cases

  • Retrospective generation from real sprint/milestone data: Synthesizes planned work, actual completion status (including production/sprint-status.yaml when available), and Git history into metrics and conclusions.
  • Trend and process insight extraction: Compares TODO/FIXME/HACK counts and reviews previous retrospectives to identify recurring issues and velocity shifts.
  • Actionable next-iteration outputs: Produces focused action items with owners and deadlines, then saves the result to production/retrospectives/ after explicit confirmation.

Quick Start

Run the retrospective skill for sprint 5 by providing the argument sprint-5, then review the generated document and choose whether to write it to production/retrospectives.

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

To generate a sprint retrospective, the Skill parses planned work from sprint or milestone folders, computes completion metrics from sprint-status.yaml, scans TODO/FIXME/HACK trends, and reviews Git history to produce actionable insights. Output is saved to production/retrospectives/ after explicit user confirmation.

What is velocity tracking and how does it work for milestone analysis?▼

Velocity tracking for milestone analysis works by computing completion and variance metrics from your planned work and actual sprint-status.yaml data. It compares these metrics against previous retrospectives to identify velocity shifts and recurring blockers, generating focused action items for the next iteration.

Can I use sprint-status.yaml to track process improvement and blockers?▼

Yes, you can use sprint-status.yaml to track process improvement and blockers. The Skill parses this optional file to compute actual completion facts, compares them against planned work, and scans TODO/FIXME/HACK trends to identify recurring issues that require process improvements.

How to extract action items from recurring patterns in previous retrospectives?▼

Extracting action items from recurring patterns requires parsing existing retrospectives alongside current sprint data. The Skill identifies recurring blockers and velocity shifts by comparing historical documents with current TODO/FIXME/HACK trends, then produces focused action items with owners and deadlines for the next iteration.

Does this retrospective generation work with milestone workflows or only sprints?▼

This retrospective generation works with both milestone and sprint workflows. It applies to workflows maintaining plans under production/sprints and production/milestones, optionally reading completion facts from production/sprint-status.yaml to analyze completed work and generate actionable improvements.

What are the limitations of automated sprint analysis for next-iteration improvements?▼

Automated sprint analysis requires maintaining plans under production/sprints or production/milestones and optionally completion facts in production/sprint-status.yaml. It cannot generate improvements without existing Git history or planned work data, and saving output requires explicit user approval before writing to production/retrospectives/.

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
akillnessakillness
40

sprint-retrospective

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

Community
Intermediate
FrancisVargaFrancisVarga

retrospective

Generate sprint or milestone retrospectives from plans, status, and git history.

Community
Advanced
scomofoscomofo

retrospective

Generate sprint or milestone retrospectives from plans, status, and git history.

Community
Advanced