retrospective-analyzer · qdhenry — Claude Code command: what it does
retrospective-analyzer pulls sprint numbers from Linear and Git, finds problems that repeat across retros, and drafts action items with owners and dates.
no license ★ 1,357 updated 2026-03-01
.claude/commands/retrospective-analyzer.mdWhat retrospective-analyzer does
It reads a sprint the way a team lead would: planned points against delivered, velocity, cycle time, escaped defects, how much work arrived unplanned. Git and GitHub supply the rest — commit spread, how long pull requests sit before merge, review turnaround, build success.
The flow is a set of steps. Pick the sprint, defaulting to the latest; confirm the Linear MCP connection; pull numbers and the softer signals such as review comments, commit messages and last retro's action items. Then it hunts for patterns and writes the output: a retro summary and a trend report across sprints, plus SMART actions with an owner and a date. With no Linear MCP you get Git data only, and it offers to go ahead on that, take metrics by hand, or reconnect and start over.
Sentiment comes from word lists applied to comments and commit messages, so treat it as a rough signal. A sprint still in flight gets a partial read, and the command asks before continuing.
What it helps with
- pull sprint metrics from Linear and Git into one report
- spot issues that keep coming back across retros
- prepare discussion questions before a retro
- turn retro notes into SMART actions with owners and dates
- compare velocity and cycle time against the previous sprint
Example prompts for the agent
- Run
/retrospective-analyzeron the last sprint and show planned versus delivered points - Find the problems that repeated across the last five retros
- Turn these retro notes into SMART action items with owners and dates
How to install retrospective-analyzer
Manually: put the files in place
.claude/commands/retrospective-analyzer.mdCall it with /retrospective-analyzer. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/retrospective-analyzer.mdCall it with /prompts:retrospective-analyzer. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/retrospective-analyzer.prompt.mdManually: put the files in place
.gemini/commands/retrospective-analyzer.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about retrospective-analyzer
How do I install retrospective-analyzer in Claude Code?
Place the command file at .claude/commands/retrospective-analyzer.md in your project. It then shows up among your slash commands.
What does retrospective-analyzer do?
It gathers sprint metrics from Linear and Git, looks for recurring patterns across retros, and produces a summary with suggested discussion topics and action items.
Does it need Linear?
Linear MCP supplies story points, task-level metrics and team capacity. Without that connection it falls back to Git data or to metrics you type in yourself.
Similar slash commands
All slash commands for DevOps and infrastructure →retrospective-analyzer by other authors comes first.