retrospective

Generates a sprint or milestone retrospective from git history and prior retrospectives.

72|7|Updated Apr 29, 2026

Search Tags:#retrospective #blockers #action items #velocity #git log #sprint analysis

Ready to run

npx skills add https://github.com/striderZA/OpenCodeGameStudios --skill retrospective-striderza

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/striderZA/OpenCodeGameStudios/tree/main/.opencode/skills/retrospective
Command: npx skills add https://github.com/striderZA/OpenCodeGameStudios --skill retrospective-striderza

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Retrospective planning often turns into vague discussion instead of evidence-based improvements, leaving teams unclear on what to fix next and how to prevent repeats.

Core Features & Use Cases

Sprint/milestone retrospective generation: Produces a structured retrospective by analyzing planned vs actual work, velocity, blockers, and recurring patterns.
Data-backed insights from repo history: Uses git log to infer what was actually committed during the period and highlights trends via previous retrospectives.
Action items with ownership and deadlines: Produces a focused set of 3–5 measurable next-iteration actions, each with an owner and deadline.

Quick Start

Use the retrospective skill to generate a sprint retrospective for sprint 5 by running: /retrospective sprint-5.

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

A sprint retrospective uses git log data to analyze actual commits against planned work, evaluating velocity and blockers. This process generates a structured retrospective file with 3-5 measurable action items, including owners and deadlines for the next iteration.

What is the best way to turn sprint analysis results into action items?▼

Turning sprint analysis into action items requires evaluating planned versus actual velocity, blockers, and recurring patterns. This produces 3 to 5 measurable next-iteration actions, each with a designated owner and deadline for continuous improvement.

Can I use this for milestone evaluations in game development lifecycles?▼

Yes, milestone retrospectives work for both game and software development lifecycles. The skill evaluates completed work, velocity, and blockers to recommend actionable improvements, requiring only a milestone identifier to parse and analyze.

How does a retrospective identify recurring blockers from previous sprints?▼

A retrospective identifies recurring blockers by optionally loading existing retrospective content to highlight historical trends. It compares current sprint blockers against previous patterns to recommend evidence-based preventative actions.

Do I need to manually write the retrospective file after the sprint analysis?▼

No, manual writing is unnecessary. After presenting key findings and requesting confirmation, the skill automatically writes a finalized retrospective file containing the sprint analysis, blockers, and action items.