moflo 4.8.10 → 4.8.12

package/.claude/commands/agents/agent-spawning.md

@@ -1,28 +1,28 @@
-# agent-spawning
-
-Guide to spawning agents with Claude Code's Task tool.
-
-## Using Claude Code's Task Tool
-
-**CRITICAL**: Always use Claude Code's Task tool for actual agent execution:
-
-```javascript
-// Spawn ALL agents in ONE message
-Task("Researcher", "Analyze requirements...", "researcher")
-Task("Coder", "Implement features...", "coder")
-Task("Tester", "Create tests...", "tester")
-```
-
-## MCP Coordination Setup (Optional)
-
-MCP tools are ONLY for coordination:
-```javascript
-mcp__claude-flow__swarm_init { topology: "mesh" }
-mcp__claude-flow__agent_spawn { type: "researcher" }
-```
-
-## Best Practices
-1. Always spawn agents concurrently
-2. Use Task tool for execution
-3. MCP only for coordination
-4. Batch all operations
+# agent-spawning
+
+Guide to spawning agents with Claude Code's Task tool.
+
+## Using Claude Code's Task Tool
+
+**CRITICAL**: Always use Claude Code's Task tool for actual agent execution:
+
+```javascript
+// Spawn ALL agents in ONE message
+Task("Researcher", "Analyze requirements...", "researcher")
+Task("Coder", "Implement features...", "coder")
+Task("Tester", "Create tests...", "tester")
+```
+
+## MCP Coordination Setup (Optional)
+
+MCP tools are ONLY for coordination:
+```javascript
+mcp__moflo__swarm_init { topology: "mesh" }
+mcp__moflo__agent_spawn { type: "researcher" }
+```
+
+## Best Practices
+1. Always spawn agents concurrently
+2. Use Task tool for execution
+3. MCP only for coordination
+4. Batch all operations

package/.claude/commands/analysis/COMMAND_COMPLIANCE_REPORT.md

@@ -1,54 +1,54 @@
-# Analysis Commands Compliance Report
-
-## Overview
-Reviewed all command files in `.claude/commands/analysis/` directory to ensure proper usage of:
-- `mcp__claude-flow__*` tools (preferred)
-- `npx claude-flow` commands (as fallback)
-- No direct implementation calls
-
-## Files Reviewed
-
-### 1. token-efficiency.md
-**Status**: ✅ Updated
-**Changes Made**:
-- Replaced `npx ruv-swarm hook session-end --export-metrics` with proper MCP tool call
-- Updated to: `Tool: mcp__claude-flow__token_usage` with appropriate parameters
-- Maintained result format and context
-
-**Before**:
-```bash
-npx ruv-swarm hook session-end --export-metrics
-```
-
-**After**:
-```
-Tool: mcp__claude-flow__token_usage
-Parameters: {"operation": "session", "timeframe": "24h"}
-```
-
-### 2. performance-bottlenecks.md
-**Status**: ✅ Compliant (No changes needed)
-**Reason**: Already uses proper `mcp__claude-flow__task_results` tool format
-
-## Summary
-
-- **Total files reviewed**: 2
-- **Files updated**: 1
-- **Files already compliant**: 1
-- **Compliance rate after updates**: 100%
-
-## Compliance Patterns Enforced
-
-1. **MCP Tool Usage**: All direct tool calls now use `mcp__claude-flow__*` format
-2. **Parameter Format**: JSON parameters properly structured
-3. **Command Context**: Preserved original functionality and expected results
-4. **Documentation**: Maintained clarity and examples
-
-## Recommendations
-
-1. All analysis commands now follow the proper pattern
-2. No direct bash commands or implementation calls remain
-3. Token usage analysis properly integrated with MCP tools
-4. Performance analysis already using correct tool format
-
+# Analysis Commands Compliance Report
+
+## Overview
+Reviewed all command files in `.claude/commands/analysis/` directory to ensure proper usage of:
+- `mcp__moflo__*` tools (preferred)
+- `npx claude-flow` commands (as fallback)
+- No direct implementation calls
+
+## Files Reviewed
+
+### 1. token-efficiency.md
+**Status**: ✅ Updated
+**Changes Made**:
+- Replaced `npx ruv-swarm hook session-end --export-metrics` with proper MCP tool call
+- Updated to: `Tool: mcp__moflo__token_usage` with appropriate parameters
+- Maintained result format and context
+
+**Before**:
+```bash
+npx ruv-swarm hook session-end --export-metrics
+```
+
+**After**:
+```
+Tool: mcp__moflo__token_usage
+Parameters: {"operation": "session", "timeframe": "24h"}
+```
+
+### 2. performance-bottlenecks.md
+**Status**: ✅ Compliant (No changes needed)
+**Reason**: Already uses proper `mcp__moflo__task_results` tool format
+
+## Summary
+
+- **Total files reviewed**: 2
+- **Files updated**: 1
+- **Files already compliant**: 1
+- **Compliance rate after updates**: 100%
+
+## Compliance Patterns Enforced
+
+1. **MCP Tool Usage**: All direct tool calls now use `mcp__moflo__*` format
+2. **Parameter Format**: JSON parameters properly structured
+3. **Command Context**: Preserved original functionality and expected results
+4. **Documentation**: Maintained clarity and examples
+
+## Recommendations
+
+1. All analysis commands now follow the proper pattern
+2. No direct bash commands or implementation calls remain
+3. Token usage analysis properly integrated with MCP tools
+4. Performance analysis already using correct tool format
+
 The analysis directory is now fully compliant with the Claude Flow command standards.

package/.claude/commands/analysis/bottleneck-detect.md

@@ -1,162 +1,162 @@
-# bottleneck detect
-
-Analyze performance bottlenecks in swarm operations and suggest optimizations.
-
-## Usage
-
-```bash
-npx claude-flow bottleneck detect [options]
-```
-
-## Options
-
-- `--swarm-id, -s <id>` - Analyze specific swarm (default: current)
-- `--time-range, -t <range>` - Analysis period: 1h, 24h, 7d, all (default: 1h)
-- `--threshold <percent>` - Bottleneck threshold percentage (default: 20)
-- `--export, -e <file>` - Export analysis to file
-- `--fix` - Apply automatic optimizations
-
-## Examples
-
-### Basic bottleneck detection
-
-```bash
-npx claude-flow bottleneck detect
-```
-
-### Analyze specific swarm
-
-```bash
-npx claude-flow bottleneck detect --swarm-id swarm-123
-```
-
-### Last 24 hours with export
-
-```bash
-npx claude-flow bottleneck detect -t 24h -e bottlenecks.json
-```
-
-### Auto-fix detected issues
-
-```bash
-npx claude-flow bottleneck detect --fix --threshold 15
-```
-
-## Metrics Analyzed
-
-### Communication Bottlenecks
-
-- Message queue delays
-- Agent response times
-- Coordination overhead
-- Memory access patterns
-
-### Processing Bottlenecks
-
-- Task completion times
-- Agent utilization rates
-- Parallel execution efficiency
-- Resource contention
-
-### Memory Bottlenecks
-
-- Cache hit rates
-- Memory access patterns
-- Storage I/O performance
-- Neural pattern loading
-
-### Network Bottlenecks
-
-- API call latency
-- MCP communication delays
-- External service timeouts
-- Concurrent request limits
-
-## Output Format
-
-```
-🔍 Bottleneck Analysis Report
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-📊 Summary
-├── Time Range: Last 1 hour
-├── Agents Analyzed: 6
-├── Tasks Processed: 42
-└── Critical Issues: 2
-
-🚨 Critical Bottlenecks
-1. Agent Communication (35% impact)
-   └── coordinator → coder-1 messages delayed by 2.3s avg
-
-2. Memory Access (28% impact)
-   └── Neural pattern loading taking 1.8s per access
-
-⚠️ Warning Bottlenecks
-1. Task Queue (18% impact)
-   └── 5 tasks waiting > 10s for assignment
-
-💡 Recommendations
-1. Switch to hierarchical topology (est. 40% improvement)
-2. Enable memory caching (est. 25% improvement)
-3. Increase agent concurrency to 8 (est. 20% improvement)
-
-✅ Quick Fixes Available
-Run with --fix to apply:
-- Enable smart caching
-- Optimize message routing
-- Adjust agent priorities
-```
-
-## Automatic Fixes
-
-When using `--fix`, the following optimizations may be applied:
-
-1. **Topology Optimization**
-
-   - Switch to more efficient topology
-   - Adjust communication patterns
-   - Reduce coordination overhead
-
-2. **Caching Enhancement**
-
-   - Enable memory caching
-   - Optimize cache strategies
-   - Preload common patterns
-
-3. **Concurrency Tuning**
-
-   - Adjust agent counts
-   - Optimize parallel execution
-   - Balance workload distribution
-
-4. **Priority Adjustment**
-   - Reorder task queues
-   - Prioritize critical paths
-   - Reduce wait times
-
-## Performance Impact
-
-Typical improvements after bottleneck resolution:
-
-- **Communication**: 30-50% faster message delivery
-- **Processing**: 20-40% reduced task completion time
-- **Memory**: 40-60% fewer cache misses
-- **Overall**: 25-45% performance improvement
-
-## Integration with Claude Code
-
-```javascript
-// Check for bottlenecks in Claude Code
-mcp__claude-flow__bottleneck_detect {
-  timeRange: "1h",
-  threshold: 20,
-  autoFix: false
-}
-```
-
-## See Also
-
-- `performance report` - Detailed performance analysis
-- `token usage` - Token optimization analysis
-- `swarm monitor` - Real-time monitoring
-- `cache manage` - Cache optimization
+# bottleneck detect
+
+Analyze performance bottlenecks in swarm operations and suggest optimizations.
+
+## Usage
+
+```bash
+npx claude-flow bottleneck detect [options]
+```
+
+## Options
+
+- `--swarm-id, -s <id>` - Analyze specific swarm (default: current)
+- `--time-range, -t <range>` - Analysis period: 1h, 24h, 7d, all (default: 1h)
+- `--threshold <percent>` - Bottleneck threshold percentage (default: 20)
+- `--export, -e <file>` - Export analysis to file
+- `--fix` - Apply automatic optimizations
+
+## Examples
+
+### Basic bottleneck detection
+
+```bash
+npx claude-flow bottleneck detect
+```
+
+### Analyze specific swarm
+
+```bash
+npx claude-flow bottleneck detect --swarm-id swarm-123
+```
+
+### Last 24 hours with export
+
+```bash
+npx claude-flow bottleneck detect -t 24h -e bottlenecks.json
+```
+
+### Auto-fix detected issues
+
+```bash
+npx claude-flow bottleneck detect --fix --threshold 15
+```
+
+## Metrics Analyzed
+
+### Communication Bottlenecks
+
+- Message queue delays
+- Agent response times
+- Coordination overhead
+- Memory access patterns
+
+### Processing Bottlenecks
+
+- Task completion times
+- Agent utilization rates
+- Parallel execution efficiency
+- Resource contention
+
+### Memory Bottlenecks
+
+- Cache hit rates
+- Memory access patterns
+- Storage I/O performance
+- Neural pattern loading
+
+### Network Bottlenecks
+
+- API call latency
+- MCP communication delays
+- External service timeouts
+- Concurrent request limits
+
+## Output Format
+
+```
+🔍 Bottleneck Analysis Report
+━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+📊 Summary
+├── Time Range: Last 1 hour
+├── Agents Analyzed: 6
+├── Tasks Processed: 42
+└── Critical Issues: 2
+
+🚨 Critical Bottlenecks
+1. Agent Communication (35% impact)
+   └── coordinator → coder-1 messages delayed by 2.3s avg
+
+2. Memory Access (28% impact)
+   └── Neural pattern loading taking 1.8s per access
+
+⚠️ Warning Bottlenecks
+1. Task Queue (18% impact)
+   └── 5 tasks waiting > 10s for assignment
+
+💡 Recommendations
+1. Switch to hierarchical topology (est. 40% improvement)
+2. Enable memory caching (est. 25% improvement)
+3. Increase agent concurrency to 8 (est. 20% improvement)
+
+✅ Quick Fixes Available
+Run with --fix to apply:
+- Enable smart caching
+- Optimize message routing
+- Adjust agent priorities
+```
+
+## Automatic Fixes
+
+When using `--fix`, the following optimizations may be applied:
+
+1. **Topology Optimization**
+
+   - Switch to more efficient topology
+   - Adjust communication patterns
+   - Reduce coordination overhead
+
+2. **Caching Enhancement**
+
+   - Enable memory caching
+   - Optimize cache strategies
+   - Preload common patterns
+
+3. **Concurrency Tuning**
+
+   - Adjust agent counts
+   - Optimize parallel execution
+   - Balance workload distribution
+
+4. **Priority Adjustment**
+   - Reorder task queues
+   - Prioritize critical paths
+   - Reduce wait times
+
+## Performance Impact
+
+Typical improvements after bottleneck resolution:
+
+- **Communication**: 30-50% faster message delivery
+- **Processing**: 20-40% reduced task completion time
+- **Memory**: 40-60% fewer cache misses
+- **Overall**: 25-45% performance improvement
+
+## Integration with Claude Code
+
+```javascript
+// Check for bottlenecks in Claude Code
+mcp__moflo__bottleneck_detect {
+  timeRange: "1h",
+  threshold: 20,
+  autoFix: false
+}
+```
+
+## See Also
+
+- `performance report` - Detailed performance analysis
+- `token usage` - Token optimization analysis
+- `swarm monitor` - Real-time monitoring
+- `cache manage` - Cache optimization

package/.claude/commands/analysis/performance-bottlenecks.md

@@ -1,59 +1,59 @@
-# Performance Bottleneck Analysis
-
-## Purpose
-Identify and resolve performance bottlenecks in your development workflow.
-
-## Automated Analysis
-
-### 1. Real-time Detection
-The post-task hook automatically analyzes:
-- Execution time vs. complexity
-- Agent utilization rates
-- Resource constraints
-- Operation patterns
-
-### 2. Common Bottlenecks
-
-**Time Bottlenecks:**
-- Tasks taking > 5 minutes
-- Sequential operations that could parallelize
-- Redundant file operations
-
-**Coordination Bottlenecks:**
-- Single agent for complex tasks
-- Unbalanced agent workloads
-- Poor topology selection
-
-**Resource Bottlenecks:**
-- High operation count (> 100)
-- Memory constraints
-- I/O limitations
-
-### 3. Improvement Suggestions
-
-```
-Tool: mcp__claude-flow__task_results
-Parameters: {"taskId": "task-123", "format": "detailed"}
-
-Result includes:
-{
-  "bottlenecks": [
-    {
-      "type": "coordination",
-      "severity": "high",
-      "description": "Single agent used for complex task",
-      "recommendation": "Spawn specialized agents for parallel work"
-    }
-  ],
-  "improvements": [
-    {
-      "area": "execution_time",
-      "suggestion": "Use parallel task execution",
-      "expectedImprovement": "30-50% time reduction"
-    }
-  ]
-}
-```
-
-## Continuous Optimization
+# Performance Bottleneck Analysis
+
+## Purpose
+Identify and resolve performance bottlenecks in your development workflow.
+
+## Automated Analysis
+
+### 1. Real-time Detection
+The post-task hook automatically analyzes:
+- Execution time vs. complexity
+- Agent utilization rates
+- Resource constraints
+- Operation patterns
+
+### 2. Common Bottlenecks
+
+**Time Bottlenecks:**
+- Tasks taking > 5 minutes
+- Sequential operations that could parallelize
+- Redundant file operations
+
+**Coordination Bottlenecks:**
+- Single agent for complex tasks
+- Unbalanced agent workloads
+- Poor topology selection
+
+**Resource Bottlenecks:**
+- High operation count (> 100)
+- Memory constraints
+- I/O limitations
+
+### 3. Improvement Suggestions
+
+```
+Tool: mcp__moflo__task_results
+Parameters: {"taskId": "task-123", "format": "detailed"}
+
+Result includes:
+{
+  "bottlenecks": [
+    {
+      "type": "coordination",
+      "severity": "high",
+      "description": "Single agent used for complex task",
+      "recommendation": "Spawn specialized agents for parallel work"
+    }
+  ],
+  "improvements": [
+    {
+      "area": "execution_time",
+      "suggestion": "Use parallel task execution",
+      "expectedImprovement": "30-50% time reduction"
+    }
+  ]
+}
+```
+
+## Continuous Optimization
 The system learns from each task to prevent future bottlenecks!