retrospective

Compile and analyze sprint retrospective data from project artifacts into structured reports.

Updated Jul 22, 2025
One-click install
npx skills add https://github.com/MichaelSolati/mkai --skill retrospective-michaelsolati
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/MichaelSolati/mkai/tree/main/profiles/game-dev/skills/retrospective
Command: npx skills add https://github.com/MichaelSolati/mkai --skill retrospective-michaelsolati

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually compiling sprint and milestone retrospectives from scattered project data (sprint plans, git logs, past reports) is time-consuming, inconsistent, and often misses key trends, recurring blockers, and actionable improvement opportunities.

Core Features & Use Cases

  • Automated Data Aggregation: Cross-references sprint plans, milestone definitions, git commit history, and past retrospectives to pull all relevant project data without manual copying.
  • Structured Insight Generation: Produces standardized retrospective reports with key metrics (completion rate, velocity, estimation accuracy), trend analysis, and prioritized action items.
  • Use Case: For a 2-week engineering sprint, use this skill to automatically calculate completion rates, identify the top blocker that delayed feature delivery, and generate a report the team can use to adjust estimation practices for the next iteration.

Quick Start

Use the retrospective skill to generate a structured retrospective report for your team's most recently completed sprint or milestone.

Frequently Asked Questions about retrospective

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

FAQPage Schema
How do I automate sprint retrospective data aggregation from git commits and sprint plans?

Automating sprint retrospective data aggregation cross-references sprint plans, milestone definitions, git commit history, and past retrospectives to pull relevant project data. This eliminates manual copying and ensures consistent data compilation for analysis.

What metrics are included in an automated agile retrospective report?

An automated agile retrospective report includes key metrics such as completion rate, velocity trends, and estimation accuracy. It also analyzes technical debt shifts and recurring blockers to generate prioritized action items for future iterations.

Can I generate milestone-based retrospective analysis for agile teams?

Yes, you can generate milestone-based retrospective analysis for agile software development teams running time-boxed sprints or milestone-based workflows. The analysis identifies completion trends, recurring blockers, and process improvement recommendations.

How do I identify recurring blockers and technical debt shifts across sprints?

Identifying recurring blockers and technical debt shifts across sprints requires analyzing historical sprint data and past retrospective documents. Automated compilation tracks these patterns over time to highlight estimation gaps and prioritize process improvements.

Does this approach to retrospective reporting require specific project management tools?

No specific project management tools are required as dependencies. The approach works by compiling and analyzing data from scattered project artifacts like sprint plans and git commit history to generate structured, actionable retrospective reports.