skills.rest
thilthpc01208
thilthpc01208COMMUNITY
Explore all skills by this author →
GitHub

retrospective

Generate structured markdown sprint and milestone retrospectives from production data.

Updated Aug 27, 2026
Search Tags:#retrospective#blockers#agile#velocity#sprint#process-improvement#action-items
One-click install
npx skills add https://github.com/thilthpc01208/Codex-Game-Studios --skill retrospective-thilthpc01208
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/thilthpc01208/Codex-Game-Studios/tree/main/.codex/skills/retrospective
Command: npx skills add https://github.com/thilthpc01208/Codex-Game-Studios --skill retrospective-thilthpc01208

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sprint retrospectives are often manual and inconsistent. This skill automates the generation of structured, data-driven retrospectives by analyzing completed work, velocity, blockers, and patterns to produce actionable insights for the next iteration.

Core Features & Use Cases

  • Phase-based analysis of sprint or milestone data, including planned vs actual work, outcomes, and trends.
  • Velocity and trend analysis, blockers tracking, carryover identification, and technical debt signals.
  • Reuse of previous retrospectives to assess progress and inform future actions.

Quick Start

Load sprint or milestone data, generate a retrospective with insights and action items, and save it to the appropriate production path (e.g., production/sprints/sprint-<N>-retrospective.md or production/milestones/milestone-<name>-retrospective.md).

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

Generate a sprint retrospective by loading completed work data to analyze velocity, blockers, and technical debt, producing a structured markdown file with metrics, carryover, and action items.

What is the best way to track blockers and carryover across sprint cycles?▼

Track blockers and carryover by analyzing completed work and velocity trends, reading previous retrospectives to identify recurring patterns, and generating data-driven action items for the next iteration.

Can I analyze planned versus actual delivery for milestone reviews?▼

Yes, you analyze planned versus actual delivery for milestone reviews by loading milestone data to evaluate outcomes, velocity, and technical debt, outputting a formatted retrospective with metrics and action items.

Does this retrospective process require previous sprint reports to work?▼

The retrospective process reads previous retrospectives to assess progress and inform future actions, but the core analysis of completed work, velocity, and blockers can still generate insights without them.

How do I save and format action items from a sprint retrospective?▼

Save and format action items by outputting a formatted markdown file to the appropriate production path, such as production/sprints/sprint-N-retrospective.md, containing metrics, blockers, and action items.

Related Skills

Explore More Software Engineering Skills→
XGanQAQXGanQAQ
1

retrospective

Generate structured markdown sprint retrospectives from git history and plan data.

Community
Intermediate
scomofoscomofo

retrospective

Generate sprint or milestone retrospectives from plans, status, and git history.

Community
Advanced
semicolon-devteamsemicolon-devteam

close-sprint

Automates sprint closure, velocity calculation, retrospective generation, task migration, and label removal for Iterations.

Official
Intermediate
mcauduro0mcauduro0
1

scrum-master

Analyze sprint data with Monte Carlo simulations to forecast velocity and team health.

Community
Advanced