agentic-qe 1.9.1 → 1.9.3

package/.claude/commands/sparc/orchestrator.md

@@ -1,132 +0,0 @@
-# SPARC Orchestrator Mode
-
-## Purpose
-Multi-agent task orchestration with TodoWrite/TodoRead/Task/Memory using MCP tools.
-
-## Activation
-
-### Option 1: Using MCP Tools (Preferred in Claude Code)
-```javascript
-mcp__claude-flow__sparc_mode {
-  mode: "orchestrator",
-  task_description: "coordinate feature development"
-}
-```
-
-### 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 orchestrator "coordinate feature development"
-
-# For alpha features
-npx claude-flow@alpha sparc run orchestrator "coordinate feature development"
-```
-
-### Option 3: Local Installation
-```bash
-# If claude-flow is installed locally
-./claude-flow sparc run orchestrator "coordinate feature development"
-```
-
-## Core Capabilities
-- Task decomposition
-- Agent coordination
-- Resource allocation
-- Progress tracking
-- Result synthesis
-
-## Integration Examples
-
-### Using MCP Tools (Preferred)
-```javascript
-// Initialize orchestration swarm
-mcp__claude-flow__swarm_init {
-  topology: "hierarchical",
-  strategy: "auto",
-  maxAgents: 8
-}
-
-// Spawn coordinator agent
-mcp__claude-flow__agent_spawn {
-  type: "coordinator",
-  capabilities: ["task-planning", "resource-management"]
-}
-
-// Orchestrate tasks
-mcp__claude-flow__task_orchestrate {
-  task: "feature development",
-  strategy: "parallel",
-  dependencies: ["auth", "ui", "api"]
-}
-```
-
-### Using NPX CLI (Fallback)
-```bash
-# Initialize orchestration swarm
-npx claude-flow swarm init --topology hierarchical --strategy auto --max-agents 8
-
-# Spawn coordinator agent
-npx claude-flow agent spawn --type coordinator --capabilities "task-planning,resource-management"
-
-# Orchestrate tasks
-npx claude-flow task orchestrate --task "feature development" --strategy parallel --deps "auth,ui,api"
-```
-
-## Orchestration Patterns
-- Hierarchical coordination
-- Parallel execution
-- Sequential pipelines
-- Event-driven flows
-- Adaptive strategies
-
-## Coordination Tools
-- TodoWrite for planning
-- Task for agent launch
-- Memory for sharing
-- Progress monitoring
-- Result aggregation
-
-## Workflow Example
-
-### Using MCP Tools (Preferred)
-```javascript
-// 1. Initialize orchestration swarm
-mcp__claude-flow__swarm_init {
-  topology: "hierarchical",
-  maxAgents: 10
-}
-
-// 2. Create workflow
-mcp__claude-flow__workflow_create {
-  name: "feature-development",
-  steps: ["design", "implement", "test", "deploy"]
-}
-
-// 3. Execute orchestration
-mcp__claude-flow__sparc_mode {
-  mode: "orchestrator",
-  options: {parallel: true, monitor: true},
-  task_description: "develop user management system"
-}
-
-// 4. Monitor progress
-mcp__claude-flow__swarm_monitor {
-  swarmId: "current",
-  interval: 5000
-}
-```
-
-### Using NPX CLI (Fallback)
-```bash
-# 1. Initialize orchestration swarm
-npx claude-flow swarm init --topology hierarchical --max-agents 10
-
-# 2. Create workflow
-npx claude-flow workflow create --name "feature-development" --steps "design,implement,test,deploy"
-
-# 3. Execute orchestration
-npx claude-flow sparc run orchestrator "develop user management system" --parallel --monitor
-
-# 4. Monitor progress
-npx claude-flow swarm monitor --interval 5000
-```

package/.claude/commands/sparc/sparc-modes.md

@@ -1,174 +0,0 @@
-# SPARC Modes Overview
-
-SPARC (Specification, Planning, Architecture, Review, Code) is a comprehensive development methodology with 17 specialized modes, all integrated with MCP tools for enhanced coordination and execution.
-
-## Available Modes
-
-### Core Orchestration Modes
-- **orchestrator**: Multi-agent task orchestration
-- **swarm-coordinator**: Specialized swarm management
-- **workflow-manager**: Process automation
-- **batch-executor**: Parallel task execution
-
-### Development Modes  
-- **coder**: Autonomous code generation
-- **architect**: System design
-- **reviewer**: Code review
-- **tdd**: Test-driven development
-
-### Analysis and Research Modes
-- **researcher**: Deep research capabilities
-- **analyzer**: Code and data analysis
-- **optimizer**: Performance optimization
-
-### Creative and Support Modes
-- **designer**: UI/UX design
-- **innovator**: Creative problem solving
-- **documenter**: Documentation generation
-- **debugger**: Systematic debugging
-- **tester**: Comprehensive testing
-- **memory-manager**: Knowledge management
-
-## Usage
-
-### Option 1: Using MCP Tools (Preferred in Claude Code)
-```javascript
-// Execute SPARC mode directly
-mcp__claude-flow__sparc_mode {
-  mode: "<mode>",
-  task_description: "<task>",
-  options: {
-    // mode-specific options
-  }
-}
-
-// Initialize swarm for advanced coordination
-mcp__claude-flow__swarm_init {
-  topology: "hierarchical",
-  strategy: "auto",
-  maxAgents: 8
-}
-
-// Spawn specialized agents
-mcp__claude-flow__agent_spawn {
-  type: "<agent-type>",
-  capabilities: ["<capability1>", "<capability2>"]
-}
-
-// Monitor execution
-mcp__claude-flow__swarm_monitor {
-  swarmId: "current",
-  interval: 5000
-}
-```
-
-### 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 <mode> "task description"
-
-# For alpha features
-npx claude-flow@alpha sparc run <mode> "task description"
-
-# List all modes
-npx claude-flow sparc modes
-
-# Get help for a mode
-npx claude-flow sparc help <mode>
-
-# Run with options
-npx claude-flow sparc run <mode> "task" --parallel --monitor
-```
-
-### Option 3: Local Installation
-```bash
-# If claude-flow is installed locally
-./claude-flow sparc run <mode> "task description"
-```
-
-## Common Workflows
-
-### Full Development Cycle
-
-#### Using MCP Tools (Preferred)
-```javascript
-// 1. Initialize development swarm
-mcp__claude-flow__swarm_init {
-  topology: "hierarchical",
-  maxAgents: 12
-}
-
-// 2. Architecture design
-mcp__claude-flow__sparc_mode {
-  mode: "architect",
-  task_description: "design microservices"
-}
-
-// 3. Implementation
-mcp__claude-flow__sparc_mode {
-  mode: "coder",
-  task_description: "implement services"
-}
-
-// 4. Testing
-mcp__claude-flow__sparc_mode {
-  mode: "tdd",
-  task_description: "test all services"
-}
-
-// 5. Review
-mcp__claude-flow__sparc_mode {
-  mode: "reviewer",
-  task_description: "review implementation"
-}
-```
-
-#### Using NPX CLI (Fallback)
-```bash
-# 1. Architecture design
-npx claude-flow sparc run architect "design microservices"
-
-# 2. Implementation
-npx claude-flow sparc run coder "implement services"
-
-# 3. Testing
-npx claude-flow sparc run tdd "test all services"
-
-# 4. Review
-npx claude-flow sparc run reviewer "review implementation"
-```
-
-### Research and Innovation
-
-#### Using MCP Tools (Preferred)
-```javascript
-// 1. Research phase
-mcp__claude-flow__sparc_mode {
-  mode: "researcher",
-  task_description: "research best practices"
-}
-
-// 2. Innovation
-mcp__claude-flow__sparc_mode {
-  mode: "innovator",
-  task_description: "propose novel solutions"
-}
-
-// 3. Documentation
-mcp__claude-flow__sparc_mode {
-  mode: "documenter",
-  task_description: "document findings"
-}
-```
-
-#### Using NPX CLI (Fallback)
-```bash
-# 1. Research phase
-npx claude-flow sparc run researcher "research best practices"
-
-# 2. Innovation
-npx claude-flow sparc run innovator "propose novel solutions"
-
-# 3. Documentation
-npx claude-flow sparc run documenter "document findings"
-```

package/.claude/commands/stream-chain/pipeline.md

@@ -1,121 +0,0 @@
-# stream-chain pipeline
-
-Execute predefined pipelines for common development workflows.
-
-## Usage
-
-```bash
-claude-flow stream-chain pipeline <type> [options]
-```
-
-## Available Pipelines
-
-### analysis
-Code analysis and improvement pipeline.
-
-```bash
-claude-flow stream-chain pipeline analysis
-```
-
-**Steps:**
-1. Analyze current directory structure and identify main components
-2. Based on analysis, identify potential improvements and issues
-3. Generate detailed report with actionable recommendations
-
-### refactor
-Automated refactoring workflow.
-
-```bash
-claude-flow stream-chain pipeline refactor
-```
-
-**Steps:**
-1. Identify code that could benefit from refactoring
-2. Create prioritized refactoring plan with specific changes
-3. Provide refactored code examples for top 3 priorities
-
-### test
-Comprehensive test generation.
-
-```bash
-claude-flow stream-chain pipeline test
-```
-
-**Steps:**
-1. Analyze codebase and identify areas lacking test coverage
-2. Design comprehensive test cases for critical functions
-3. Generate unit test implementations with assertions
-
-### optimize
-Performance optimization pipeline.
-
-```bash
-claude-flow stream-chain pipeline optimize
-```
-
-**Steps:**
-1. Profile codebase and identify performance bottlenecks
-2. Analyze bottlenecks and suggest optimization strategies
-3. Provide optimized implementations for main issues
-
-## Options
-
-- `--verbose` - Show detailed execution
-- `--timeout <seconds>` - Timeout per step (default: 30)
-- `--debug` - Enable debug mode
-
-## Examples
-
-### Run Analysis Pipeline
-```bash
-claude-flow stream-chain pipeline analysis
-```
-
-### Refactor with Extended Timeout
-```bash
-claude-flow stream-chain pipeline refactor --timeout 60
-```
-
-### Verbose Test Generation
-```bash
-claude-flow stream-chain pipeline test --verbose
-```
-
-### Performance Optimization
-```bash
-claude-flow stream-chain pipeline optimize --debug
-```
-
-## Output
-
-Each pipeline generates:
-- Step-by-step execution progress
-- Success/failure status per step
-- Total execution time
-- Summary of results
-
-## Custom Pipelines
-
-Define custom pipelines in `.claude-flow/config.json`:
-
-```json
-{
-  "streamChain": {
-    "pipelines": {
-      "security": {
-        "name": "Security Audit Pipeline",
-        "prompts": [
-          "Scan for security vulnerabilities",
-          "Prioritize by severity",
-          "Generate fixes"
-        ]
-      }
-    }
-  }
-}
-```
-
-Then run:
-```bash
-claude-flow stream-chain pipeline security
-```

package/.claude/commands/stream-chain/run.md

@@ -1,70 +0,0 @@
-# stream-chain run
-
-Execute a custom stream chain with your own prompts.
-
-## Usage
-
-```bash
-claude-flow stream-chain run <prompt1> <prompt2> [...] [options]
-```
-
-Minimum 2 prompts required for chaining.
-
-## Options
-
-- `--verbose` - Show detailed execution information
-- `--timeout <seconds>` - Timeout per step (default: 30)
-- `--debug` - Enable debug mode
-
-## How It Works
-
-Each prompt in the chain receives the complete output from the previous step as context, enabling complex multi-step workflows.
-
-## Examples
-
-### Basic Chain
-```bash
-claude-flow stream-chain run \
-  "Write a function" \
-  "Add tests for it"
-```
-
-### Complex Workflow
-```bash
-claude-flow stream-chain run \
-  "Analyze the authentication system" \
-  "Identify security vulnerabilities" \
-  "Propose fixes with priority levels" \
-  "Implement the critical fixes" \
-  "Generate tests for the fixes"
-```
-
-### With Options
-```bash
-claude-flow stream-chain run \
-  "Complex analysis task" \
-  "Detailed implementation" \
-  --timeout 60 \
-  --verbose
-```
-
-## Context Preservation
-
-The output from each step is injected into the next prompt:
-
-```
-Step 1: "Write a sorting function"
-Output: [function code]
-
-Step 2 receives: "Previous step output:
-[function code]
-
-Next step: Optimize for performance"
-```
-
-## Best Practices
-
-1. **Clear Instructions**: Make each prompt specific
-2. **Logical Flow**: Order prompts in logical sequence
-3. **Appropriate Timeouts**: Increase for complex tasks
-4. **Verification**: Add verification steps in chain

package/.claude/commands/swarm/analysis.md

@@ -1,95 +0,0 @@
-# Analysis Swarm Strategy
-
-## Purpose
-Comprehensive analysis through distributed agent coordination.
-
-## Activation
-
-### Using MCP Tools
-```javascript
-// Initialize analysis swarm
-mcp__claude-flow__swarm_init({
-  "topology": "mesh",
-  "maxAgents": 6,
-  "strategy": "adaptive"
-})
-
-// Orchestrate analysis task
-mcp__claude-flow__task_orchestrate({
-  "task": "analyze system performance",
-  "strategy": "parallel",
-  "priority": "medium"
-})
-```
-
-### Using CLI (Fallback)
-`npx claude-flow swarm "analyze system performance" --strategy analysis`
-
-## Agent Roles
-
-### Agent Spawning with MCP
-```javascript
-// Spawn analysis agents
-mcp__claude-flow__agent_spawn({
-  "type": "analyst",
-  "name": "Data Collector",
-  "capabilities": ["metrics", "logging", "monitoring"]
-})
-
-mcp__claude-flow__agent_spawn({
-  "type": "analyst",
-  "name": "Pattern Analyzer",
-  "capabilities": ["pattern-recognition", "anomaly-detection"]
-})
-
-mcp__claude-flow__agent_spawn({
-  "type": "documenter",
-  "name": "Report Generator",
-  "capabilities": ["reporting", "visualization"]
-})
-
-mcp__claude-flow__agent_spawn({
-  "type": "coordinator",
-  "name": "Insight Synthesizer",
-  "capabilities": ["synthesis", "correlation"]
-})
-```
-
-## Coordination Modes
-- Mesh: For exploratory analysis
-- Pipeline: For sequential processing
-- Hierarchical: For complex systems
-
-## Analysis Operations
-```javascript
-// Run performance analysis
-mcp__claude-flow__performance_report({
-  "format": "detailed",
-  "timeframe": "24h"
-})
-
-// Identify bottlenecks
-mcp__claude-flow__bottleneck_analyze({
-  "component": "api",
-  "metrics": ["response-time", "throughput"]
-})
-
-// Pattern recognition
-mcp__claude-flow__pattern_recognize({
-  "data": performanceData,
-  "patterns": ["anomaly", "trend", "cycle"]
-})
-```
-
-## Status Monitoring
-```javascript
-// Monitor analysis progress
-mcp__claude-flow__task_status({
-  "taskId": "analysis-task-001"
-})
-
-// Get analysis results
-mcp__claude-flow__task_results({
-  "taskId": "analysis-task-001"
-})
-```

package/.claude/commands/swarm/development.md

@@ -1,96 +0,0 @@
-# Development Swarm Strategy
-
-## Purpose
-Coordinated development through specialized agent teams.
-
-## Activation
-
-### Using MCP Tools
-```javascript
-// Initialize development swarm
-mcp__claude-flow__swarm_init({
-  "topology": "hierarchical",
-  "maxAgents": 8,
-  "strategy": "balanced"
-})
-
-// Orchestrate development task
-mcp__claude-flow__task_orchestrate({
-  "task": "build feature X",
-  "strategy": "parallel",
-  "priority": "high"
-})
-```
-
-### Using CLI (Fallback)
-`npx claude-flow swarm "build feature X" --strategy development`
-
-## Agent Roles
-
-### Agent Spawning with MCP
-```javascript
-// Spawn development agents
-mcp__claude-flow__agent_spawn({
-  "type": "architect",
-  "name": "System Designer",
-  "capabilities": ["system-design", "api-design"]
-})
-
-mcp__claude-flow__agent_spawn({
-  "type": "coder",
-  "name": "Frontend Developer",
-  "capabilities": ["react", "typescript", "ui"]
-})
-
-mcp__claude-flow__agent_spawn({
-  "type": "coder",
-  "name": "Backend Developer",
-  "capabilities": ["nodejs", "api", "database"]
-})
-
-mcp__claude-flow__agent_spawn({
-  "type": "specialist",
-  "name": "Database Expert",
-  "capabilities": ["sql", "nosql", "optimization"]
-})
-
-mcp__claude-flow__agent_spawn({
-  "type": "tester",
-  "name": "Integration Tester",
-  "capabilities": ["integration", "e2e", "api-testing"]
-})
-```
-
-## Best Practices
-- Use hierarchical mode for large projects
-- Enable parallel execution
-- Implement continuous testing
-- Monitor swarm health regularly
-
-## Status Monitoring
-```javascript
-// Check swarm status
-mcp__claude-flow__swarm_status({
-  "swarmId": "development-swarm"
-})
-
-// Monitor agent performance
-mcp__claude-flow__agent_metrics({
-  "agentId": "architect-001"
-})
-
-// Real-time monitoring
-mcp__claude-flow__swarm_monitor({
-  "swarmId": "development-swarm",
-  "interval": 5000
-})
-```
-
-## Error Handling
-```javascript
-// Enable fault tolerance
-mcp__claude-flow__daa_fault_tolerance({
-  "agentId": "all",
-  "strategy": "auto-recovery"
-})
-```