retrospective

Name: retrospective
Availability: InStock
Author: NuoYan

Analyze sprint data to produce a retrospective with actionable improvement items.

47|12|Updated Jun 14, 2026

Search Tags:#retrospective #technical debt #action planning #velocity tracking #sprint analysis #milestone review #blocker analysis

Ready to run

npx skills add https://github.com/nuoyanruoshui/GodotGameFramework --skill retrospective-nuoyanruoshui

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/nuoyanruoshui/GodotGameFramework/tree/main/Godot/.claude/skills/retrospective
Command: npx skills add https://github.com/nuoyanruoshui/GodotGameFramework --skill retrospective-nuoyanruoshui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill transforms scattered sprint or milestone data into a structured retrospective, revealing delivery gaps, recurring blockers, estimation issues, technical debt trends, and concrete improvements for the next iteration.

Core Features & Use Cases

Completion Analysis: Compare planned work with completed, modified, carried-over, descoped, and unplanned tasks.
Trend Evaluation: Analyze velocity, git activity, technical debt markers, blockers, estimation accuracy, and previous action items.
Action Planning: Produce prioritized, owner-assigned, deadline-based action items and process improvements.
Use Case: After a sprint ends, use this Skill to review the sprint plan, authoritative status data, commit history, and prior retrospectives, then create a data-backed report for the team.

Quick Start

Use the retrospective skill to analyze sprint-12 and prepare an actionable retrospective from the available project data.

Frequently Asked Questions about retrospective

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

FAQPage Schema

How do I generate a data-backed sprint retrospective from project plans and git history?▼

To generate a sprint retrospective, analyze completed sprint plans, authoritative status data, git commit history, and prior retrospectives to produce a structured report with actionable improvement items. The analysis requires user approval before saving the final retrospective.

What is the best way to track technical debt and recurring blockers across delivery milestones?▼

Tracking technical debt and recurring blockers involves evaluating delivery trends, velocity data, and git activity across milestone reviews. This process identifies estimation accuracy issues and recurring delivery gaps, transforming them into prioritized, owner-assigned action items.

How do I analyze sprint completion data to identify carried-over and unplanned tasks?▼

Sprint completion analysis compares planned work with completed, modified, carried-over, descoped, and unplanned tasks. By reviewing project plans and status data, the analysis reveals delivery gaps and estimation issues for the next iteration.

Can I use sprint velocity tracking to improve estimation accuracy for future iterations?▼

Sprint velocity tracking improves estimation accuracy by evaluating delivery trends against prior retrospectives and git activity. This analysis identifies estimation discrepancies and produces concrete process improvements assigned to specific owners with deadlines.

Do I need prior retrospective reports to run a milestone review and blocker analysis?▼

Prior retrospective reports are required to run a milestone review and blocker analysis. The evaluation combines previous action items, project plans, status data, and git history to assess delivery trends and generate new actionable improvements.