mirror of
https://github.com/SuperClaude-Org/SuperClaude_Framework.git
synced 2025-12-29 16:16:08 +00:00
ab8904bc8c
Restored 26 additional commands from commitd4a17fc, bringing total from 5 to 30 commands. ## New Commands Added (26): - /analyze - Code and architecture analysis - /brainstorm - Structured brainstorming sessions - /build - Build and compilation workflows - /business-panel - Multi-expert business analysis - /cleanup - Code cleanup and refactoring - /design - System design and architecture - /document - Documentation generation - /estimate - Effort and time estimation - /explain - Code explanation - /git - Git operations and workflows - /help - Command help and usage - /implement - Implementation workflows - /improve - Code improvement suggestions - /index - Project indexing (alias for index-repo) - /load - Load saved sessions - /pm - Project management workflows - /reflect - Reflection and retrospectives - /save - Save current session - /select-tool - Tool selection guidance - /spawn - Spawn parallel tasks - /spec-panel - Multi-expert specification analysis - /task - Task management - /test - Testing workflows - /troubleshoot - Debugging and troubleshooting - /workflow - Custom workflow automation ## Documentation Updates: - Created docs/reference/commands-list.md with categorized command reference - Updated README.md with expandable 30-command list - Updated README-zh.md with Chinese translations - Updated README-ja.md with Japanese translations - Updated README-kr.md with Korean translations - Changed statistics: "3 plugins" → "30 commands" - Added command categories: Planning & Design, Development, Testing & Quality, Documentation, Version Control, Project Management, Research & Analysis, Utilities ## Files Changed: - 60 files changed, 7930 insertions(+), 267 deletions(-) - Added 26 commands to plugins/superclaude/commands/ - Added 26 commands to src/superclaude/commands/ - Created comprehensive command documentation Commands restored from:d4a17fc(superclaude/commands/) Total: 30 commands now available 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
88 lines
3.9 KiB
Markdown
88 lines
3.9 KiB
Markdown
---
|
|
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)
|
|
|
|
## 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
|
|
|