moflo 4.8.10 → 4.8.12

package/.claude/commands/memory/neural.md

@@ -1,47 +1,47 @@
-# Neural Pattern Training
-
-## 🎯 Key Principle
-**This tool coordinates Claude Code's actions. It does NOT write code or create content.**
-
-## MCP Tool Usage in Claude Code
-
-**Tool:** `mcp__claude-flow__neural_train`
-
-## Parameters
-```json
-{
-  "pattern_type": "coordination",
-  "training_data": "task decomposition patterns",
-  "epochs": 50
-}
-```
-
-## Description
-Improve coordination patterns through neural network training
-
-## Details
-Training improves:
-- Task breakdown effectiveness
-- Coordination pattern selection
-- Resource allocation strategies
-- Overall coordination efficiency
-
-## Example Usage
-
-**In Claude Code:**
-1. Train coordination patterns: Use tool `mcp__claude-flow__neural_train` with parameters `{"pattern_type": "coordination", "training_data": "successful task patterns", "epochs": 50}`
-2. Train optimization patterns: Use tool `mcp__claude-flow__neural_train` with parameters `{"pattern_type": "optimization", "training_data": "performance metrics", "epochs": 30}`
-3. Check training status: Use tool `mcp__claude-flow__neural_status`
-4. Analyze patterns: Use tool `mcp__claude-flow__neural_patterns` with parameters `{"action": "analyze"}`
-
-## Important Reminders
-- ✅ This tool provides coordination and structure
-- ✅ Claude Code performs all actual implementation
-- ❌ The tool does NOT write code
-- ❌ The tool does NOT access files directly
-- ❌ The tool does NOT execute commands
-
-## See Also
-- Main documentation: /CLAUDE.md
-- Other commands in this category
-- Workflow examples in /workflows/
+# Neural Pattern Training
+
+## 🎯 Key Principle
+**This tool coordinates Claude Code's actions. It does NOT write code or create content.**
+
+## MCP Tool Usage in Claude Code
+
+**Tool:** `mcp__moflo__neural_train`
+
+## Parameters
+```json
+{
+  "pattern_type": "coordination",
+  "training_data": "task decomposition patterns",
+  "epochs": 50
+}
+```
+
+## Description
+Improve coordination patterns through neural network training
+
+## Details
+Training improves:
+- Task breakdown effectiveness
+- Coordination pattern selection
+- Resource allocation strategies
+- Overall coordination efficiency
+
+## Example Usage
+
+**In Claude Code:**
+1. Train coordination patterns: Use tool `mcp__moflo__neural_train` with parameters `{"pattern_type": "coordination", "training_data": "successful task patterns", "epochs": 50}`
+2. Train optimization patterns: Use tool `mcp__moflo__neural_train` with parameters `{"pattern_type": "optimization", "training_data": "performance metrics", "epochs": 30}`
+3. Check training status: Use tool `mcp__moflo__neural_status`
+4. Analyze patterns: Use tool `mcp__moflo__neural_patterns` with parameters `{"action": "analyze"}`
+
+## Important Reminders
+- ✅ This tool provides coordination and structure
+- ✅ Claude Code performs all actual implementation
+- ❌ The tool does NOT write code
+- ❌ The tool does NOT access files directly
+- ❌ The tool does NOT execute commands
+
+## See Also
+- Main documentation: /CLAUDE.md
+- Other commands in this category
+- Workflow examples in /workflows/

package/.claude/commands/monitoring/agents.md

@@ -1,44 +1,44 @@
-# List Active Patterns
-
-## 🎯 Key Principle
-**This tool coordinates Claude Code's actions. It does NOT write code or create content.**
-
-## MCP Tool Usage in Claude Code
-
-**Tool:** `mcp__claude-flow__agent_list`
-
-## Parameters
-```json
-{
-  "swarmId": "current"
-}
-```
-
-## Description
-View all active cognitive patterns and their current focus areas
-
-## Details
-Filters:
-- **all**: Show all defined patterns
-- **active**: Currently engaged patterns
-- **idle**: Available but unused patterns
-- **busy**: Patterns actively coordinating tasks
-
-## Example Usage
-
-**In Claude Code:**
-1. List all agents: Use tool `mcp__claude-flow__agent_list`
-2. Get specific agent metrics: Use tool `mcp__claude-flow__agent_metrics` with parameters `{"agentId": "coder-123"}`
-3. Monitor agent performance: Use tool `mcp__claude-flow__swarm_monitor` with parameters `{"interval": 2000}`
-
-## Important Reminders
-- ✅ This tool provides coordination and structure
-- ✅ Claude Code performs all actual implementation
-- ❌ The tool does NOT write code
-- ❌ The tool does NOT access files directly
-- ❌ The tool does NOT execute commands
-
-## See Also
-- Main documentation: /CLAUDE.md
-- Other commands in this category
-- Workflow examples in /workflows/
+# List Active Patterns
+
+## 🎯 Key Principle
+**This tool coordinates Claude Code's actions. It does NOT write code or create content.**
+
+## MCP Tool Usage in Claude Code
+
+**Tool:** `mcp__moflo__agent_list`
+
+## Parameters
+```json
+{
+  "swarmId": "current"
+}
+```
+
+## Description
+View all active cognitive patterns and their current focus areas
+
+## Details
+Filters:
+- **all**: Show all defined patterns
+- **active**: Currently engaged patterns
+- **idle**: Available but unused patterns
+- **busy**: Patterns actively coordinating tasks
+
+## Example Usage
+
+**In Claude Code:**
+1. List all agents: Use tool `mcp__moflo__agent_list`
+2. Get specific agent metrics: Use tool `mcp__moflo__agent_metrics` with parameters `{"agentId": "coder-123"}`
+3. Monitor agent performance: Use tool `mcp__moflo__swarm_monitor` with parameters `{"interval": 2000}`
+
+## Important Reminders
+- ✅ This tool provides coordination and structure
+- ✅ Claude Code performs all actual implementation
+- ❌ The tool does NOT write code
+- ❌ The tool does NOT access files directly
+- ❌ The tool does NOT execute commands
+
+## See Also
+- Main documentation: /CLAUDE.md
+- Other commands in this category
+- Workflow examples in /workflows/

package/.claude/commands/monitoring/status.md

@@ -1,46 +1,46 @@
-# Check Coordination Status
-
-## 🎯 Key Principle
-**This tool coordinates Claude Code's actions. It does NOT write code or create content.**
-
-## MCP Tool Usage in Claude Code
-
-**Tool:** `mcp__claude-flow__swarm_status`
-
-## Parameters
-```json
-{
-  "swarmId": "current"
-}
-```
-
-## Description
-Monitor the effectiveness of current coordination patterns
-
-## Details
-Shows:
-- Active coordination topologies
-- Current cognitive patterns in use
-- Task breakdown and progress
-- Resource utilization for coordination
-- Overall system health
-
-## Example Usage
-
-**In Claude Code:**
-1. Check swarm status: Use tool `mcp__claude-flow__swarm_status`
-2. Monitor in real-time: Use tool `mcp__claude-flow__swarm_monitor` with parameters `{"interval": 1000}`
-3. Get agent metrics: Use tool `mcp__claude-flow__agent_metrics` with parameters `{"agentId": "agent-123"}`
-4. Health check: Use tool `mcp__claude-flow__health_check` with parameters `{"components": ["swarm", "memory", "neural"]}`
-
-## Important Reminders
-- ✅ This tool provides coordination and structure
-- ✅ Claude Code performs all actual implementation
-- ❌ The tool does NOT write code
-- ❌ The tool does NOT access files directly
-- ❌ The tool does NOT execute commands
-
-## See Also
-- Main documentation: /CLAUDE.md
-- Other commands in this category
-- Workflow examples in /workflows/
+# Check Coordination Status
+
+## 🎯 Key Principle
+**This tool coordinates Claude Code's actions. It does NOT write code or create content.**
+
+## MCP Tool Usage in Claude Code
+
+**Tool:** `mcp__moflo__swarm_status`
+
+## Parameters
+```json
+{
+  "swarmId": "current"
+}
+```
+
+## Description
+Monitor the effectiveness of current coordination patterns
+
+## Details
+Shows:
+- Active coordination topologies
+- Current cognitive patterns in use
+- Task breakdown and progress
+- Resource utilization for coordination
+- Overall system health
+
+## Example Usage
+
+**In Claude Code:**
+1. Check swarm status: Use tool `mcp__moflo__swarm_status`
+2. Monitor in real-time: Use tool `mcp__moflo__swarm_monitor` with parameters `{"interval": 1000}`
+3. Get agent metrics: Use tool `mcp__moflo__agent_metrics` with parameters `{"agentId": "agent-123"}`
+4. Health check: Use tool `mcp__moflo__health_check` with parameters `{"components": ["swarm", "memory", "neural"]}`
+
+## Important Reminders
+- ✅ This tool provides coordination and structure
+- ✅ Claude Code performs all actual implementation
+- ❌ The tool does NOT write code
+- ❌ The tool does NOT access files directly
+- ❌ The tool does NOT execute commands
+
+## See Also
+- Main documentation: /CLAUDE.md
+- Other commands in this category
+- Workflow examples in /workflows/

package/.claude/commands/optimization/auto-topology.md

@@ -1,62 +1,62 @@
-# Automatic Topology Selection
-
-## Purpose
-Automatically select the optimal swarm topology based on task complexity analysis.
-
-## How It Works
-
-### 1. Task Analysis
-The system analyzes your task description to determine:
-- Complexity level (simple/medium/complex)
-- Required agent types
-- Estimated duration
-- Resource requirements
-
-### 2. Topology Selection
-Based on analysis, it selects:
-- **Star**: For simple, centralized tasks
-- **Mesh**: For medium complexity with flexibility needs
-- **Hierarchical**: For complex tasks requiring structure
-- **Ring**: For sequential processing workflows
-
-### 3. Example Usage
-
-**Simple Task:**
-```
-Tool: mcp__claude-flow__task_orchestrate
-Parameters: {"task": "Fix typo in README.md"}
-Result: Automatically uses star topology with single agent
-```
-
-**Complex Task:**
-```
-Tool: mcp__claude-flow__task_orchestrate
-Parameters: {"task": "Refactor authentication system with JWT, add tests, update documentation"}
-Result: Automatically uses hierarchical topology with architect, coder, and tester agents
-```
-
-## Benefits
-- 🎯 Optimal performance for each task type
-- 🤖 Automatic agent assignment
-- ⚡ Reduced setup time
-- 📊 Better resource utilization
-
-## Hook Configuration
-The pre-task hook automatically handles topology selection:
-```json
-{
-  "command": "npx claude-flow hook pre-task --optimize-topology"
-}
-```
-
-## Direct Optimization
-```
-Tool: mcp__claude-flow__topology_optimize
-Parameters: {"swarmId": "current"}
-```
-
-## CLI Usage
-```bash
-# Auto-optimize topology via CLI
-npx claude-flow optimize topology
+# Automatic Topology Selection
+
+## Purpose
+Automatically select the optimal swarm topology based on task complexity analysis.
+
+## How It Works
+
+### 1. Task Analysis
+The system analyzes your task description to determine:
+- Complexity level (simple/medium/complex)
+- Required agent types
+- Estimated duration
+- Resource requirements
+
+### 2. Topology Selection
+Based on analysis, it selects:
+- **Star**: For simple, centralized tasks
+- **Mesh**: For medium complexity with flexibility needs
+- **Hierarchical**: For complex tasks requiring structure
+- **Ring**: For sequential processing workflows
+
+### 3. Example Usage
+
+**Simple Task:**
+```
+Tool: mcp__moflo__task_orchestrate
+Parameters: {"task": "Fix typo in README.md"}
+Result: Automatically uses star topology with single agent
+```
+
+**Complex Task:**
+```
+Tool: mcp__moflo__task_orchestrate
+Parameters: {"task": "Refactor authentication system with JWT, add tests, update documentation"}
+Result: Automatically uses hierarchical topology with architect, coder, and tester agents
+```
+
+## Benefits
+- 🎯 Optimal performance for each task type
+- 🤖 Automatic agent assignment
+- ⚡ Reduced setup time
+- 📊 Better resource utilization
+
+## Hook Configuration
+The pre-task hook automatically handles topology selection:
+```json
+{
+  "command": "npx claude-flow hook pre-task --optimize-topology"
+}
+```
+
+## Direct Optimization
+```
+Tool: mcp__moflo__topology_optimize
+Parameters: {"swarmId": "current"}
+```
+
+## CLI Usage
+```bash
+# Auto-optimize topology via CLI
+npx claude-flow optimize topology
 ```

package/.claude/commands/optimization/parallel-execution.md

@@ -1,50 +1,50 @@
-# Parallel Task Execution
-
-## Purpose
-Execute independent subtasks in parallel for maximum efficiency.
-
-## Coordination Strategy
-
-### 1. Task Decomposition
-```
-Tool: mcp__claude-flow__task_orchestrate
-Parameters: {
-  "task": "Build complete REST API with auth, CRUD operations, and tests",
-  "strategy": "parallel",
-  "maxAgents": 8
-}
-```
-
-### 2. Parallel Workflows
-The system automatically:
-- Identifies independent components
-- Assigns specialized agents
-- Executes in parallel where possible
-- Synchronizes at dependency points
-
-### 3. Example Breakdown
-For the REST API task:
-- **Agent 1 (Architect)**: Design API structure
-- **Agent 2-3 (Coders)**: Implement auth & CRUD in parallel
-- **Agent 4 (Tester)**: Write tests as features complete
-- **Agent 5 (Documenter)**: Update docs continuously
-
-## CLI Usage
-```bash
-# Execute parallel tasks via CLI
-npx claude-flow parallel "Build REST API" --max-agents 8
-```
-
-## Performance Gains
-- 🚀 2.8-4.4x faster execution
-- 💪 Optimal CPU utilization
-- 🔄 Automatic load balancing
-- 📈 Linear scalability with agents
-
-## Monitoring
-```
-Tool: mcp__claude-flow__swarm_monitor
-Parameters: {"interval": 1000, "swarmId": "current"}
-```
-
+# Parallel Task Execution
+
+## Purpose
+Execute independent subtasks in parallel for maximum efficiency.
+
+## Coordination Strategy
+
+### 1. Task Decomposition
+```
+Tool: mcp__moflo__task_orchestrate
+Parameters: {
+  "task": "Build complete REST API with auth, CRUD operations, and tests",
+  "strategy": "parallel",
+  "maxAgents": 8
+}
+```
+
+### 2. Parallel Workflows
+The system automatically:
+- Identifies independent components
+- Assigns specialized agents
+- Executes in parallel where possible
+- Synchronizes at dependency points
+
+### 3. Example Breakdown
+For the REST API task:
+- **Agent 1 (Architect)**: Design API structure
+- **Agent 2-3 (Coders)**: Implement auth & CRUD in parallel
+- **Agent 4 (Tester)**: Write tests as features complete
+- **Agent 5 (Documenter)**: Update docs continuously
+
+## CLI Usage
+```bash
+# Execute parallel tasks via CLI
+npx claude-flow parallel "Build REST API" --max-agents 8
+```
+
+## Performance Gains
+- 🚀 2.8-4.4x faster execution
+- 💪 Optimal CPU utilization
+- 🔄 Automatic load balancing
+- 📈 Linear scalability with agents
+
+## Monitoring
+```
+Tool: mcp__moflo__swarm_monitor
+Parameters: {"interval": 1000, "swarmId": "current"}
+```
+
 Watch real-time parallel execution progress!

package/.claude/commands/sparc/analyzer.md

@@ -1,52 +1,52 @@
-# SPARC Analyzer Mode
-
-## Purpose
-Deep code and data analysis with batch processing capabilities.
-
-## Activation
-
-### Option 1: Using MCP Tools (Preferred in Claude Code)
-```javascript
-mcp__claude-flow__sparc_mode {
-  mode: "analyzer",
-  task_description: "analyze codebase performance",
-  options: {
-    parallel: true,
-    detailed: true
-  }
-}
-```
-
-### Option 2: Using NPX CLI (Fallback when MCP not available)
-```bash
-# Use when running from terminal or MCP tools unavailable
-npx claude-flow sparc run analyzer "analyze codebase performance"
-
-# For alpha features
-npx claude-flow@alpha sparc run analyzer "analyze codebase performance"
-```
-
-### Option 3: Local Installation
-```bash
-# If claude-flow is installed locally
-./claude-flow sparc run analyzer "analyze codebase performance"
-```
-
-## Core Capabilities
-- Code analysis with parallel file processing
-- Data pattern recognition
-- Performance profiling
-- Memory usage analysis
-- Dependency mapping
-
-## Batch Operations
-- Parallel file analysis using concurrent Read operations
-- Batch pattern matching with Grep tool
-- Simultaneous metric collection
-- Aggregated reporting
-
-## Output Format
-- Detailed analysis reports
-- Performance metrics
-- Improvement recommendations
+# SPARC Analyzer Mode
+
+## Purpose
+Deep code and data analysis with batch processing capabilities.
+
+## Activation
+
+### Option 1: Using MCP Tools (Preferred in Claude Code)
+```javascript
+mcp__moflo__sparc_mode {
+  mode: "analyzer",
+  task_description: "analyze codebase performance",
+  options: {
+    parallel: true,
+    detailed: true
+  }
+}
+```
+
+### Option 2: Using NPX CLI (Fallback when MCP not available)
+```bash
+# Use when running from terminal or MCP tools unavailable
+npx claude-flow sparc run analyzer "analyze codebase performance"
+
+# For alpha features
+npx claude-flow@alpha sparc run analyzer "analyze codebase performance"
+```
+
+### Option 3: Local Installation
+```bash
+# If claude-flow is installed locally
+./claude-flow sparc run analyzer "analyze codebase performance"
+```
+
+## Core Capabilities
+- Code analysis with parallel file processing
+- Data pattern recognition
+- Performance profiling
+- Memory usage analysis
+- Dependency mapping
+
+## Batch Operations
+- Parallel file analysis using concurrent Read operations
+- Batch pattern matching with Grep tool
+- Simultaneous metric collection
+- Aggregated reporting
+
+## Output Format
+- Detailed analysis reports
+- Performance metrics
+- Improvement recommendations
 - Visualizations when applicable