retrospective

Analyze sprint and milestone data to generate structured retrospective reports.

Updated Apr 8, 2026

Search Tags:#planning #retrospective #blockers #engineering #velocity #sprint #action-items

Ready to run

npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill retrospective-hechaoyannet

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/HechaoYannet/3kingdom-unity/tree/main/.claude/skills/retrospective
Command: npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill retrospective-hechaoyannet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineering and project teams quickly generate structured retrospectives by analyzing completed work, velocity, blockers, and patterns. It translates raw sprint/milestone data into actionable insights that inform next steps and process improvements.

Core Features & Use Cases

Phase-based analysis of planned vs. actual work, blockers, and completion rates.
Velocity trend assessment and carryover identification to guide planning.
Generation of concrete action items, risk flags, and improvement recommendations based on historical data.

Quick Start

Provide sprint N or milestone-name data to generate a ready-to-review retrospective.

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 report from planned tasks and actual commits?▼

To generate a sprint retrospective report, analyze completed work by comparing planned tasks against actual commits, velocity trends, and blockers to produce actionable insights and improvement recommendations.

What is the best way to identify blockers and technical debt trends during a milestone review?▼

Identifying blockers and technical debt trends during a milestone review involves processing milestone data to compare planned versus actual work, highlighting risk flags and referencing historical retrospectives for patterns.

Can I use this retrospective process for both sprint planning cycles and milestone reviews?▼

Yes, the retrospective process applies to both sprint planning cycles and milestone reviews, reading data from production sprints and production milestones to assess completion rates and generate action items.

How does velocity trend assessment and carryover identification work for sprint planning?▼

Velocity trend assessment and carryover identification work by evaluating actual sprint data against planned work, analyzing completion rates to guide future planning and flagging risks based on historical retrospective data.

What data do I need to provide to generate concrete action items and risk flags for engineering projects?▼

To generate concrete action items and risk flags, you need to provide sprint or milestone data, which is then processed to compare planned versus actual work, evaluate velocity trends, and identify blockers.