Skip to main content
command CX Codex

estimate — Claude Code command: task estimation

This command estimates development time, effort, or complexity and returns a breakdown with risks. Use it to scope work before implementation begins.

MIT ★ 23,950 updated 2026-09-27

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/estimate.md
Open on GitHub

What estimate does

Run /sc:estimate to examine a task’s scope, dependencies, and complexity, then get an estimate with a breakdown, confidence intervals, and risk assessment. You can request a time, effort, or complexity estimate; time estimates can use hours, days, or weeks. The command produces a report only and does not start implementation.

The analysis can coordinate architect, performance, and project-manager personas. Sequential MCP and Context7 MCP are preferred tools, not requirements; when a server is unavailable, the command can fall back to native reasoning or other tools. Estimates are not guaranteed without scope analysis and validation, so treat the report as an assessment rather than a commitment.

What it helps with

  • estimate delivery time for a feature
  • split a task into effort categories
  • assess the complexity of an architecture migration
  • surface project risks and dependencies

Example prompts for the agent

  • Estimate the time for a user authentication system and break it into stages: /sc:estimate "user authentication system" --type time --unit days --breakdown
  • Assess the complexity of moving a monolith to microservices: /sc:estimate "migrate monolith to microservices" --type complexity --breakdown
  • Estimate the effort, in hours, for application performance work: /sc:estimate "optimize application performance" --type effort --unit hours

How to install estimate

Manually: put the files in place

.claude/commands/estimate.md

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

Questions about estimate

How do I install estimate in Claude Code?

Place the command file at .claude/commands/estimate.md.

What does estimate do?

It assesses development time, effort, or complexity and returns a report with a breakdown and risk analysis. It does not carry out the work.

Does estimate require Sequential MCP or Context7 MCP?

No. These are preferred tools rather than hard requirements; the command can fall back to native reasoning or other tools when a server is unavailable.

Source text

estimate.md · MIT
---
name: estimate
description: "Provide development estimates for tasks, features, or projects with intelligent analysis"
category: special
complexity: standard
mcp-servers: [sequential, context7]
personas: [architect, performance, project-manager]
---

# /sc:estimate - Development Estimation

## Triggers
- Development planning requiring time, effort, or complexity estimates
- Project scoping and resource allocation decisions
- Feature breakdown needing systematic estimation methodology
- Risk assessment and confidence interval analysis requirements

## Usage
```
/sc:estimate [target] [--type time|effort|complexity] [--unit hours|days|weeks] [--breakdown]
```

## Behavioral Flow
1. **Analyze**: Examine scope, complexity factors, dependencies, and framework patterns
2. **Calculate**: Apply estimation methodology with historical benchmarks and complexity scoring
3. **Validate**: Cross-reference estimates with project patterns and domain expertise
4. **Present**: Provide detailed breakdown with confidence intervals and risk assessment
5. **Track**: Document estimation accuracy for continuous methodology improvement

Key behaviors:
- Multi-persona coordination (architect, performance, project-manager) based on estimation scope
- Sequential MCP integration for systematic analysis and complexity assessment
- Context7 MCP integration for framework-specific patterns and historical benchmarks
- Intelligent breakdown analysis with confidence intervals and risk factors

## MCP Integration
- **Sequential MCP**: Complex multi-step estimation analysis and systematic complexity assessment
- **Context7 MCP**: Framework-specific estimation patterns and historical benchmark data
- **Persona Coordination**: Architect (design complexity), Performance (optimization effort), Project Manager (timeline)
- **Availability fallback**: The MCP servers named here are preferred tooling, not hard requirements — when one is not installed, degrade gracefully (native reasoning in place of Sequential, official docs via web lookup in place of Context7, native tools otherwise) instead of routing work to absent servers.

## Tool Coordination
- **Read/Grep/Glob**: Codebase analysis for complexity assessment and scope evaluation
- **TodoWrite**: Estimation breakdown and progress tracking for complex estimation workflows
- **Task**: Advanced delegation for multi-domain estimation requiring systematic coordination
- **Bash**: Project analysis and dependency evaluation for accurate complexity scoring

## Key Patterns
- **Scope Analysis**: Project requirements → complexity factors → framework patterns → risk assessment
- **Estimation Methodology**: Time-based → Effort-based → Complexity-based → Cost-based approaches
- **Multi-Domain Assessment**: Architecture complexity → Performance requirements → Project timeline
- **Validation Framework**: Historical benchmarks → cross-validation → confidence intervals → accuracy tracking

## Examples

### Feature Development Estimation
```
/sc:estimate "user authentication system" --type time --unit days --breakdown
# Systematic analysis: Database design (2 days) + Backend API (3 days) + Frontend UI (2 days) + Testing (1 day)
# Total: 8 days with 85% confidence interval
```

### Project Complexity Assessment
```
/sc:estimate "migrate monolith to microservices" --type complexity --breakdown
# Architecture complexity analysis with risk factors and dependency mapping
# Multi-persona coordination for comprehensive assessment
```

### Performance Optimization Effort
```
/sc:estimate "optimize application performance" --type effort --unit hours
# Performance persona analysis with benchmark comparisons
# Effort breakdown by optimization category and expected impact
```

## Boundaries

**Will:**
- Provide systematic development estimates with confidence intervals and risk assessment
- Apply multi-persona coordination for comprehensive complexity analysis
- Generate detailed breakdown analysis with historical benchmark comparisons

**Will Not:**
- Guarantee estimate accuracy without proper scope analysis and validation
- Provide estimates without appropriate domain expertise and complexity assessment
- Override historical benchmarks without clear justification and analysis

## CRITICAL BOUNDARIES

**STOP AFTER ESTIMATION**

This command produces an ESTIMATION REPORT ONLY - no implementation.

**Explicitly Will NOT**:
- Execute work based on estimates
- Create implementation timelines for execution
- Start implementation tasks
- Make commitments on behalf of user

**Output**: Estimation report containing:
- Time/effort breakdown
- Complexity analysis
- Confidence intervals
- Risk assessment
- Resource requirements

**Next Step**: After estimation, user decides on timeline. Use `/sc:workflow` for planning or `/sc:implement` for execution.

© SuperClaude-Org · MIT · SuperClaude-Org/SuperClaude_Framework

Similar slash commands

Slash commands catalog →

From the same set56

The whole set →
spawn spawn — a command that breaks down large multi-domain operations into hierarchical task plans with dependencies and delegation. Analyzes scope, decomposes work, and assigns executors—it plans rather than implements. CX Codex +1 ★ 23,950repo stars cleanup The cleanup command for Claude Code finds dead code, removes unused imports, and tidies project structure without breaking public APIs. CX Codex +1 ★ 23,950repo stars deep-research-agent The deep-research-agent subagent investigates complex questions, checks sources, and turns findings into a cited report. Use it for current topics or when information needs careful synthesis. CX Codex ★ 23,950repo stars improve improve removes technical debt, tunes execution speed, and patches vulnerabilities in your project. Useful for component refactoring and enforcing code standards. CX Codex +1 ★ 23,950repo stars implement The /sc:implement command coordinates feature development in Claude Code using specialist personas and MCP tools. It handles planning, code generation, and test prep. CX Codex +1 ★ 23,950repo stars task task — a slash command for multi-stage project execution with seven expert personas, intelligent MCP server routing, and cross-session context preservation. User-invoked, runs to completion, then stops. CX Codex +1 ★ 23,950repo stars workflow workflow parses PRDs and feature requirements to generate structured implementation plans with dependency mapping. It plans the execution without touching your code. CX Codex +1 ★ 23,950repo stars brainstorm brainstorm is a command for Claude Code, Codex, GitHub Copilot, and Gemini CLI that clarifies vague project ideas and turns them into requirements before planning. CX Codex +1 ★ 23,950repo stars

Project sponsors

Companies that keep this analytics open