mirror of https://github.com/SuperClaude-Org/SuperClaude_Framework.git synced 2025-12-29 16:16:08 +00:00

Files

NomenAK 219ff3905a feat: Optimize all 18 command files using @include reference system

Major streamlining achievement:
- Eliminate 2,733 lines of duplicate content across commands
- Reduce individual command files by ~70% (130-150 → 35-60 lines)
- Leverage existing shared/*.yml reference patterns
- Maintain full Claude Code compliance

Benefits:
• Single source of truth for universal content
• Guaranteed consistency across all commands
• Dramatically reduced maintenance overhead
• Massive token efficiency improvements

Implementation:
- Universal Legend: @include shared/universal-constants.yml#Universal Legend
- Universal Flags: @include shared/flag-inheritance.yml#Universal_Always
- Command patterns: References to appropriate shared/*.yml files
- Template system: Enhanced command-patterns.yml

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

2025-06-24 22:46:52 +02:00

2.7 KiB

Raw Blame History

/estimate - Estimate time, complexity and resources

Legend

@include shared/universal-constants.yml#Universal_Legend

Purpose

Provide comprehensive time, complexity, and resource estimates for tasks specified in $ARGUMENTS using data-driven analysis.

Syntax

/estimate [flags] [task]

@include shared/flag-inheritance.yml#Universal_Always

Core Flags

--scope flag:

feature: Single feature estimation
epic: Multi-feature epic
project: Full project scope
refactor: Code refactoring effort
migration: Data/system migration

--team flag:

solo: Single developer
small: 2-3 developers
medium: 4-8 developers
large: 9+ developers

--detail flag:

high: Detailed breakdown
medium: Standard estimates
low: Quick rough estimates

Estimation Components

Time Estimates:

Development hours/days
Testing & QA time
Code review cycles
Integration effort
Buffer for unknowns

Complexity Analysis:

Technical complexity score
Integration points
Dependencies & blockers
Risk factors
Learning curve

Resource Requirements:

Developer skill levels
Infrastructure needs
Third-party services
Testing resources
Documentation effort

Methodology

Estimation Factors:

Historical data from similar tasks
Code complexity metrics
Team velocity & capacity
Technical debt impact
External dependencies

Risk Assessment:

Technical risks
Resource availability
Timeline constraints
Scope creep potential
Integration challenges

Output Format

Standard Estimate:

Task: [Description]
Complexity: [Low/Medium/High]
Time_Estimate:
  Optimistic: X days
  Realistic: Y days
  Pessimistic: Z days
Resources:
  Developers: N
  QA: M hours
  Infrastructure: [Details]
Risks:
  - [Risk 1]: [Mitigation]
  - [Risk 2]: [Mitigation]
Assumptions:
  - [Assumption 1]
  - [Assumption 2]

Best Practices

Accuracy:

Break down into smaller tasks
Consider all phases (dev, test, deploy)
Include communication overhead
Account for code reviews
Add appropriate buffers

Communication:

Provide ranges, not fixed numbers
Document assumptions clearly
Highlight major risks
Update estimates as work progresses
Track actual vs estimated

Examples

# Quick feature estimate
/estimate "Add user authentication"

# Detailed project estimation
/estimate --scope project --detail high --team medium

# Refactoring estimate with risks
/estimate --scope refactor --think "Modernize legacy API"

# Migration project estimation
/estimate --scope migration --team large --ultrathink

Deliverables

Detailed time estimates with ranges
Complexity analysis & metrics
Resource allocation plan
Risk assessment & mitigation
Assumptions & dependencies
Confidence levels

2.7 KiB Raw Blame History