retrospective

Extract sprint data into a structured markdown retrospective with actionable improvements.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/brand6/Claude-Code-Game-Studios-zh-auto --skill retrospective-brand6
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/brand6/Claude-Code-Game-Studios-zh-auto/tree/main/.claude/skills/retrospective
Command: npx skills add https://github.com/brand6/Claude-Code-Game-Studios-zh-auto --skill retrospective-brand6

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

迭代回顾与阻塞分析难以自动化。本 Skill 提供系统化的方法来分析已完成的工作、速度、阻塞项和规律,并产出下一次迭代的改进行动。

Core Features & Use Cases

  • 自动整理迭代数据与回顾要点,生成可执行的改进洞察。
  • 汇总速度趋势、阻塞源和系统分布,帮助规划下一步。
  • Use Case: 在冲刺结束后运行回顾,自动得到改进项和负载平衡建议。

Quick Start

输入要回顾的迭代编号,系统将生成可执行的改进洞察和下一步计划。

Frequently Asked Questions about retrospective

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

FAQPage Schema
How do I automate sprint retrospective reporting from velocity and blocker data?

Sprint retrospective reporting aggregates velocity, blockers, and system ownership data to produce a structured markdown report. It extracts historical trends and QA feedback to generate actionable improvement tasks for the next sprint.

What is the best way to turn agile sprint artifacts into actionable improvements?

Agile sprint artifacts are synthesized into actionable improvements by analyzing completed work, velocity trends, and blocker sources. This process outputs a concise retrospective report with structured recommendations and load balancing suggestions.

How do I analyze sprint blockers and velocity trends for continuous improvement?

Sprint blockers and velocity trends are analyzed by aggregating historical sprint data and current artifacts. This synthesis identifies recurring blocker sources and system distribution patterns to inform next steps and improvement actions.

Can I generate a structured retrospective report from QA feedback and sprint planning data?

Yes, a structured retrospective report incorporates QA feedback alongside sprint planning and execution data. It aggregates current sprint artifacts and historical trends to generate a markdown report with actionable tasks for agile teams.

Does automated retrospective analysis work for agile teams tracking system ownership and load balancing?

Automated retrospective analysis works for agile teams by aggregating system ownership distribution alongside velocity and blockers. It evaluates historical trends and current sprint data to produce load balancing suggestions and improvement insights.

What limitations exist when automating agile retrospective insights from sprint data?

Automating agile retrospective insights requires complete sprint artifacts, velocity records, and blocker data to function accurately. Without historical trends and QA feedback inputs, the generated markdown report and actionable tasks may lack sufficient context.