retrospective

Name: retrospective
Availability: InStock
Author: scomofo

Generate sprint or milestone retrospectives from plans, status, and git history.

Updated Mar 28, 2026

Search Tags:#retrospective #sprint planning #agile metrics #velocity trend #blocker analysis #estimation accuracy #git evidence

Ready to run

npx skills add https://github.com/scomofo/dragon-forge --skill retrospective-scomofo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/scomofo/dragon-forge/tree/main/.agents/skills/retrospective
Command: npx skills add https://github.com/scomofo/dragon-forge --skill retrospective-scomofo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams convert completed sprint or milestone work into a clear, data-driven retrospective so patterns, blockers, and concrete next actions are identified without relying on vague recollections.

Core Features & Use Cases

Sprint/milestone aware generation: Produces the correct retrospective type (sprint-N vs milestone-name) and uses the right plan and status sources.
Evidence-based metrics: Compares planned work against actual completion using sprint status data and commit history.
Actionable outputs: Generates metrics, velocity trends, blocker analysis, estimation accuracy, and 3–5 focused, owner-and-deadline action items.

Quick Start

Run the retrospective skill for sprint 04 by providing the argument sprint-04 and let it load the sprint plan/status, analyze completion and codebase TODO/FIXME trends, then save the retrospective to production/retrospectives.

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 with velocity trends and blocker analysis?▼

Generate a sprint retrospective by loading sprint plans and sprint-status.yaml, running git log over the iteration period, and analyzing completion data to produce velocity trends, blocker analysis, and measurable action items.

What is the best way to convert sprint outcomes into actionable improvements?▼

Converting sprint outcomes into actionable improvements requires comparing planned work against actual completion data and commit history to generate 3-5 focused action items with assigned owners and deadlines.

How does git evidence improve agile retrospective metrics and estimation accuracy?▼

Git evidence improves agile retrospective metrics by running git log over the sprint period to capture commit history, validating actual completion status and refining estimation accuracy analysis against planned work.

Can I use sprint-status.yaml to automate carryover analysis for milestone retrospectives?▼

Yes, you can use sprint-status.yaml to automate carryover analysis for milestone retrospectives. The tool loads authoritative sprint-status.yaml data to compare planned work against actual completion status.

Do I need prior retrospective artifacts to analyze sprint velocity trends?▼

Yes, you need prior retrospective artifacts to analyze sprint velocity trends. The process requires locating previous retrospective outputs to calculate accurate velocity deltas and trend lines for the current iteration.

What limitations exist when generating retrospectives from codebase TODO and FIXME signals?▼

A limitation when generating retrospectives from codebase TODO and FIXME signals is that the tool requires user confirmation before writing the new retrospective markdown file to production/retrospectives.