davila7--claude-code-templates
wehub-resource-sync
1 行
9.6 KiB
JSON
1 行
9.6 KiB
JSON
{"content": "# Orchestration Optimize Command\n\nAnalyze and optimize task orchestrations to improve efficiency, reduce bottlenecks, and maximize team productivity.\n\n## Usage\n\n```\n/orchestration/optimize [options]\n```\n\n## Description\n\nPerforms comprehensive analysis of active and historical orchestrations to identify optimization opportunities, suggest workflow improvements, and provide actionable insights for better task management.\n\n## Basic Commands\n\n### Analyze Current Orchestration\n```\n/orchestration/optimize\n```\nAnalyzes the most recently active orchestration for bottlenecks and inefficiencies.\n\n### Optimize Specific Orchestration\n```\n/orchestration/optimize --date 03_15_2024 --project auth_system\n```\nDeep analysis of a specific orchestration with detailed recommendations.\n\n### Performance Analysis\n```\n/orchestration/optimize --performance\n```\nFocuses on timing, velocity, and resource utilization metrics.\n\n### Dependency Optimization\n```\n/orchestration/optimize --dependencies\n```\nAnalyzes task dependencies for parallelization opportunities.\n\n## Analysis Areas\n\n### Bottleneck Detection\n```\n## Identified Bottlenecks\n\nCritical Path Analysis:\n- TASK-003 (JWT validation): Blocking 4 downstream tasks\n- Duration: 5.5h (150% of estimate)\n- Impact: 12h of parallel work delayed\n\nQueue Analysis:\n- on_hold queue: 6 tasks (avg 2.3 days waiting)\n- QA queue: 3 tasks (avg 8h waiting)\n- Recommendation: Add QA capacity or parallel testing\n\nResource Constraints:\n- dev-backend: 3 active tasks (overloaded)\n- dev-frontend: 0 active tasks (underutilized)\n- Suggestion: Cross-train or reassign suitable tasks\n```\n\n### Velocity Metrics\n```\n## Velocity Analysis\n\nCurrent Metrics:\n- Tasks/day: 2.1 (target: 3.0)\n- Avg task duration: 4.2h (vs 3.5h estimate)\n- Status transitions: todos→in_progress (2h avg wait)\n\nHistorical Comparison:\n- Last week: 2.8 tasks/day (33% faster)\n- Best week: 3.4 tasks/day (optimal conditions)\n\nTrending Issues:\n- Estimate accuracy declining (65% vs 80% last month)\n- QA feedback loop increased by 40%\n```\n\n### Dependency Analysis\n```\n## Dependency Optimization\n\nParallelization Opportunities:\n1. TASK-007, TASK-008 can run concurrently with TASK-003\n Potential time saving: 6 hours\n\n2. Frontend tasks independent of current backend work\n Parallelizable: TASK-009, TASK-010, TASK-011\n\nCritical Path Optimization:\n- Current: 24 hours (sequential)\n- Optimized: 16 hours (parallel execution)\n- Savings: 8 hours (33% improvement)\n\nDependency Simplification:\n- Remove false dependency: TASK-012 → TASK-004\n- Merge related tasks: TASK-014 + TASK-015\n```\n\n## Optimization Strategies\n\n### Resource Reallocation\n```\n/orchestration/optimize --rebalance\n```\n\nSuggests optimal task assignments:\n```\n## Recommended Resource Changes\n\nCurrent Load:\n┌─────────────────┬────────────┬─────────────┬────────────┐\n│ Agent │ Active │ Queue │ Utilization│\n├─────────────────┼────────────┼─────────────┼────────────┤\n│ dev-backend │ 3 tasks │ 2 tasks │ 180% │\n│ dev-frontend │ 0 tasks │ 4 tasks │ 0% │\n│ qa-engineer │ 2 tasks │ 1 task │ 120% │\n│ test-developer │ 1 task │ 0 tasks │ 60% │\n└─────────────────┴────────────┴─────────────┴────────────┘\n\nRecommendations:\n1. Move TASK-007 (API tests) to test-developer\n2. Assign TASK-009 (UI components) to dev-frontend\n3. Split TASK-003 into backend/frontend components\n```\n\n### Task Restructuring\n```\n/orchestration/optimize --restructure\n```\n\nSuggests task modifications:\n```\n## Task Restructuring Opportunities\n\nOversized Tasks (>6h estimate):\n- TASK-003: JWT validation (8h) \n → Split: JWT core (4h) + JWT middleware (3h) + Tests (1h)\n\nUndersized Tasks (<1h estimate):\n- TASK-011: Update config (0.5h)\n- TASK-012: Fix typos (0.25h)\n → Merge into maintenance batch\n\nMislabeled Dependencies:\n- TASK-008 doesn't actually need TASK-003\n → Remove dependency, add to parallel execution\n```\n\n### Workflow Improvements\n```\n/orchestration/optimize --workflow\n```\n\nProcess optimization suggestions:\n```\n## Workflow Optimization\n\nStatus Transition Delays:\n- todos → in_progress: 4.2h avg (target: <2h)\n- in_progress → qa: 1.2h avg (good)\n- qa → completed: 6.8h avg (target: <4h)\n\nRecommendations:\n1. Implement auto-assignment rules\n2. Add QA capacity during peak hours\n3. Create task preparation checklist\n\nCommunication Improvements:\n- 23% of blocks due to unclear requirements\n- 15% of QA failures from missing context\n- Add requirement review gate before in_progress\n```\n\n## Historical Analysis\n\n### Trend Analysis\n```\n/orchestration/optimize --trends --days 30\n```\n\nShows performance trends:\n```\n## 30-Day Performance Trends\n\nVelocity Trend: ↓ -15%\n- Week 1: 3.2 tasks/day\n- Week 2: 2.9 tasks/day \n- Week 3: 2.8 tasks/day\n- Week 4: 2.7 tasks/day\n\nQuality Trend: ↓ -8%\n- QA rejection rate increasing\n- Rework time per task up 12%\n\nEfficiency Indicators:\n- Estimate accuracy: 68% (down from 78%)\n- Parallel execution rate: 45% (up from 40%)\n- Blocked task duration: 1.8 days avg (up from 1.2 days)\n```\n\n### Pattern Recognition\n```\n## Identified Patterns\n\nTask Types Performance:\n- Features: 3.2h avg (close to estimates)\n- Bugfixes: 2.1h avg (underestimated by 40%)\n- Tests: 1.8h avg (overestimated by 20%)\n- Security: 5.1h avg (significantly underestimated)\n\nTime-of-Day Patterns:\n- Morning starts: 25% faster completion\n- Post-lunch blocks: 40% more likely\n- End-of-day QA: 60% higher failure rate\n\nAgent Specialization:\n- dev-backend: 2x faster on API tasks\n- dev-frontend: 30% faster on UI tasks\n- Cross-functional tasks: 50% slower than specialized\n```\n\n## Optimization Actions\n\n### Immediate Actions\n```\n/orchestration/optimize --execute immediate\n```\n\nApplies safe optimizations:\n1. Rebalance current task assignments\n2. Remove identified false dependencies\n3. Update task estimates based on historical data\n4. Reschedule blocked tasks\n\n### Structural Changes\n```\n/orchestration/optimize --execute structural --confirm\n```\n\nRequires confirmation for:\n1. Task splitting/merging\n2. Workflow process changes\n3. Agent role modifications\n4. Dependency restructuring\n\n### Continuous Optimization\n```\n/orchestration/optimize --schedule daily\n```\n\nSets up automated optimization:\n- Daily velocity monitoring\n- Weekly bottleneck analysis\n- Monthly trend reporting\n- Automated rebalancing suggestions\n\n## Simulation Mode\n\n### What-If Analysis\n```\n/orchestration/optimize --simulate \"add agent:dev-fullstack\"\n```\n\nProjects impact of changes:\n```\n## Simulation Results: Adding dev-fullstack\n\nProjected Improvements:\n- Velocity: 2.7 → 3.4 tasks/day (+26%)\n- Critical path: 24h → 18h (-25%)\n- Queue time: 4.2h → 2.1h (-50%)\n\nResource Utilization:\n- Backend overload: 180% → 120% (optimal)\n- Frontend underload: 0% → 80% (good)\n- Overall efficiency: +35%\n\nROI Analysis:\n- Cost: +1 team member\n- Delivery speed: +26%\n- Quality impact: Neutral to positive\n```\n\n## Integration Features\n\n### Automated Optimization\n```\n/orchestration/optimize --auto-apply --threshold conservative\n```\n\nAutomatically applies optimizations meeting conservative safety criteria.\n\n### Notification System\n```\n/orchestration/optimize --alerts bottleneck,velocity,quality\n```\n\nSets up alerts for optimization opportunities.\n\n### Historical Learning\n```\n/orchestration/optimize --learn-from previous_projects/\n```\n\nIncorporates lessons from past orchestrations.\n\n## Reporting\n\n### Optimization Report\n```\n/orchestration/optimize --report detailed\n```\n\nGenerates comprehensive optimization report with:\n- Current state analysis\n- Identified opportunities \n- Recommended actions\n- Expected impact metrics\n- Implementation timeline\n\n### Executive Summary\n```\n/orchestration/optimize --summary executive\n```\n\nHigh-level optimization insights for leadership.\n\n## Best Practices\n\n1. **Regular Analysis**: Run optimization weekly on active orchestrations\n2. **Incremental Changes**: Apply optimizations gradually to measure impact\n3. **Monitor Impact**: Track metrics before and after optimization\n4. **Team Communication**: Share optimization insights with the team\n5. **Continuous Learning**: Use historical data to improve future orchestrations\n\n## Examples\n\n### Example 1: Daily Optimization Check\n```\n/orchestration/optimize --quick --auto-rebalance\n```\n\n### Example 2: Deep Analysis for Struggling Project\n```\n/orchestration/optimize --date 03_15_2024 --project auth_system --deep-analysis\n```\n\n### Example 3: Team Performance Review\n```\n/orchestration/optimize --trends --days 90 --team-focus\n```\n\n## Configuration\n\n### Optimization Rules\nSet in orchestration config:\n```yaml\noptimization:\n auto_rebalance: true\n bottleneck_threshold: 2h\n velocity_target: 3.0\n quality_threshold: 85%\n parallel_execution_target: 60%\n```\n\n## Notes\n\n- All optimizations are reversible through audit trail\n- Simulation mode allows safe experimentation\n- Historical data improves optimization accuracy over time\n- Integrates with all other orchestration commands\n- Supports custom optimization rules per project type"} |