retrospective

Generate sprint retrospectives from git logs and sprint plans.

10|2|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/wanghaisheng/OpenAgenticGame-Studios --skill retrospective-wanghaisheng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/wanghaisheng/OpenAgenticGame-Studios/tree/main/refenrece/skills/retrospective
Command: npx skills add https://github.com/wanghaisheng/OpenAgenticGame-Studios --skill retrospective-wanghaisheng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of generating comprehensive retrospectives by analyzing completed work, identifying blockers, and tracking trends, leading to actionable insights for continuous improvement.

Core Features & Use Cases

  • Automated Data Aggregation: Gathers data from git logs, sprint plans, and previous retrospectives.
  • Performance Analysis: Calculates metrics like completion rate, velocity trends, and estimation accuracy.
  • Actionable Insights: Identifies recurring issues, technical debt, and suggests specific improvements.
  • Use Case: After a two-week sprint, invoke this Skill with sprint-5 to automatically generate a detailed retrospective report, highlighting what went well, what didn't, and proposing concrete action items for the next sprint.

Quick Start

Generate a retrospective for sprint 3 by running retrospective skill with the argument sprint-3.

Frequently Asked Questions about retrospective

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

FAQPage Schema
How do I generate an automated sprint retrospective from git logs?

To generate a sprint retrospective, the Skill aggregates data from git logs, sprint plans, and previous retrospectives to analyze completed work, velocity, and blockers. Invoke it with a sprint identifier like `sprint-3` to produce a detailed report with actionable insights.

What is the best way to analyze team velocity and estimation accuracy after a milestone?

Analyzing team velocity and estimation accuracy is done by comparing planned versus actual tasks within the sprint. The Skill calculates these metrics alongside technical debt indicators to identify performance trends and formulate data-driven improvement recommendations.

Can I use this to track technical debt indicators across previous sprints?

Yes, you can track technical debt indicators by leveraging the Skill's automated data aggregation. It analyzes previous retrospectives and completed work to identify recurring issues and technical debt, suggesting specific improvements for continuous process enhancement.

How do I identify recurring blockers from our agile process data?

Identifying recurring blockers involves aggregating historical sprint data and analyzing patterns. The Skill processes previous retrospectives and sprint plans to pinpoint trends in completed work, helping your team recognize persistent issues and implement actionable process improvements.

Do I need to prepare sprint plans in a specific format for the retrospective analysis?

The Skill requires sprint plans, git logs, and previous retrospective data to perform its analysis. It aggregates these inputs to evaluate planned versus actual tasks, calculating completion rates and velocity trends to generate comprehensive retrospective insights.

What actionable insights can I expect from an automated agile retrospective?

An automated agile retrospective provides actionable insights by highlighting what went well, what didn't, and proposing concrete action items. It uses data-driven analysis of estimation accuracy, blockers, and technical debt to recommend specific improvements for the next sprint.