Name: estimate
Author: yuemori

Prompt file imported from yuemori/UnityMCPTest (.cursor/commands/estimate.md). Copyright stays with the author.

/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

/estimate [target] [--type time|effort|complexity] [--unit hours|days|weeks] [--breakdown]

Behavioral Flow

Analyze: Examine scope, complexity factors, dependencies, and framework patterns
Calculate: Apply estimation methodology with historical benchmarks and complexity scoring
Validate: Cross-reference estimates with project patterns and domain expertise
Present: Provide detailed breakdown with confidence intervals and risk assessment
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)

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

/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

/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

/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

Install estimate and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# /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 ``` /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) ## 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 ``` /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 ``` /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 ``` /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

{ "prompt": "# /estimate - Development Estimation\n\n## Triggers\n\n- Development planning requiring time, effort, or complexity estimates\n- Project scoping and resource allocation decisions\n- Feature breakdown needing systematic estimation methodology\n- Risk assessment and confidence interval analysis requirements\n\n## Usage\n\n```\n/estimate [target] [--type time|effort|complexity] [--unit hours|days|weeks] [--breakdown]\n```\n\n## Behavioral Flow\n\n1. **Analyze**: Examine scope, complexity factors, dependencies, and framework patterns\n2. **Calculate**: Apply estimation methodology with historical benchmarks and complexity scoring\n3. **Validate**: Cross-reference estimates with project patterns and domain expertise\n4. **Present**: Provide detailed breakdown with confidence intervals and risk assessment\n5. **Track**: Document estimation accuracy for continuous methodology improvement\n\nKey behaviors:\n\n- Multi-persona coordination (architect, performance, project-manager) based on estimation scope\n- Sequential MCP integration for systematic analysis and complexity assessment\n- Context7 MCP integration for framework-specific patterns and historical benchmarks\n- Intelligent breakdown analysis with confidence intervals and risk factors\n\n## MCP Integration\n\n- **Sequential MCP**: Complex multi-step estimation analysis and systematic complexity assessment\n- **Context7 MCP**: Framework-specific estimation patterns and historical benchmark data\n- **Persona Coordination**: Architect (design complexity), Performance (optimization effort), Project Manager (timeline)\n\n## Tool Coordination\n\n- **Read/Grep/Glob**: Codebase analysis for complexity assessment and scope evaluation\n- **TodoWrite**: Estimation breakdown and progress tracking for complex estimation workflows\n- **Task**: Advanced delegation for multi-domain estimation requiring systematic coordination\n- **Bash**: Project analysis and dependency evaluation for accurate complexity scoring\n\n## Key Patterns\n\n- **Scope Analysis**: Project requirements → complexity factors → framework patterns → risk assessment\n- **Estimation Methodology**: Time-based → Effort-based → Complexity-based → Cost-based approaches\n- **Multi-Domain Assessment**: Architecture complexity → Performance requirements → Project timeline\n- **Validation Framework**: Historical benchmarks → cross-validation → confidence intervals → accuracy tracking\n\n## Examples\n\n### Feature Development Estimation\n\n```\n/estimate \"user authentication system\" --type time --unit days --breakdown\n# Systematic analysis: Database design (2 days) + Backend API (3 days) + Frontend UI (2 days) + Testing (1 day)\n# Total: 8 days with 85% confidence interval\n```\n\n### Project Complexity Assessment\n\n```\n/estimate \"migrate monolith to microservices\" --type complexity --breakdown\n# Architecture complexity analysis with risk factors and dependency mapping\n# Multi-persona coordination for comprehensive assessment\n```\n\n### Performance Optimization Effort\n\n```\n/estimate \"optimize application performance\" --type effort --unit hours\n# Performance persona analysis with benchmark comparisons\n# Effort breakdown by optimization category and expected impact\n```\n\n## Boundaries\n\n**Will:**\n\n- Provide systematic development estimates with confidence intervals and risk assessment\n- Apply multi-persona coordination for comprehensive complexity analysis\n- Generate detailed breakdown analysis with historical benchmark comparisons\n\n**Will Not:**\n\n- Guarantee estimate accuracy without proper scope analysis and validation\n- Provide estimates without appropriate domain expertise and complexity assessment\n- Override historical benchmarks without clear justification and analysis", "variables": [], "notes": "Provide development estimates for tasks, features, or projects with intelligent analysis", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/yuemori/UnityMCPTest", "path": ".cursor/commands/estimate.md", "ref": "4cdc3dcefbc27960027605300be8b99c49fff6b7", "url": "https://github.com/yuemori/UnityMCPTest/blob/4cdc3dcefbc27960027605300be8b99c49fff6b7/.cursor/commands/estimate.md", "key": "yuemori/UnityMCPTest/.cursor/commands/estimate.md" } } }

estimate

About