retrospective

Generate structured sprint and milestone retrospectives from velocity and blocker data.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/johnatas-henrique/overdrive --skill retrospective-johnatas-henrique
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/johnatas-henrique/overdrive/tree/main/.opencode/skills/retrospective
Command: npx skills add https://github.com/johnatas-henrique/overdrive --skill retrospective-johnatas-henrique

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to translate completed sprint or milestone work into meaningful, actionable insights, leading to repeated process mistakes and unaddressed bottlenecks that slow down future work.

Core Features & Use Cases

  • Structured Retrospective Generation: Automatically compiles metrics like completion rate, velocity, and blocker data into a standardized retrospective format.
  • Dual Workflow Support: Handles both sprint-level and milestone-level retrospectives, with checks for existing files to avoid duplicate work.
  • Use Case: After finishing a 2-week feature sprint, use this skill to pull sprint plan data, git commit history, and TODO counts to produce a full retrospective with estimation accuracy analysis and prioritized action items.

Quick Start

Use the retrospective skill to generate a retrospective for the latest completed sprint.

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 retrospective from completed sprint work?

To generate an agile retrospective, this skill analyzes completed sprint work, velocity metrics, and blocker data to produce a structured retrospective with estimation accuracy analysis and prioritized action items.

What is the best way to analyze sprint velocity and estimation accuracy?

The best way to analyze sprint velocity is by pulling sprint plan data and TODO counts to calculate estimation accuracy, identify recurring team patterns, and highlight bottlenecks that slow down future work.

Can I run a retrospective for milestone-based project phases instead of time-boxed sprints?

Yes, you can run a retrospective for milestone-based project phases. This skill supports dual workflows, automatically adapting its analysis for both time-boxed sprints and milestone-level project phases.

How do I turn sprint blockers and recurring team patterns into actionable improvements?

You turn sprint blockers into actionable improvements by compiling blocker data and analyzing recurring team patterns to generate prioritized process improvements that drive continuous iteration.

Does this retrospective tool check for existing files to avoid duplicate work?

Yes, this retrospective tool includes checks for existing files to avoid duplicate work, ensuring your sprint and milestone retrospectives remain standardized without overwriting previous analysis.