retrospective

Generate sprint or milestone retrospectives from plans, git commits, and outcomes.

14|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill retrospective-euraika-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/Euraika-Labs/Codex-Code-Game-Studios/tree/main/.agents/skills/retrospective
Command: npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill retrospective-euraika-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured, data-driven way to produce sprint or milestone retrospectives so teams can quickly understand completion, velocity, blockers, recurring issues, and create prioritized action items without manual aggregation.

Core Features & Use Cases

  • Automatic analysis: Compares planned tasks against commits and outcomes to identify completed, modified, carried-over, and unplanned work.
  • Trend and debt tracking: Counts TODO/FIXME/HACK trends and compares velocity and action-item follow-up against previous retrospectives.
  • Flexible input handling: Loads sprint plans from production/sprints/ or milestone definitions from production/milestones/, reads git logs for the period, and accepts manual data if files are missing.
  • Report generation & saving: Produces a comprehensive markdown retrospective with metrics, blockers, estimation accuracy, and action items, and can save it to production/retrospectives/ or production/sprints/ with user confirmation.
  • Real-world use: Ideal for engineering teams finishing a sprint who need a concise, evidence-backed retrospective and clear next-step assignments.

Quick Start

Generate a retrospective for sprint-12 using the sprint plan, git history for the sprint period, and past 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 commits and sprint plans?▼

Generate a sprint retrospective by loading sprint plans from production/sprints/, reading git logs for the sprint period, and comparing planned tasks against commits to output a markdown report with metrics and action items.

What is the best way to track technical debt and TODO/FIXME trends across sprints?▼

Track technical debt and TODO/FIXME/HACK trends by reading git commit history during the sprint period, counting occurrences, and comparing velocity and action-item follow-up against previous retrospectives to identify recurring issues.

Can I create a milestone retrospective if my milestone definition files are missing?▼

Yes, you can create a milestone retrospective without definition files. The tool loads milestone definitions from production/milestones/ but also accepts manual data input to analyze outcomes and generate the report.

Does the retrospective report include action items and estimation accuracy metrics?▼

Yes, the retrospective report includes estimation accuracy metrics, identified blockers, and prioritized action items by comparing planned tasks and owners against actual git activity and outcomes.

How do I save a retrospective report to my project repository?▼

Save a retrospective report by confirming the save action during generation, which writes the markdown file to production/retrospectives/ or production/sprints/ within your project directory.