retrospective

Generates sprint or milestone retrospectives by analyzing plans, git history, and task completion data.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/onemanking/the-operator --skill retrospective-onemanking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/onemanking/the-operator/tree/main/.github/skills/retrospective
Command: npx skills add https://github.com/onemanking/the-operator --skill retrospective-onemanking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing sprint or milestone retrospectives manually requires digging through plans, git logs, and old reports to reconstruct what actually happened, which is time-consuming and often produces vague, data-free summaries. ## Core Features & Use Cases - Plan vs. Actual Analysis: Compares sprint or milestone plans against git history to identify completed, modified, carried-over, and unplanned tasks. - Velocity and Debt Tracking: Computes completion rates, velocity trends across sprints, and TODO/FIXME/HACK counts to show whether technical debt is growing or shrinking. - Action Item Follow-Up: Checks whether previous retrospective action items were addressed and generates owned, deadline-bound action items for the next iteration. - Use Case: After finishing Sprint 7, invoke the skill to produce a structured retrospective with metrics tables, blocker analysis, and estimation accuracy, saved to production/sprints/sprint-7-retrospective.md. ## Quick Start Run the retrospective skill with the argument sprint-7 to generate a data-backed retrospective for the last sprint.

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 automatically?

Invoke the skill with a sprint argument like sprint-7. It reads the sprint plan from production/sprints/, compares it against git log history, and writes a structured retrospective with metrics, blockers, and action items to production/sprints/sprint-7-retrospective.md.

How to track velocity trends across multiple sprints?

The skill builds a velocity trend table by reading previous retrospectives and comparing planned versus completed tasks across recent sprints. It labels the trend as increasing, stable, or decreasing with a one-sentence explanation.

Can I run a retrospective for a milestone instead of a sprint?

Yes, pass a milestone name as the argument instead of sprint-N. The skill reads milestone definitions from production/milestones/ and additionally evaluates whether milestone goals were achieved and what that means for the project timeline.

What data does a sprint retrospective need to be useful?

A useful retrospective needs the sprint plan with estimated effort, git commit history for the period, TODO/FIXME/HACK counts for technical debt, and prior retrospectives for action item follow-up. The skill gathers all of these automatically.

Why do retrospectives fail to improve team performance?

Retrospectives fail when they are vague, lack data, or produce action items without owners and deadlines. This skill enforces specificity by requiring measurable observations, limiting action items to 3-5, and checking whether previous items were completed.