skills.rest
packetalien
packetalienCOMMUNITY
Explore all skills by this author →
𝕏@packetmonkGitHub

retrospective

Analyze sprint and milestone data to generate a structured Markdown retrospective.

Updated Apr 25, 2026
Search Tags:#retrospective#blockers#agile#velocity#sprint#action-items
One-click install
npx skills add https://github.com/packetalien/cursor-game-studios --skill retrospective-packetalien
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/packetalien/cursor-game-studios/tree/main/.cursor/skills/retrospective
Command: npx skills add https://github.com/packetalien/cursor-game-studios --skill retrospective-packetalien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps Agile teams generate structured retrospectives by analyzing completed work, velocity trends, blockers, and patterns from project data, enabling actionable improvements for the next iteration.

Core Features & Use Cases

  • Analyze sprint and milestone data to produce a comprehensive retrospective with metrics, trends, and action items.
  • Compare planned versus actual work, identify carryovers, and surface recurring issues to inform process improvements.
  • Generate a ready-to-save Markdown retrospective document for production sprints or milestones.

Quick Start

Generate a sprint retrospective for sprint-42 using the latest git log and sprint plan.

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 logs and sprint artifacts?▼

Generate a sprint retrospective by analyzing git logs and sprint artifacts to produce a structured Markdown document containing metrics, velocity trends, blockers, and concrete action items for the next iteration.

What is a data-driven sprint retrospective?▼

A data-driven sprint retrospective analyzes completed work, velocity trends, and blockers from project data to identify recurring issues and generate actionable process improvements for the next iteration.

How do I compare planned versus actual work in an agile sprint?▼

Compare planned versus actual work by analyzing sprint and milestone data to identify carryovers, surface recurring issues, and produce a comprehensive retrospective with metrics and action items.

Can I use this to track velocity trends and blockers for my agile team?▼

Yes, it analyzes sprint and milestone data for agile teams to track velocity trends and blockers, outputting a ready-to-save Markdown retrospective document suitable for production sprints.

What is the best way to create a structured retrospective document for a milestone?▼

The best way to create a structured retrospective is by analyzing milestone data to produce a comprehensive Markdown document with metrics, trends, and concrete action items for process improvements.

Related Skills

Explore More Software Engineering Skills→
MichaelSolatiMichaelSolati

retrospective

Compile and analyze sprint retrospective data from project artifacts into structured reports.

Community
Advanced
JingyiWngJingyiWng

bmad-retrospective

Conduct post-epic retrospectives from story files and sprint-status.yaml.

Community
Advanced
emcconnellemcconnell

retrospective

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

Community
Advanced
xloxn69xloxn69
7

agileflow-retro-facilitator

Structure sprint retrospectives with feedback templates and SMART action items.

Community
Intermediate