retrospective

Analyze sprint data to generate a structured retro document.

39|6|Updated May 3, 2026
One-click install
npx skills add https://github.com/cenconq25/claude-code-app-studio --skill retrospective-cenconq25
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/cenconq25/claude-code-app-studio/tree/main/.claude/skills/retrospective
Command: npx skills add https://github.com/cenconq25/claude-code-app-studio --skill retrospective-cenconq25

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates sprint or milestone retrospectives by analyzing completed work, velocity, blockers, and patterns to provide actionable improvements for the next iteration.

Core Features & Use Cases

  • Automated retro drafting: Converts sprint data into a structured retro document.
  • Data-driven insights: Identifies velocity trends, blocker patterns, and quality signals to guide process improvements.
  • Use Case: Run at sprint end or after a missed deadline to generate a retro and a set of concrete action items.

Quick Start

Run the retrospective on the most recent sprint to generate a retro document.

Frequently Asked Questions about retrospective

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

FAQPage Schema
How do I generate an actionable sprint retrospective from completed work data?▼

Generate an actionable sprint retrospective by analyzing completed work, velocity, blockers, and patterns to produce a structured retro document with concrete improvement opportunities. It reads sprint plans and stories to automate drafting.

What is the best way to identify velocity trends and blocker patterns after a sprint?▼

Identify velocity trends and blocker patterns after a sprint by computing data from sprint plans and stories. This process extracts quality signals and recurring issues to guide process improvements for the next iteration.

Can I run a milestone retrospective after a missed deadline to find improvement opportunities?▼

Yes, you can run a milestone retrospective after a missed deadline. It analyzes completed work and blockers from the milestone to generate a retro document with concrete action items for recovery and process improvement.

What input artifacts do I need to provide for an automated retrospective?▼

Provide sprint plans and stories as input artifacts for an automated retrospective. The system reads these artifacts to compute velocity and blockers, outputting the final retro document to a designated markdown file path.

How does automating a retrospective compare to manual retro drafting?▼

Automating retrospective drafting converts sprint data into a structured document using data-driven insights, whereas manual drafting relies on subjective recall. It computes velocity trends and blocker patterns objectively to output actionable improvements.