retrospective

Generates sprint or milestone retrospectives from completion data, velocity trends, and blockers.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill retrospective-claretagrapelike32
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/claretagrapelike32/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/retrospective
Command: npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill retrospective-claretagrapelike32

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often skip retrospectives or produce vague notes because gathering sprint data, computing velocity, and tracking recurring blockers is tedious manual work. This Skill automates that analysis and produces a structured, data-backed retrospective document. ## Core Features & Use Cases - Automated Data Collection: Reads sprint plans, milestone definitions, sprint-status YAML, and git history to reconstruct what actually happened during the iteration. - Trend and Debt Analysis: Computes completion rates, velocity trends across sprints, estimation accuracy, and TODO/FIXME/HACK technical debt counts compared to previous retrospectives. - Actionable Output: Generates a structured markdown retrospective with metrics tables, blocker analysis, carryover tracking, and owned action items with deadlines, saved to production/retrospectives/. - Use Case: After finishing sprint 12, run the Skill to analyze the sprint plan against git commits and sprint-status.yaml, then produce a retrospective showing a 78% completion rate, a growing FIXME trend, and three prioritized action items for sprint 13 planning. ## Quick Start Ask the AI to generate a retrospective for sprint 12 using the sprint plan, sprint-status.yaml, and recent git history, then save it to production/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 automatically?

Run the retrospective Skill with a sprint identifier like sprint-12. It reads the sprint plan, sprint-status.yaml, and git log for the period, then produces a markdown retrospective with completion metrics, velocity trends, and action items saved to production/retrospectives/.

How to track velocity trends across multiple sprints?

The Skill reads previous retrospectives from production/retrospectives/ and builds a velocity table comparing planned versus completed tasks across recent sprints. It labels the trend as increasing, stable, or decreasing with a one-sentence explanation.

What happens if no sprint data exists for the retrospective?

The Skill reports that no sprint data was found and offers two options: provide the sprint tasks, dates, and outcomes manually as the source of truth, or abort with a BLOCKED verdict. It suggests running sprint-status first to generate the data.

Can I update an existing retrospective instead of creating a new one?

Yes. The Skill globs for existing retrospective files matching the sprint or milestone slug before starting. You can choose to update the existing file with new data or archive it with a date suffix and start fresh.

Does the retrospective track technical debt over time?

Yes. It counts TODO, FIXME, and HACK comments in the codebase and compares them against counts recorded in previous retrospectives, reporting whether technical debt is growing, stable, or shrinking.