skills.rest
TraftG
TraftGCOMMUNITY
Explore all skills by this author →
GitHub

retrospective

Generate a Markdown retrospective from sprint plans and git history.

33|8|Updated Mar 26, 2026
Search Tags:#retrospective#blockers#agile#velocity#sprint#process-improvement#action-items
One-click install
npx skills add https://github.com/TraftG/opencode-game-studio --skill retrospective-traftg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/TraftG/opencode-game-studio/tree/main/.opencode/skills/retrospective
Command: npx skills add https://github.com/TraftG/opencode-game-studio --skill retrospective-traftg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts sprint data into a structured, actionable retrospective to guide next iterations.

Core Features & Use Cases

  • Plan vs. Actual Analysis: compare planned tasks, owners, and estimates against what was delivered.
  • Velocity & Trend Insights: analyze velocity over multiple sprints to identify patterns.
  • Actionable Output: generate a Markdown retrospective with clear blockers, carryovers, and next-step items.

Quick Start

Invoke the retrospective generator for the current sprint or milestone to produce a formatted retrospective document.

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 sprint data?▼

To generate an agile retrospective, the tool reads sprint plans and git history to compare planned versus actual work, outputting a Markdown document with metrics, blockers, and next-step actions.

What is the best way to analyze sprint velocity and identify blockers?▼

Analyzing sprint velocity and blockers is done by comparing planned tasks against actual delivery and git history, surfacing trends and actionable insights in a structured retrospective format.

Can I compare planned vs actual work for a milestone retrospective?▼

Yes, you can compare planned vs actual work for milestones by applying the generator to analyze planned tasks, owners, estimates, and actual delivery to produce a structured retrospective document.

Does the retrospective analysis require specific dependencies?▼

No specific dependencies are required to run the retrospective analysis, as it directly reads existing sprint or milestone plans alongside your git history to calculate metrics and generate output.

How do I track action items and carryovers across multiple sprints?▼

To track action items and carryovers across multiple sprints, the tool analyzes velocity trends over time and generates a Markdown retrospective highlighting incomplete work and clear next-step items.

Related Skills

Explore More Product & Management Skills→
Euraika-LabsEuraika-Labs
14

retrospective

Generate sprint or milestone retrospectives from plans, git commits, and outcomes.

Official
Intermediate
89jobrien89jobrien
4

action-item-organizer

Extract actionable items from documents into prioritized Markdown checklists.

Community
Intermediate
wsmanwsman
18

retrospective

Analyze sprint artifacts and git logs to generate retrospective reports.

Community
Advanced
Fantasia1999Fantasia1999

scrum-master

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

Community
Advanced