retrospective-analyzer — Claude Code command: setup guide
Runs retrospective analysis on sprint git commits and Linear completion data. Helps engineering teams track metrics and plan concrete action items.
npx claude-code-templates@latest --command team/retrospective-analyzerWhat retrospective-analyzer does
The command inspects recent sprint progress using Claude Code tools: Read, Write, Bash, and Glob. It counts commits from the past two weeks via git log and pulls sprint metrics directly through Linear MCP.
Its framework covers sprint velocity, review habits, process bottlenecks, and workload distribution. Flags let you narrow the output to raw metrics (--metrics), generated findings (--insights), prioritized tasks (--action-items), or multi-sprint history (--trends).
Linear MCP must be configured to inspect tickets and task completion. Without it, the prompt relies strictly on Git logs and local retrospective notes.
What it helps with
- Count two-week git commit volumes automatically
- Retrieve sprint completion stats from Linear MCP
- Track multi-sprint performance using
--trends - Extract prioritized process fixes with
--action-items
Example prompts for the agent
- /retrospective-analyzer sprint-24 --metrics
- /retrospective-analyzer --action-items
- /retrospective-analyzer --trends
How to install retrospective-analyzer
1claude-code-templates
npx claude-code-templates@latest --command team/retrospective-analyzer2Manually: 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 to install retrospective-analyzer in Claude Code?
Run npx claude-code-templates@latest --command team/retrospective-analyzer in your terminal. Alternatively, place the markdown prompt at .claude/commands/retrospective-analyzer.md.
What does retrospective-analyzer do?
It evaluates sprint outcomes by combining Git commit records with Linear MCP data. The command produces quantitative velocity metrics and a prioritized action list.
Is Linear MCP required for this command?
Linear MCP is necessary to import sprint tickets and completion rates. Without this connection, the command only processes local Git logs and existing retrospective files.
Source text
retrospective-analyzer.md · MIT
--- allowed-tools: Read, Write, Bash, Glob argument-hint: "[sprint-identifier] | --metrics | --insights | --action-items | --trends" description: Analyze team retrospectives with quantitative metrics and actionable insights generation --- # Retrospective Analyzer Analyze team retrospectives with comprehensive metrics and actionable improvement insights: **$ARGUMENTS** ## Current Retrospective Context - Sprint period: !`git log --oneline --since='2 weeks ago' | wc -l` commits in recent sprint - Team activity: Analysis of recent collaboration patterns and productivity metrics - Linear sprint: Current sprint data and completion metrics from Linear MCP - Previous retrospectives: Historical retrospective data and improvement tracking ## Task Execute comprehensive retrospective analysis with quantitative insights and improvement recommendations: **Analysis Focus**: Use $ARGUMENTS to specify sprint identifier, quantitative metrics, insight generation, action item tracking, or trend analysis **Retrospective Analysis Framework**: 1. **Sprint Performance Analysis** - Analyze velocity trends, completion rates, cycle time metrics, quality indicators 2. **Team Collaboration Assessment** - Evaluate communication patterns, code review effectiveness, knowledge sharing, pair programming impact 3. **Process Effectiveness** - Assess meeting efficiency, planning accuracy, impediment resolution, workflow optimization 4. **Quality Metrics** - Analyze bug rates, technical debt accumulation, code review quality, testing effectiveness 5. **Individual Contribution** - Evaluate workload distribution, skill development, mentorship activities, cross-training progress 6. **Actionable Insights Generation** - Identify improvement opportunities, prioritize action items, track progress, measure impact **Advanced Features**: Trend analysis across multiple sprints, predictive performance modeling, team satisfaction correlation, continuous improvement tracking. **Insight Quality**: Data-driven recommendations, quantified improvement potential, implementation feasibility, success measurement criteria. **Output**: Comprehensive retrospective analysis with quantitative metrics, actionable insights, prioritized improvements, and progress tracking framework.
© davila7 · MIT · davila7/claude-code-templates
