skills.rest
supermalang
supermalangCOMMUNITY
Explore all skills by this author →
Website𝕏@supermalang_GitHub

retro

Write a structured end-of-sprint retrospective file from git history and review blockers.

Updated Mar 2, 2026
Search Tags:#retrospective#roadmap#agile#process improvement#git history#sprint#review blockers
One-click install
npx skills add https://github.com/supermalang/ai-augmented-coding --skill retro-supermalang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/supermalang/ai-augmented-coding/tree/main/.claude/skills/retro
Command: npx skills add https://github.com/supermalang/ai-augmented-coding --skill retro-supermalang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns the end-of-sprint review into a structured retrospective so teams can understand what helped, what slowed delivery, and which process changes will improve the next sprint.

Core Features & Use Cases

  • Sprint evidence review: Reads roadmap outcomes, git history, review blockers, and sprint-exit checklist results to build an evidence-based view of the sprint.
  • Actionable process improvement: Distills recurring friction into concrete action items, with clear ownership and target timing.
  • Retrospective documentation: Writes a structured retrospective file under docs/retros so the sprint closes with a durable record of lessons learned.

Quick Start

Ask the assistant to run a retrospective for the current or most recent sprint and save the report in docs/retros with the correct sprint date.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I generate an agile sprint retrospective from git history and roadmap data?▼

An agile sprint retrospective summarizes sprint outcomes by analyzing git history, roadmap delivery, and review blockers to identify recurring friction and actionable process improvements.

What is the best way to turn sprint lessons into concrete process improvements?▼

The best way to turn sprint lessons into process improvements is by reviewing sprint-exit compliance and usability checks, then distilling recurring friction into action items with clear ownership.

How do I document end-of-sprint review results for future reference?▼

You document end-of-sprint review results by writing a structured retrospective file under docs/retros, creating a durable record of sprint outcomes and lessons learned.

Can I use retrospective tools to analyze review blockers without modifying code or tests?▼

Yes, retrospective tools can analyze review blockers while keeping code, tests, schema, and roadmap contents strictly read-only during the sprint review process.

Does an automated sprint review assess sprint-exit compliance and usability checks?▼

Yes, an automated sprint review examines sprint-exit compliance and usability checks alongside git history and roadmap outcomes to build an evidence-based view of the sprint.

What limitations exist when generating retrospective files from sprint evidence?▼

The main limitation is that the retrospective generation process only writes to the retrospective file directory, leaving all source code, tests, schemas, and roadmap contents completely read-only.

Related Skills

Explore More Product & Management Skills→
sethdfordsethdford
2

Sprint Planning Assistant

Generate sprint plans and risk assessments from team capacity and velocity.

Community
Advanced
phurynphuryn
25.0k

retro

Facilitate structured sprint retrospectives and generate prioritized action items with owners and deadlines.

Community
Intermediate
sfinessfines

bmad-sprint-planning

Parse epic files, detect story statuses, and generate sprint-status.yaml files.

Community
Intermediate
CuriousLearnerCuriousLearner
27

meeting-notes

Convert meeting transcripts into structured notes with decisions and action items.

Community
Intermediate