skills.rest
solace-ill
solace-illCOMMUNITY
Explore all skills by this author →
GitHub

retrospective

Generate markdown retrospectives from sprint data and git history.

Updated Apr 26, 2026
Search Tags:#retrospective#blockers#agile#velocity#sprint#action-items
One-click install
npx skills add https://github.com/solace-ill/vector-flow --skill retrospective-solace-ill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/solace-ill/vector-flow/tree/main/.claude/skills/retrospective
Command: npx skills add https://github.com/solace-ill/vector-flow --skill retrospective-solace-ill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates structured retrospectives by analyzing completed work, velocity, blockers, and patterns to produce actionable insights for the next iteration.

Core Features & Use Cases

  • Automates the generation of sprint and milestone retrospectives to standardize reviews.
  • Analyzes planned work vs. actual delivery, velocity trends, blockers, and emerging patterns to surface improvement opportunities.
  • Reuses and references past retrospectives to track action item closure and recurring issues.
  • Produces a concise, report-friendly format suitable for team reviews and stakeholder updates.

Quick Start

Provide the sprint or milestone details when prompted to generate the retrospective.

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 from agile velocity and blocker data?▼

Generate a sprint retrospective by analyzing sprint data, including planned work versus actuals and previous retrospectives, producing a markdown report with metrics, velocity trends, blockers, and action items.

What is needed to automate milestone retrospective generation?▼

Automating milestone retrospective generation requires access to plan data, actuals, and previous retrospectives, while also reading git history for context to accurately track action item closure and recurring issues.

Can I use previous retrospectives to track recurring blockers across sprints?▼

Yes, previous retrospectives are reused and referenced to track action item closure and identify recurring blockers. The system analyzes these patterns alongside current sprint data to surface improvement opportunities.

Does the retrospective analysis read git history for sprint context?▼

Yes, the retrospective analysis reads git history for context. This historical data supplements plan data and actuals to provide a comprehensive view of completed work and emerging patterns.

What format does the automated retrospective report output?▼

The automated retrospective outputs a concise, report-friendly markdown format. This structured output includes dedicated sections for metrics, velocity, blockers, and action items suitable for stakeholder updates.

When should I use an automated retrospective over manual sprint review?▼

Use an automated retrospective to standardize reviews across sprint-level and milestone-level projects. It effectively surfaces improvement opportunities by analyzing velocity trends and patterns that manual reviews might overlook.

Related Skills

Explore More Software Engineering Skills→
JingyiWngJingyiWng

bmad-retrospective

Conduct post-epic retrospectives from story files and sprint-status.yaml.

Community
Advanced
packetalienpacketalien

retrospective

Analyze sprint and milestone data to generate a structured Markdown retrospective.

Community
Advanced
Fantasia1999Fantasia1999

scrum-master

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

Community
Advanced
legioncodeinclegioncodeinc
72

retrospective-stinger

Convert team feedback sessions into structured behavior-change workflows.

Official
Advanced