- .git-commit-template.txt: 커밋 메시지 템플릿 추가 - .gitignore: OS 및 데이터베이스 관련 파일 무시 설정 추가 - .mcp.json: MCP 서버 설정 추가 - CLAUDE.md: SuperClaude 엔트리 포인트 문서 추가 - README.md: 프로젝트 템플릿 설명 추가 - .claude/COMMANDS.md: 명령어 실행 프레임워크 문서 추가 - .claude/FLAGS.md: 플래그 시스템 문서 추가 - .claude/MCP.md: MCP 서버 통합 문서 추가 - .claude/MODES.md: 운영 모드 문서 추가 - .claude/ORCHESTRATOR.md: 지능형 라우팅 시스템 문서 추가 - .claude/PERSONAS.md: 페르소나 시스템 문서 추가 - .claude/PRINCIPLES.md: 핵심 원칙 문서 추가 - .claude/RULES.md: 실행 가능한 규칙 문서 추가 - .claude/settings.json: 권한 설정 추가 - .claude/commands 디렉토리: 다양한 명령어 문서 추가 - .taskmaster/config.json: 기본 설정 파일 추가 - .taskmaster/docs 디렉토리: 문서 파일 추가 - .taskmaster/tasks/tasks.json: 기본 작업 파일 추가
22 KiB
ORCHESTRATOR.md - SuperClaude Intelligent Routing System
Intelligent routing system for Claude Code SuperClaude framework.
🧠 Detection Engine
Analyzes requests to understand intent, complexity, and requirements.
Pre-Operation Validation Checks
Resource Validation:
- Token usage prediction based on operation complexity and scope
- Memory and processing requirements estimation
- File system permissions and available space verification
- MCP server availability and response time checks
Compatibility Validation:
- Flag combination conflict detection (e.g.,
--no-mcpwith--seq) - Persona + command compatibility verification
- Tool availability for requested operations
- Project structure requirements validation
Risk Assessment:
- Operation complexity scoring (0.0-1.0 scale)
- Failure probability based on historical patterns
- Resource exhaustion likelihood prediction
- Cascading failure potential analysis
Validation Logic: Resource availability, flag compatibility, risk assessment, outcome prediction, and safety recommendations. Operations with risk scores >0.8 trigger safe mode suggestions.
Resource Management Thresholds:
- Green Zone (0-60%): Full operations, predictive monitoring active
- Yellow Zone (60-75%): Resource optimization, caching, suggest --uc mode
- Orange Zone (75-85%): Warning alerts, defer non-critical operations
- Red Zone (85-95%): Force efficiency modes, block resource-intensive operations
- Critical Zone (95%+): Emergency protocols, essential operations only
Pattern Recognition Rules
Complexity Detection
simple:
indicators:
- single file operations
- basic CRUD tasks
- straightforward queries
- < 3 step workflows
token_budget: 5K
time_estimate: < 5 min
moderate:
indicators:
- multi-file operations
- analysis tasks
- refactoring requests
- 3-10 step workflows
token_budget: 15K
time_estimate: 5-30 min
complex:
indicators:
- system-wide changes
- architectural decisions
- performance optimization
- > 10 step workflows
token_budget: 30K+
time_estimate: > 30 min
Domain Identification
frontend:
keywords: [UI, component, React, Vue, CSS, responsive, accessibility, implement component, build UI]
file_patterns: ["*.jsx", "*.tsx", "*.vue", "*.css", "*.scss"]
typical_operations: [create, implement, style, optimize, test]
backend:
keywords: [API, database, server, endpoint, authentication, performance, implement API, build service]
file_patterns: ["*.js", "*.ts", "*.py", "*.go", "controllers/*", "models/*"]
typical_operations: [implement, optimize, secure, scale]
infrastructure:
keywords: [deploy, Docker, CI/CD, monitoring, scaling, configuration]
file_patterns: ["Dockerfile", "*.yml", "*.yaml", ".github/*", "terraform/*"]
typical_operations: [setup, configure, automate, monitor]
security:
keywords: [vulnerability, authentication, encryption, audit, compliance]
file_patterns: ["*auth*", "*security*", "*.pem", "*.key"]
typical_operations: [scan, harden, audit, fix]
documentation:
keywords: [document, README, wiki, guide, manual, instructions, commit, release, changelog]
file_patterns: ["*.md", "*.rst", "*.txt", "docs/*", "README*", "CHANGELOG*"]
typical_operations: [write, document, explain, translate, localize]
iterative:
keywords: [improve, refine, enhance, correct, polish, fix, iterate, loop, repeatedly]
file_patterns: ["*.*"] # Can apply to any file type
typical_operations: [improve, refine, enhance, correct, polish, fix, iterate]
wave_eligible:
keywords: [comprehensive, systematically, thoroughly, enterprise, large-scale, multi-stage, progressive, iterative, campaign, audit]
complexity_indicators: [system-wide, architecture, performance, security, quality, scalability]
operation_indicators: [improve, optimize, refactor, modernize, enhance, audit, transform]
scale_indicators: [entire, complete, full, comprehensive, enterprise, large, massive]
typical_operations: [comprehensive_improvement, systematic_optimization, enterprise_transformation, progressive_enhancement]
Operation Type Classification
analysis:
verbs: [analyze, review, explain, understand, investigate, troubleshoot]
outputs: [insights, recommendations, reports]
typical_tools: [Grep, Read, Sequential]
creation:
verbs: [create, build, implement, generate, design]
outputs: [new files, features, components]
typical_tools: [Write, Magic, Context7]
implementation:
verbs: [implement, develop, code, construct, realize]
outputs: [working features, functional code, integrated components]
typical_tools: [Write, Edit, MultiEdit, Magic, Context7, Sequential]
modification:
verbs: [update, refactor, improve, optimize, fix]
outputs: [edited files, improvements]
typical_tools: [Edit, MultiEdit, Sequential]
debugging:
verbs: [debug, fix, troubleshoot, resolve, investigate]
outputs: [fixes, root causes, solutions]
typical_tools: [Grep, Sequential, Playwright]
iterative:
verbs: [improve, refine, enhance, correct, polish, fix, iterate, loop]
outputs: [progressive improvements, refined results, enhanced quality]
typical_tools: [Sequential, Read, Edit, MultiEdit, TodoWrite]
wave_operations:
verbs: [comprehensively, systematically, thoroughly, progressively, iteratively]
modifiers: [improve, optimize, refactor, modernize, enhance, audit, transform]
outputs: [comprehensive improvements, systematic enhancements, progressive transformations]
typical_tools: [Sequential, Task, Read, Edit, MultiEdit, Context7]
wave_patterns: [review-plan-implement-validate, assess-design-execute-verify, analyze-strategize-transform-optimize]
Intent Extraction Algorithm
1. Parse user request for keywords and patterns
2. Match against domain/operation matrices
3. Score complexity based on scope and steps
4. Evaluate wave opportunity scoring
5. Estimate resource requirements
6. Generate routing recommendation (traditional vs wave mode)
7. Apply auto-detection triggers for wave activation
Enhanced Wave Detection Algorithm:
- Flag Overrides:
--single-wavedisables,--force-waves/--wave-modeenables - Scoring Factors: Complexity (0.2-0.4), scale (0.2-0.3), operations (0.2), domains (0.1), flag modifiers (0.05-0.1)
- Thresholds: Default 0.7, customizable via
--wave-threshold, enterprise strategy lowers file thresholds - Decision Logic: Sum all indicators, trigger waves when total ≥ threshold
🚦 Routing Intelligence
Dynamic decision trees that map detected patterns to optimal tool combinations, persona activation, and orchestration strategies.
Wave Orchestration Engine
Multi-stage command execution with compound intelligence. Automatic complexity assessment or explicit flag control.
Wave Control Matrix:
wave-activation:
automatic: "complexity >= 0.7"
explicit: "--wave-mode, --force-waves"
override: "--single-wave, --wave-dry-run"
wave-strategies:
progressive: "Incremental enhancement"
systematic: "Methodical analysis"
adaptive: "Dynamic configuration"
Wave-Enabled Commands:
- Tier 1:
/analyze,/build,/implement,/improve - Tier 2:
/design,/task
Master Routing Table
| Pattern | Complexity | Domain | Auto-Activates | Confidence |
|---|---|---|---|---|
| "analyze architecture" | complex | infrastructure | architect persona, --ultrathink, Sequential | 95% |
| "create component" | simple | frontend | frontend persona, Magic, --uc | 90% |
| "implement feature" | moderate | any | domain-specific persona, Context7, Sequential | 88% |
| "implement API" | moderate | backend | backend persona, --seq, Context7 | 92% |
| "implement UI component" | simple | frontend | frontend persona, Magic, --c7 | 94% |
| "implement authentication" | complex | security | security persona, backend persona, --validate | 90% |
| "fix bug" | moderate | any | analyzer persona, --think, Sequential | 85% |
| "optimize performance" | complex | backend | performance persona, --think-hard, Playwright | 90% |
| "security audit" | complex | security | security persona, --ultrathink, Sequential | 95% |
| "write documentation" | moderate | documentation | scribe persona, --persona-scribe=en, Context7 | 95% |
| "improve iteratively" | moderate | iterative | intelligent persona, --seq, loop creation | 90% |
| "analyze large codebase" | complex | any | --delegate --parallel-dirs, domain specialists | 95% |
| "comprehensive audit" | complex | multi | --multi-agent --parallel-focus, specialized agents | 95% |
| "improve large system" | complex | any | --wave-mode --adaptive-waves | 90% |
| "security audit enterprise" | complex | security | --wave-mode --wave-validation | 95% |
| "modernize legacy system" | complex | legacy | --wave-mode --enterprise-waves --wave-checkpoint | 92% |
| "comprehensive code review" | complex | quality | --wave-mode --wave-validation --systematic-waves | 94% |
Decision Trees
Tool Selection Logic
Base Tool Selection:
- Search: Grep (specific patterns) or Agent (open-ended)
- Understanding: Sequential (complexity >0.7) or Read (simple)
- Documentation: Context7
- UI: Magic
- Testing: Playwright
Delegation & Wave Evaluation:
- Delegation Score >0.6: Add Task tool, auto-enable delegation flags based on scope
- Wave Score >0.7: Add Sequential for coordination, auto-enable wave strategies based on requirements
Auto-Flag Assignment:
- Directory count >7 →
--delegate --parallel-dirs - Focus areas >2 →
--multi-agent --parallel-focus - High complexity + critical quality →
--wave-mode --wave-validation - Multiple operation types →
--wave-mode --adaptive-waves
Task Delegation Intelligence
Sub-Agent Delegation Decision Matrix:
Delegation Scoring Factors:
- Complexity >0.6: +0.3 score
- Parallelizable Operations: +0.4 (scaled by opportunities/5, max 1.0)
- High Token Requirements >15K: +0.2 score
- Multi-domain Operations >2: +0.1 per domain
Wave Opportunity Scoring:
- High Complexity >0.8: +0.4 score
- Multiple Operation Types >2: +0.3 score
- Critical Quality Requirements: +0.2 score
- Large File Count >50: +0.1 score
- Iterative Indicators: +0.2 (scaled by indicators/3)
- Enterprise Scale: +0.15 score
Strategy Recommendations:
- Wave Score >0.7: Use wave strategies
- Directories >7:
parallel_dirs - Focus Areas >2:
parallel_focus - High Complexity:
adaptive_delegation - Default:
single_agent
Wave Strategy Selection:
- Security Focus:
wave_validation - Performance Focus:
progressive_waves - Critical Operations:
wave_validation - Multiple Operations:
adaptive_waves - Enterprise Scale:
enterprise_waves - Default:
systematic_waves
Auto-Delegation Triggers:
directory_threshold:
condition: directory_count > 7
action: auto_enable --delegate --parallel-dirs
confidence: 95%
file_threshold:
condition: file_count > 50 AND complexity > 0.6
action: auto_enable --delegate --sub-agents [calculated]
confidence: 90%
multi_domain:
condition: domains.length > 3
action: auto_enable --delegate --parallel-focus
confidence: 85%
complex_analysis:
condition: complexity > 0.8 AND scope = comprehensive
action: auto_enable --delegate --focus-agents
confidence: 90%
token_optimization:
condition: estimated_tokens > 20000
action: auto_enable --delegate --aggregate-results
confidence: 80%
Wave Auto-Delegation Triggers:
- Complex improvement: complexity > 0.8 AND files > 20 AND operation_types > 2 → --wave-count 5 (95%)
- Multi-domain analysis: domains > 3 AND tokens > 15K → --adaptive-waves (90%)
- Critical operations: production_deploy OR security_audit → --wave-validation (95%)
- Enterprise scale: files > 100 AND complexity > 0.7 AND domains > 2 → --enterprise-waves (85%)
- Large refactoring: large_scope AND structural_changes AND complexity > 0.8 → --systematic-waves --wave-validation (93%)
Delegation Routing Table:
| Operation | Complexity | Auto-Delegates | Performance Gain |
|---|---|---|---|
/load @monorepo/ |
moderate | --delegate --parallel-dirs | 65% |
/analyze --comprehensive |
high | --multi-agent --parallel-focus | 70% |
| Comprehensive system improvement | high | --wave-mode --progressive-waves | 80% |
| Enterprise security audit | high | --wave-mode --wave-validation | 85% |
| Large-scale refactoring | high | --wave-mode --systematic-waves | 75% |
Sub-Agent Specialization Matrix:
- Quality: qa persona, complexity/maintainability focus, Read/Grep/Sequential tools
- Security: security persona, vulnerabilities/compliance focus, Grep/Sequential/Context7 tools
- Performance: performance persona, bottlenecks/optimization focus, Read/Sequential/Playwright tools
- Architecture: architect persona, patterns/structure focus, Read/Sequential/Context7 tools
- API: backend persona, endpoints/contracts focus, Grep/Context7/Sequential tools
Wave-Specific Specialization Matrix:
- Review: analyzer persona, current_state/quality_assessment focus, Read/Grep/Sequential tools
- Planning: architect persona, strategy/design focus, Sequential/Context7/Write tools
- Implementation: intelligent persona, code_modification/feature_creation focus, Edit/MultiEdit/Task tools
- Validation: qa persona, testing/validation focus, Sequential/Playwright/Context7 tools
- Optimization: performance persona, performance_tuning/resource_optimization focus, Read/Sequential/Grep tools
Persona Auto-Activation System
Multi-Factor Activation Scoring:
- Keyword Matching: Base score from domain-specific terms (30%)
- Context Analysis: Project phase, urgency, complexity assessment (40%)
- User History: Past preferences and successful outcomes (20%)
- Performance Metrics: Current system state and bottlenecks (10%)
Intelligent Activation Rules:
Performance Issues → --persona-performance + --focus performance
- Trigger Conditions: Response time >500ms, error rate >1%, high resource usage
- Confidence Threshold: 85% for automatic activation
Security Concerns → --persona-security + --focus security
- Trigger Conditions: Vulnerability detection, auth failures, compliance gaps
- Confidence Threshold: 90% for automatic activation
UI/UX Tasks → --persona-frontend + --magic
- Trigger Conditions: Component creation, responsive design, accessibility
- Confidence Threshold: 80% for automatic activation
Complex Debugging → --persona-analyzer + --think + --seq
- Trigger Conditions: Multi-component failures, root cause investigation
- Confidence Threshold: 75% for automatic activation
Documentation Tasks → --persona-scribe=en
- Trigger Conditions: README, wiki, guides, commit messages, API docs
- Confidence Threshold: 70% for automatic activation
Flag Auto-Activation Patterns
Context-Based Auto-Activation:
- Performance issues → --persona-performance + --focus performance + --think
- Security concerns → --persona-security + --focus security + --validate
- UI/UX tasks → --persona-frontend + --magic + --c7
- Complex debugging → --think + --seq + --persona-analyzer
- Large codebase → --uc when context >75% + --delegate auto
- Testing operations → --persona-qa + --play + --validate
- DevOps operations → --persona-devops + --safe-mode + --validate
- Refactoring → --persona-refactorer + --wave-strategy systematic + --validate
- Iterative improvement → --loop for polish, refine, enhance keywords
Wave Auto-Activation:
- Complex multi-domain → --wave-mode auto when complexity >0.8 AND files >20 AND types >2
- Enterprise scale → --wave-strategy enterprise when files >100 AND complexity >0.7 AND domains >2
- Critical operations → Wave validation enabled by default for production deployments
- Legacy modernization → --wave-strategy enterprise --wave-delegation tasks
- Performance optimization → --wave-strategy progressive --wave-delegation files
- Large refactoring → --wave-strategy systematic --wave-delegation folders
Sub-Agent Auto-Activation:
- File analysis → --delegate files when >50 files detected
- Directory analysis → --delegate folders when >7 directories detected
- Mixed scope → --delegate auto for complex project structures
- High concurrency → --concurrency auto-adjusted based on system resources
Loop Auto-Activation:
- Quality improvement → --loop for polish, refine, enhance, improve keywords
- Iterative requests → --loop when "iteratively", "step by step", "incrementally" detected
- Refinement operations → --loop for cleanup, fix, correct operations on existing code
Flag Precedence Rules
- Safety flags (--safe-mode) > optimization flags
- Explicit flags > auto-activation
- Thinking depth: --ultrathink > --think-hard > --think
- --no-mcp overrides all individual MCP flags
- Scope: system > project > module > file
- Last specified persona takes precedence
- Wave mode: --wave-mode off > --wave-mode force > --wave-mode auto
- Sub-Agent delegation: explicit --delegate > auto-detection
- Loop mode: explicit --loop > auto-detection based on refinement keywords
- --uc auto-activation overrides verbose flags
Confidence Scoring
Based on pattern match strength (40%), historical success rate (30%), context completeness (20%), resource availability (10%).
Quality Gates & Validation Framework
8-Step Validation Cycle with AI Integration
quality_gates:
step_1_syntax: "language parsers, Context7 validation, intelligent suggestions"
step_2_type: "Sequential analysis, type compatibility, context-aware suggestions"
step_3_lint: "Context7 rules, quality analysis, refactoring suggestions"
step_4_security: "Sequential analysis, vulnerability assessment, OWASP compliance"
step_5_test: "Playwright E2E, coverage analysis (≥80% unit, ≥70% integration)"
step_6_performance: "Sequential analysis, benchmarking, optimization suggestions"
step_7_documentation: "Context7 patterns, completeness validation, accuracy verification"
step_8_integration: "Playwright testing, deployment validation, compatibility verification"
validation_automation:
continuous_integration: "CI/CD pipeline integration, progressive validation, early failure detection"
intelligent_monitoring: "success rate monitoring, ML prediction, adaptive validation"
evidence_generation: "comprehensive evidence, validation metrics, improvement recommendations"
wave_integration:
validation_across_waves: "wave boundary gates, progressive validation, rollback capability"
compound_validation: "AI orchestration, domain-specific patterns, intelligent aggregation"
Task Completion Criteria
completion_requirements:
validation: "all 8 steps pass, evidence provided, metrics documented"
ai_integration: "MCP coordination, persona integration, tool orchestration, ≥90% context retention"
performance: "response time targets, resource limits, success thresholds, token efficiency"
quality: "code quality standards, security compliance, performance assessment, integration testing"
evidence_requirements:
quantitative: "performance/quality/security metrics, coverage percentages, response times"
qualitative: "code quality improvements, security enhancements, UX improvements"
documentation: "change rationale, test results, performance benchmarks, security scans"
⚡ Performance Optimization
Resource management, operation batching, and intelligent optimization for sub-100ms performance targets.
Token Management: Intelligent resource allocation based on unified Resource Management Thresholds (see Detection Engine section)
Operation Batching:
- Tool Coordination: Parallel operations when no dependencies
- Context Sharing: Reuse analysis results across related routing decisions
- Cache Strategy: Store successful routing patterns for session reuse
- Task Delegation: Intelligent sub-agent spawning for parallel processing
- Resource Distribution: Dynamic token allocation across sub-agents
Resource Allocation:
- Detection Engine: 1-2K tokens for pattern analysis
- Decision Trees: 500-1K tokens for routing logic
- MCP Coordination: Variable based on servers activated
🔗 Integration Intelligence
Smart MCP server selection and orchestration.
MCP Server Selection Matrix
Reference: See MCP.md for detailed server capabilities, workflows, and integration patterns.
Quick Selection Guide:
- Context7: Library docs, framework patterns
- Sequential: Complex analysis, multi-step reasoning
- Magic: UI components, design systems
- Playwright: E2E testing, performance metrics
Intelligent Server Coordination
Reference: See MCP.md for complete server orchestration patterns and fallback strategies.
Core Coordination Logic: Multi-server operations, fallback chains, resource optimization
Persona Integration
Reference: See PERSONAS.md for detailed persona specifications and MCP server preferences.
🚨 Emergency Protocols
Handling resource constraints and failures gracefully.
Resource Management
Threshold-based resource management follows the unified Resource Management Thresholds (see Detection Engine section above).
Graceful Degradation
- Level 1: Reduce verbosity, skip optional enhancements, use cached results
- Level 2: Disable advanced features, simplify operations, batch aggressively
- Level 3: Essential operations only, maximum compression, queue non-critical
Error Recovery Patterns
- MCP Timeout: Use fallback server
- Token Limit: Activate compression
- Tool Failure: Try alternative tool
- Parse Error: Request clarification
🔧 Configuration
Orchestrator Settings
orchestrator_config:
# Performance
enable_caching: true
cache_ttl: 3600
parallel_operations: true
max_parallel: 3
# Intelligence
learning_enabled: true
confidence_threshold: 0.7
pattern_detection: aggressive
# Resource Management
token_reserve: 10%
emergency_threshold: 90%
compression_threshold: 75%
# Wave Mode Settings
wave_mode:
enable_auto_detection: true
wave_score_threshold: 0.7
max_waves_per_operation: 5
adaptive_wave_sizing: true
wave_validation_required: true
Custom Routing Rules
Users can add custom routing patterns via YAML configuration files.