team-velocity-tracker — Claude Code command for team forecasting
Analyze sprint pace, team consistency, and delivery forecasts from Claude Code. Use it to examine capacity and estimate likely sprint outcomes.
npx claude-code-templates@latest --command team/team-velocity-trackerWhat team-velocity-tracker does
The command reviews sprint completion history and delivery patterns, then assesses how steady the team’s pace has been. It also considers team size, availability, and external factors when estimating future sprint results and delivery timelines.
Its analysis options include Monte Carlo forecasting, anomaly detection, and sustainable pace assessment. Pass a period or choose --sprint, --monthly, --quarterly, or --trend-analysis. One caveat: the current velocity context counts Git commits from the last two weeks, so that figure is not a story-point total.
Install it in Claude Code with npx claude-code-templates@latest --command team/team-velocity-tracker. The command file is placed at .claude/commands/team-velocity-tracker.md.
What it helps with
- compare team pace across sprints
- forecast delivery timelines from velocity patterns
- assess how team capacity affects sprint outcomes
- spot unusual changes in delivery pace
- relate velocity to quality and technical debt
Example prompts for the agent
- Analyze the team’s pace for a sprint:
/team-velocity-tracker --sprint. - Estimate delivery timelines from quarterly patterns:
/team-velocity-tracker --quarterly. - Find shifts and anomalies in the team’s velocity:
/team-velocity-tracker --trend-analysis.
How to install team-velocity-tracker
1claude-code-templates
npx claude-code-templates@latest --command team/team-velocity-tracker2Manually: put the files in place
.claude/commands/team-velocity-tracker.mdCall it with /team-velocity-tracker. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/team-velocity-tracker.mdCall it with /prompts:team-velocity-tracker. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/team-velocity-tracker.prompt.mdManually: put the files in place
.gemini/commands/team-velocity-tracker.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about team-velocity-tracker
How do I install team-velocity-tracker in Claude Code?
Run npx claude-code-templates@latest --command team/team-velocity-tracker. The command file is located at .claude/commands/team-velocity-tracker.md.
What does team-velocity-tracker do?
It reviews team velocity and consistency, considers capacity factors, and produces forecasts for sprint outcomes and delivery timelines.
How does it calculate the current velocity figure?
The current context counts Git commits from the last two weeks. That commit count is not a story-point completion total.
Source text
team-velocity-tracker.md · MIT
--- allowed-tools: Read, Bash, Glob, Grep argument-hint: "[analysis-period] | --sprint | --monthly | --quarterly | --trend-analysis" description: Track and analyze team velocity with predictive forecasting and performance optimization recommendations --- # Team Velocity Tracker Track team velocity patterns with predictive forecasting and performance optimization: **$ARGUMENTS** ## Current Velocity Context - Sprint velocity: !`git log --oneline --since='2 weeks ago' | wc -l` commits per current sprint - Team consistency: Analysis of velocity stability across recent sprints - Linear tracking: Sprint point completion rates and story delivery metrics - Capacity factors: Team size changes, availability, and skill development impact ## Task Execute comprehensive velocity tracking with predictive analytics and optimization recommendations: **Analysis Period**: Use $ARGUMENTS to focus on sprint velocity, monthly trends, quarterly patterns, or comprehensive trend analysis **Velocity Tracking Framework**: 1. **Historical Velocity Analysis** - Extract sprint completion data, analyze story point delivery, calculate team throughput, identify performance patterns 2. **Consistency Assessment** - Measure velocity stability, identify variance patterns, assess predictability factors, evaluate planning accuracy 3. **Capacity Correlation** - Analyze team size impact, assess skill level effects, evaluate availability constraints, measure external factor influence 4. **Predictive Forecasting** - Generate velocity projections, predict sprint outcomes, estimate delivery timelines, calculate confidence intervals 5. **Performance Optimization** - Identify improvement opportunities, recommend capacity adjustments, suggest process enhancements, optimize team composition 6. **Quality Integration** - Correlate velocity with quality metrics, assess technical debt impact, evaluate sustainable pace, measure team satisfaction **Advanced Features**: Monte Carlo forecasting, velocity trend decomposition, capacity planning optimization, performance anomaly detection, sustainable pace analysis. **Predictive Analytics**: Sprint outcome predictions, delivery timeline forecasting, capacity requirement planning, performance trend analysis. **Output**: Comprehensive velocity analysis with predictive forecasts, optimization recommendations, capacity planning insights, and sustainable performance strategies.
© davila7 · MIT · davila7/claude-code-templates