Skip to main content
command

estimate-assistant — Claude Code command for task estimates

Estimate tasks from Git history, code complexity, and team velocity. Use it to plan sprint work or compare estimates with past outcomes.

Install into Claude Code · claude-code-templates All methods and platforms ↓
npx claude-code-templates@latest --command team/estimate-assistant
Open on GitHub

What estimate-assistant does

Pass a task description or choose a mode: --historical, --complexity-analysis, --team-velocity, or --confidence-intervals. The command looks for similar work in Git history and returns an estimate with a confidence range and risk analysis.

It counts commits from the past month to assess team velocity and checks JavaScript, TypeScript, and Python files when gauging code size. Its analysis also uses task completion times from Linear, sprint load, and external dependencies. Historical team estimates therefore rely on accessible Git and Linear data.

The output includes past accuracy metrics and calibration recommendations. Listed methods include Monte Carlo simulation and forecasting from comparable work; the command description does not name separate tools for these methods.

What it helps with

  • estimate a task from similar changes in Git
  • assess technical complexity and scope uncertainty
  • factor team velocity and sprint load into an estimate
  • compare past estimates with actual completion times

Example prompts for the agent

  • Estimate the work for adding report export using past tasks: /estimate-assistant --historical
  • Assess the complexity of moving payment processing to a new API: /estimate-assistant --complexity-analysis
  • Give a confidence range for adding a status filter: /estimate-assistant --confidence-intervals

How to install estimate-assistant

1claude-code-templates

npx claude-code-templates@latest --command team/estimate-assistant

2Manually: put the files in place

.claude/commands/estimate-assistant.md

Call it with /estimate-assistant. For all projects use ~/.claude/commands/

Questions about estimate-assistant

How do I install estimate-assistant in Claude Code?

Run npx claude-code-templates@latest --command team/estimate-assistant. The command file path is .claude/commands/estimate-assistant.md.

What does estimate-assistant do?

It estimates tasks using Git history, code complexity, and team velocity. Its output includes a confidence range, risk assessment, and calibration recommendations.

What data does estimate-assistant use?

It checks Git commits from the past month, JavaScript, TypeScript, and Python files, and task completion times in Linear. Sprint load and external dependencies also factor into its analysis.

Source text

estimate-assistant.md · MIT
---
allowed-tools: Read, Bash, Glob, Grep
argument-hint: "[task-description] | --historical | --complexity-analysis | --team-velocity | --confidence-intervals"
description: Generate accurate task estimates using historical data, complexity analysis, and team velocity metrics
---

# Estimate Assistant

Generate data-driven task estimates with confidence intervals and accuracy tracking: **$ARGUMENTS**

## Current Estimation Context

- Team velocity: !`git log --oneline --since='1 month ago' | wc -l` commits in last month
- Historical data: Git history analysis for similar task completion patterns
- Code complexity: !`find . -name "*.js" -o -name "*.ts" -o -name "*.py" | head -5 | xargs wc -l 2>/dev/null | tail -1 || echo "No code files"`
- Sprint tracking: Linear task completion times and estimate accuracy

## Task

Execute comprehensive task estimation with historical analysis and confidence modeling:

**Estimation Focus**: Use $ARGUMENTS for task description analysis, historical pattern matching, complexity assessment, or team velocity calculation

**Estimation Framework**:
1. **Historical Pattern Analysis** - Analyze similar past tasks, extract completion time patterns, identify velocity trends, calculate accuracy metrics
2. **Complexity Assessment** - Evaluate technical complexity, assess scope uncertainty, identify risk factors, estimate effort distribution
3. **Team Velocity Integration** - Calculate sprint velocity, analyze individual capacity, assess team expertise, factor in availability constraints
4. **Confidence Modeling** - Generate confidence intervals, assess estimation uncertainty, identify risk factors, provide accuracy ranges
5. **Calibration Analysis** - Compare past estimates vs actuals, identify systematic biases, calculate estimation accuracy, improve prediction models
6. **Context Integration** - Factor in current sprint load, assess team familiarity, evaluate external dependencies, integrate deadline pressure

**Advanced Features**: Multi-point estimation, Monte Carlo simulation, reference class forecasting, estimation accuracy tracking, bias correction algorithms.

**Quality Metrics**: Estimation confidence levels, accuracy historical trends, velocity stability, complexity correlation analysis.

**Output**: Data-driven estimates with confidence intervals, historical accuracy metrics, risk assessment, and calibration recommendations.

© davila7 · MIT · davila7/claude-code-templates

Similar slash commands

All slash commands for Notes, tasks and projects →

From the same set495

The whole set →

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor