skills.rest
JunnnnyWon
JunnnnyWonCOMMUNITY
Explore all skills by this author →
GitHub

retrospective

Generate structured sprint retrospectives with planned versus actual work in Markdown reports.

Updated Aug 27, 2026
Search Tags:#retrospective#blockers#agile#velocity#sprint#action-items#sprint-analysis
One-click install
npx skills add https://github.com/JunnnnyWon/Codex-Game-Studios --skill retrospective-junnnnywon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/JunnnnyWon/Codex-Game-Studios/tree/main/.claude/skills/retrospective
Command: npx skills add https://github.com/JunnnnyWon/Codex-Game-Studios --skill retrospective-junnnnywon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating sprint or milestone retrospectives by analyzing completed work, velocity, blockers, and patterns to surface actionable insights.

Core Features & Use Cases

  • Phase-driven analysis to collect data from sprint plans, git logs, and templates.
  • Pattern detection for recurring issues and technical debt trends.
  • Actionable outputs with owners and deadlines to inform the next iteration.

Quick Start

Provide sprint or milestone data and run the retrospective workflow to generate a report.

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 sprint retrospective from git logs and planned work?▼

To generate an agile sprint retrospective, you provide sprint plans, git logs, and blocker data. The system analyzes planned versus actual work, detects patterns, and outputs a structured Markdown report with actionable items.

What is the best way to track velocity trends and technical debt across multiple milestones?▼

Tracking velocity trends and technical debt across milestones requires analyzing completed work and recurring blockers. The system applies phase-driven analysis to extract debt indicators and velocity data, producing consistent retrospective reports.

Can I use sprint analysis to automatically assign action items with owners and deadlines?▼

Yes, sprint analysis can automatically generate actionable outputs. By evaluating sprint data, blockers, and patterns, the system produces a retrospective report that assigns specific action items with designated owners and deadlines for the next iteration.

How does pattern detection work for recurring issues in a milestone retrospective?▼

Pattern detection in a milestone retrospective works by analyzing historical sprint data, actual commits, and documented blockers. It identifies recurring issues and technical debt trends to surface actionable insights for future iterations.

Do I need to format sprint data templates before running a retrospective analysis?▼

You need to provide raw sprint or milestone data such as sprint plans and git logs. The system processes this input through a phase-driven workflow to extract planned versus actual work, requiring minimal pre-formatting to generate the retrospective report.

Related Skills

Explore More Product & Management Skills→
mahg-esmahg-es
3

retrospective

Facilitate structured sprint retrospectives and generate action plans.

Official
Intermediate
MichaelSolatiMichaelSolati

retrospective

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

Community
Advanced
amanhsnamanhsn

agile-product-owner

Facilitate agile backlog management and sprint planning with user story writing.

Community
Intermediate
nikhillinitnikhillinit

tech-debt-tracker

Detect and prioritize technical debt with configurable thresholds and SQALE metrics.

Community
Advanced