retrospective

Generates structured sprint or milestone retrospectives from plans, git history, and blockers.

Updated Mar 15, 2026

Search Tags:#automation #retrospective #agile #velocity #sprint #action-items

Ready to run

npx skills add https://github.com/jtvaris/sunday-night-dynasty --skill retrospective-jtvaris

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/jtvaris/sunday-night-dynasty/tree/main/.agents/skills/retrospective
Command: npx skills add https://github.com/jtvaris/sunday-night-dynasty --skill retrospective-jtvaris

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams generate structured sprint or milestone retrospectives by analyzing planned work, actual delivery, blockers, and emerging patterns to yield concrete improvements for the next iteration.

Core Features & Use Cases

Automated retrospective generation for sprints or milestones by comparing plans to actual delivery and highlighting variances.
Historical context and debt awareness by scanning previous retrospectives and codebase trends (TODO/FIXME/HACK) to surface recurring issues.
Actionable outcomes with ownership and deadlines, plus a velocity trend overview to inform process improvements.
Cross-repo integration by reading sprint plans from production/sprints and milestone definitions from production/milestones to provide a holistic view.

Quick Start

Invoke the skill with a sprint number (e.g., sprint-3) or a milestone name to generate the retrospective.

Frequently Asked Questions about retrospective

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate an automated sprint retrospective from git history and sprint plans?▼

An automated sprint retrospective is generated by comparing planned work from production/sprints against actual git history delivery to surface variances and actionable insights. It analyzes planned work, blockers, and emerging patterns to yield concrete improvements.

Can I generate a milestone retrospective instead of a standard sprint retrospective?▼

Yes, you can generate a milestone retrospective by invoking the skill with a milestone name. It reads milestone definitions from production/milestones and analyzes actual delivery to provide a holistic cross-repo view of progress and variances.

What is the best way to track recurring codebase issues like technical debt during an agile retrospective?▼

The best way to track recurring technical debt during an agile retrospective is scanning prior retrospectives alongside git history for TODO, FIXME, and HACK tags. This surfaces recurring issues and historical context to inform concrete process improvements.

Does this retrospective tool provide velocity trends and assign action item ownership?▼

Yes, the retrospective tool provides a velocity trend overview and generates actionable outcomes with assigned ownership and deadlines. This ensures concrete improvements are tracked and process adjustments are informed by delivery metrics.

How do I start a retrospective for a specific sprint number?▼

To start a retrospective for a specific sprint, invoke the skill with the sprint number like sprint-3. The skill then reads the corresponding sprint plans, analyzes git history, and outputs a structured Markdown report with metrics and action items.