skills.rest
rakhnianskii9
rakhnianskii9COMMUNITY
Explore all skills by this author →
GitHub

retrospective

Analyze sprint data and git logs to generate retrospective drafts and action items.

Updated Apr 24, 2026
Search Tags:#planning#retrospective#agile#data-analysis#velocity#sprint#action-items
One-click install
npx skills add https://github.com/rakhnianskii9/God-Godot --skill retrospective-rakhnianskii9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/rakhnianskii9/God-Godot/tree/main/.github/skills/retrospective
Command: npx skills add https://github.com/rakhnianskii9/God-Godot --skill retrospective-rakhnianskii9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sprint retrospectives are often manual, error-prone, and forgotten; this skill automates the analysis of completed work, velocity, blockers, and patterns to produce clear, actionable insights for the next iteration.

Core Features & Use Cases

  • Automated retrospective generation from sprint data (planned vs. actuals) plus velocity trends.
  • Identification of blockers, carryovers, and opportunities for process improvement.
  • Use Case: After a 2-week sprint, generate a structured retrospective with key metrics and actionable items for the next sprint.

Quick Start

Invoke the retrospective skill for the current sprint to generate a structured retro draft and recommended action items.

Frequently Asked Questions about retrospective

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

FAQPage Schema
How do I generate an automated sprint retrospective from velocity data and git logs?▼

To generate an automated sprint retrospective, the Skill analyzes completed work, velocity trends, blockers, and git logs to compare planned work with actuals and produce a structured draft with actionable insights.

What is the best way to identify blockers and carryovers in agile development cycles?▼

Identifying blockers and carryovers in agile development cycles is handled by analyzing completed sprint data and production milestones to detect patterns, compare plans against actuals, and generate recommended process improvements.

Does the retrospective analysis require access to specific project management data sources?▼

Yes, the retrospective analysis requires access to production sprints data and git logs to accurately compare planned work against actuals and output structured action items for the next iteration.

Can I use this for milestone retrospectives or is it only for 2-week software sprints?▼

You can use this for both ongoing software development sprints and broader project milestones, as the analysis handles data from production Sprints and Milestones to compare plans with actuals.

How do I turn sprint learnings into actionable items for the next iteration?▼

To turn sprint learnings into actionable items, the Skill analyzes completed work and velocity trends to identify blockers and opportunities, outputting a structured retrospective draft with recommended action items for the next sprint.

What limitations exist when automating agile retrospectives without manual team input?▼

Automating agile retrospectives without manual input relies entirely on available production sprints data and git logs, meaning qualitative team feedback is not factored into the generated structured draft and action items.

Related Skills

Explore More Product & Management Skills→
pixel-cellarpixel-cellar
277

retrospective

Generates sprint and MBOs from tracked data and MBOs.

Official
Advanced
eddowdingeddowding

meeting-follow-up

Extract action items and draft follow-up emails from meeting notes.

Community
Intermediate
Fantasia1999Fantasia1999

scrum-master

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

Community
Advanced
yocxy2yocxy2

retro

Analyze commit history and work patterns to generate engineering retrospective reports.

Community
Advanced