skills.rest
kay6198835
kay6198835COMMUNITY
Explore all skills by this author →
GitHub

retrospective

Generate structured sprint retrospectives from project data and git history.

Updated Feb 8, 2024
Search Tags:#retrospective#agile#velocity#sprint#project-management#milestone#action-items
One-click install
npx skills add https://github.com/kay6198835/Game-RPG --skill retrospective-kay6198835
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/kay6198835/Game-RPG/tree/main/.claude/skills/retrospective
Command: npx skills add https://github.com/kay6198835/Game-RPG --skill retrospective-kay6198835

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates a sprint or milestone retrospective by analyzing completed work, velocity, blockers, and patterns, producing actionable insights for the next iteration.

Core Features & Use Cases

  • Analyze planned vs. actual work, velocity trends, and blockers to surface actionable insights.
  • Compare retrospectives over time to spot recurring problems and track progress on action items.
  • Generate a comprehensive retrospective report that can be archived and referenced in future iterations.

Quick Start

Provide sprint or milestone data and let the skill generate a retrospective report.

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

To generate a sprint retrospective, provide your sprint or milestone data. The skill analyzes completed work, velocity trends, blockers, and git history to produce a comprehensive report with actionable insights and follow-up items.

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

The best way to analyze sprint velocity and blockers is to feed sprint plans and git history into a retrospective generator. It surfaces actionable insights by comparing planned versus actual work and tracking TODO trends.

Can I compare past retrospectives to spot recurring project problems?▼

Yes, you can compare retrospectives over time. The skill reads past retrospective reports to spot recurring problems and track progress on previously identified action items across iterations.

What data do I need to provide for an automated milestone retrospective?▼

To generate an automated milestone retrospective, you need to provide sprint plans, milestone definitions, and git history. The skill reads this project data to analyze completed work and surface actionable insights.

Does the retrospective analysis include recommended actions for the next sprint?▼

Yes, retrospective analysis includes recommended actions. It evaluates completed work, velocity, and blockers to produce a comprehensive report containing actionable insights and specific follow-up items for the next iteration.

Why use a structured retrospective report instead of manual sprint analysis?▼

A structured retrospective report archives historical data for future reference, preventing lost context. It automates the analysis of planned versus actual work and velocity trends, surfacing actionable insights efficiently.

Related Skills

Explore More Software Engineering Skills→
MichaelSolatiMichaelSolati

retrospective

Compile and analyze sprint retrospective data from project artifacts into structured reports.

Community
Advanced
dipandhali2021dipandhali2021

sprint-retrospective

Coordinate structured sprint retrospectives using Start-Stop-Continue, Mad-Sad-Glad, or 4Ls formats.

Community
Advanced
packetalienpacketalien

retrospective

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

Community
Advanced
LeKayLeKay

retrospective

Generate sprint or milestone retrospectives from git log data.

Community
Advanced