skills.rest
ezagent42
ezagent42OFFICIAL
Explore all skills by this author →
GitHub

retro

Analyze milestone execution data to generate structured retrospective recommendations.

1|1|Updated Apr 20, 2026
Search Tags:#planning#metrics#retrospective#bottlenecks#improvement#milestone#cycle-time
One-click install
npx skills add https://github.com/ezagent42/prd2impl --skill retro-ezagent42
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/ezagent42/prd2impl/tree/main/skills/skill-11-retro
Command: npx skills add https://github.com/ezagent42/prd2impl --skill retro-ezagent42

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Milestone retrospective analysis helps teams quickly identify bottlenecks, cycle-time distortions, and failure patterns to produce actionable improvements.

Core Features & Use Cases

  • Data gathering: collect task logs, git history, and artifact registries to form a complete picture of a milestone.
  • Pattern analysis: compute metrics like cycle times, blockers, and review waits to surface root causes.
  • Improvement recommendations: generate concrete, testable suggestions and carry-forward items for next milestone.

Quick Start

Analyze a completed milestone's execution data by feeding in the milestone ID and related sources to generate a retrospective report.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I generate a milestone retrospective from task logs and git history?▼

Milestone retrospective analysis identifies bottlenecks and failure patterns by computing metrics like cycle times and review waits. It processes task logs and git history to generate concrete improvement recommendations for the next milestone.

How do I analyze cycle-time distortions and blockers in completed milestones?▼

To identify bottlenecks and cycle-time distortions, apply retrospective analysis to completed milestone data. The system computes metrics from artifact registries and task logs to deliver structured recommendations and carry-forward items.

What data sources are needed to compute metrics for milestone improvement?▼

Computing milestone improvement metrics requires completed milestone execution data, specifically task logs, git history, and artifact registries. These sources provide the necessary inputs to analyze patterns and generate testable suggestions.

Can I use retrospective analysis for ongoing milestones or only completed ones?▼

Retrospective analysis is designed for completed milestones with task logs, git history, and artifact registries. It analyzes past execution data to produce carry-forward items for the next milestone.

What's the best way to turn execution data into actionable improvement recommendations?▼

The best way to turn execution data into actionable improvements is through milestone retrospective analysis. It computes metrics, analyzes patterns, and delivers structured recommendations with carry-forward items for the next cycle.

Related Skills

Explore More Data & Analytics Skills→
AlterLab-IEUAlterLab-IEU
23

game-postmortem

Generate structured post-mortem reports from git history, milestones, and retrospective notes.

Community
Advanced
tapaniatapania
5

5d-reflect

Capture completed work learnings into a formal Iteration Retrospective.

Community
Basic
Fantasia1999Fantasia1999

scrum-master

Analyze sprint data with Python scripts for forecasting and health scoring.

Community
Advanced
pynbj1001pynbj1001
4

fx-carry-trade

Compute carry-to-vol ratios and map forward curves for FX carry opportunities.

Community
Advanced