skills.rest
pixel-cellar
pixel-cellarOFFICIAL
Explore all skills by this author →
GitHub

retrospective

Generates sprint and MBOs from tracked data and MBOs.

277|65|Updated Mar 30, 2026
Search Tags:#analysis#retrospective#agile#trends#sprint#actionable#milestone
One-click install
npx skills add https://github.com/pixel-cellar/Claude-Code-Game-Studios --skill retrospective-pixel-cellar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/pixel-cellar/Claude-Code-Game-Studios/tree/main/.claude/skills/retrospective
Command: npx skills add https://github.com/pixel-cellar/Claude-Code-Game-Studios --skill retrospective-pixel-cellar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams transform fragmented sprint outcomes into concrete, actionable retrospectives that guide the next iterations.

Core Features & Use Cases

  • Sprint and milestone retrospectives: Generate structured reviews from completed work, blockers, and velocity data.
  • Plan-vs-actual analysis: Compare planned tasks against delivered work using sprint/milestone definitions and git activity.
  • Trend and debt signals: Surface TODO/FIXME trends and recurring issues to prioritize improvements.
  • Output-ready reports: Produce a markdown retrospective with metrics, findings, and recommended actions.

Quick Start

Generate a retrospective for Sprint N or milestone name using the latest data from the production folders and summarize key insights.

Frequently Asked Questions about retrospective

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

FAQPage Schema
How do I generate an agile sprint retrospective from git logs and sprint plans?▼

To generate a sprint retrospective, the skill analyzes sprint plans, milestone definitions, and git repository activity to compare planned versus actual work, extracting trend insights into a markdown report.

What's the best way to compare planned vs actual work for a completed milestone?▼

Comparing planned versus actual milestone work involves parsing production/milestones definitions and reading git logs for the specified time window to surface delivered tasks and actionable metrics.

Can I track TODO and FIXME code trends during a sprint retrospective?▼

Yes, you can track TODO and FIXME trends during a sprint retrospective; the skill scans code repository activity to surface technical debt signals and recurring issues to prioritize improvements.

What data do I need to produce an actionable retrospective with metrics and next actions?▼

Producing an actionable retrospective requires sprint plans, milestone definitions, and code repository git logs, which are parsed to output a markdown retrospective with metrics, findings, and recommended next actions.

Does this work for both sprint-level and milestone-level workflow analysis?▼

Yes, this workflow analysis applies to both sprint-level and milestone-level workflows, reading production/sprints and production/milestones definitions to compare planned tasks against delivered work.

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
tarunccettarunccet
5

retro

Converts team feedback and sprint metrics into a markdown retro with prioritized action items.

Community
Intermediate
MichaelSolatiMichaelSolati

retrospective

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

Community
Advanced
akillnessakillness
40

sprint-retrospective

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

Community
Intermediate