@sparkleideas/mcp 3.0.0-alpha.9

package/.claude/commands/sparc/swarm-coordinator.md

@@ -0,0 +1,54 @@
+# SPARC Swarm Coordinator Mode
+
+## Purpose
+Specialized swarm management with batch coordination capabilities.
+
+## Activation
+
+### Option 1: Using MCP Tools (Preferred in Claude Code)
+```javascript
+mcp__claude-flow__sparc_mode {
+  mode: "swarm-coordinator",
+  task_description: "manage development swarm",
+  options: {
+    topology: "hierarchical",
+    max_agents: 10
+  }
+}
+```
+
+### 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 swarm-coordinator "manage development swarm"
+
+# For alpha features
+npx claude-flow@alpha sparc run swarm-coordinator "manage development swarm"
+```
+
+### Option 3: Local Installation
+```bash
+# If claude-flow is installed locally
+./claude-flow sparc run swarm-coordinator "manage development swarm"
+```
+
+## Core Capabilities
+- Swarm initialization
+- Agent management
+- Task distribution
+- Load balancing
+- Result collection
+
+## Coordination Modes
+- Hierarchical swarms
+- Mesh networks
+- Pipeline coordination
+- Adaptive strategies
+- Hybrid approaches
+
+## Management Features
+- Dynamic scaling
+- Resource optimization
+- Failure recovery
+- Performance monitoring
+- Quality assurance

package/.claude/commands/sparc/tdd.md

@@ -0,0 +1,54 @@
+# SPARC TDD Mode
+
+## Purpose
+Test-driven development with TodoWrite planning and comprehensive testing.
+
+## Activation
+
+### Option 1: Using MCP Tools (Preferred in Claude Code)
+```javascript
+mcp__claude-flow__sparc_mode {
+  mode: "tdd",
+  task_description: "shopping cart feature",
+  options: {
+    coverage_target: 90,
+    test_framework: "jest"
+  }
+}
+```
+
+### 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 tdd "shopping cart feature"
+
+# For alpha features
+npx claude-flow@alpha sparc run tdd "shopping cart feature"
+```
+
+### Option 3: Local Installation
+```bash
+# If claude-flow is installed locally
+./claude-flow sparc run tdd "shopping cart feature"
+```
+
+## Core Capabilities
+- Test-first development
+- Red-green-refactor cycle
+- Test suite design
+- Coverage optimization
+- Continuous testing
+
+## TDD Workflow
+1. Write failing tests
+2. Implement minimum code
+3. Make tests pass
+4. Refactor code
+5. Repeat cycle
+
+## Testing Strategies
+- Unit testing
+- Integration testing
+- End-to-end testing
+- Performance testing
+- Security testing

package/.claude/commands/sparc/tester.md

@@ -0,0 +1,54 @@
+# SPARC Tester Mode
+
+## Purpose
+Comprehensive testing with parallel execution capabilities.
+
+## Activation
+
+### Option 1: Using MCP Tools (Preferred in Claude Code)
+```javascript
+mcp__claude-flow__sparc_mode {
+  mode: "tester",
+  task_description: "full regression suite",
+  options: {
+    parallel: true,
+    coverage: 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 tester "full regression suite"
+
+# For alpha features
+npx claude-flow@alpha sparc run tester "full regression suite"
+```
+
+### Option 3: Local Installation
+```bash
+# If claude-flow is installed locally
+./claude-flow sparc run tester "full regression suite"
+```
+
+## Core Capabilities
+- Test planning
+- Test execution
+- Bug detection
+- Coverage analysis
+- Report generation
+
+## Test Types
+- Unit tests
+- Integration tests
+- E2E tests
+- Performance tests
+- Security tests
+
+## Parallel Features
+- Concurrent test runs
+- Distributed testing
+- Load testing
+- Cross-browser testing
+- Multi-environment validation

package/.claude/commands/sparc/tutorial.md

@@ -0,0 +1,79 @@
+---
+name: sparc-tutorial
+description: 📘 SPARC Tutorial - You are the SPARC onboarding and education assistant. Your job is to guide users through the full...
+---
+
+# 📘 SPARC Tutorial
+
+## Role Definition
+You are the SPARC onboarding and education assistant. Your job is to guide users through the full SPARC development process using structured thinking models. You help users understand how to navigate complex projects using the specialized SPARC modes and properly formulate tasks using new_task.
+
+## Custom Instructions
+You teach developers how to apply the SPARC methodology through actionable examples and mental models.
+
+## Available Tools
+- **read**: File reading and viewing
+
+## Usage
+
+### Option 1: Using MCP Tools (Preferred in Claude Code)
+```javascript
+mcp__claude-flow__sparc_mode {
+  mode: "tutorial",
+  task_description: "guide me through SPARC methodology",
+  options: {
+    namespace: "tutorial",
+    non_interactive: false
+  }
+}
+```
+
+### 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 tutorial "guide me through SPARC methodology"
+
+# For alpha features
+npx claude-flow@alpha sparc run tutorial "guide me through SPARC methodology"
+
+# With namespace
+npx claude-flow sparc run tutorial "your task" --namespace tutorial
+
+# Non-interactive mode
+npx claude-flow sparc run tutorial "your task" --non-interactive
+```
+
+### Option 3: Local Installation
+```bash
+# If claude-flow is installed locally
+./claude-flow sparc run tutorial "guide me through SPARC methodology"
+```
+
+## Memory Integration
+
+### Using MCP Tools (Preferred)
+```javascript
+// Store mode-specific context
+mcp__claude-flow__memory_usage {
+  action: "store",
+  key: "tutorial_context",
+  value: "important decisions",
+  namespace: "tutorial"
+}
+
+// Query previous work
+mcp__claude-flow__memory_search {
+  pattern: "tutorial",
+  namespace: "tutorial",
+  limit: 5
+}
+```
+
+### Using NPX CLI (Fallback)
+```bash
+# Store mode-specific context
+npx claude-flow memory store "tutorial_context" "important decisions" --namespace tutorial
+
+# Query previous work
+npx claude-flow memory query "tutorial" --limit 5
+```

package/.claude/commands/sparc/workflow-manager.md

@@ -0,0 +1,54 @@
+# SPARC Workflow Manager Mode
+
+## Purpose
+Process automation with TodoWrite planning and Task execution.
+
+## Activation
+
+### Option 1: Using MCP Tools (Preferred in Claude Code)
+```javascript
+mcp__claude-flow__sparc_mode {
+  mode: "workflow-manager",
+  task_description: "automate deployment",
+  options: {
+    pipeline: "ci-cd",
+    rollback_enabled: 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 workflow-manager "automate deployment"
+
+# For alpha features
+npx claude-flow@alpha sparc run workflow-manager "automate deployment"
+```
+
+### Option 3: Local Installation
+```bash
+# If claude-flow is installed locally
+./claude-flow sparc run workflow-manager "automate deployment"
+```
+
+## Core Capabilities
+- Workflow design
+- Process automation
+- Pipeline creation
+- Event handling
+- State management
+
+## Workflow Patterns
+- Sequential flows
+- Parallel branches
+- Conditional logic
+- Loop iterations
+- Error handling
+
+## Automation Features
+- Trigger management
+- Task scheduling
+- Progress tracking
+- Result validation
+- Rollback capability

package/.claude/helpers/README.md

@@ -0,0 +1,97 @@
+# Claude Flow V3 Helpers
+
+This directory contains helper scripts and utilities for V3 development.
+
+## 🚀 Quick Start
+
+```bash
+# Initialize V3 development environment
+.claude/helpers/v3.sh init
+
+# Quick status check
+.claude/helpers/v3.sh status
+
+# Update progress metrics
+.claude/helpers/v3.sh update domain 3
+.claude/helpers/v3.sh update agent 8
+.claude/helpers/v3.sh update security 2
+```
+
+## Available Helpers
+
+### 🎛️ V3 Master Tool
+- **`v3.sh`** - Main command-line interface for all V3 operations
+  ```bash
+  .claude/helpers/v3.sh help           # Show all commands
+  .claude/helpers/v3.sh status         # Quick development status
+  .claude/helpers/v3.sh update domain 3 # Update specific metrics
+  .claude/helpers/v3.sh validate       # Validate configuration
+  .claude/helpers/v3.sh full-status    # Complete status overview
+  ```
+
+### 📊 V3 Progress Management
+- **`update-v3-progress.sh`** - Update V3 development metrics
+  ```bash
+  # Usage examples:
+  .claude/helpers/update-v3-progress.sh domain 3      # Mark 3 domains complete
+  .claude/helpers/update-v3-progress.sh agent 8       # 8 agents active
+  .claude/helpers/update-v3-progress.sh security 2    # 2 CVEs fixed
+  .claude/helpers/update-v3-progress.sh performance 2.5x # Performance boost
+  .claude/helpers/update-v3-progress.sh status        # Show current status
+  ```
+
+### 🔍 Configuration Validation
+- **`validate-v3-config.sh`** - Comprehensive environment validation
+  - Checks all required directories and files
+  - Validates JSON configuration files
+  - Verifies Node.js and development tools
+  - Confirms Git repository status
+  - Validates file permissions
+
+### ⚡ Quick Status
+- **`v3-quick-status.sh`** - Compact development progress overview
+  - Shows domain, agent, and DDD progress
+  - Displays security and performance metrics
+  - Color-coded status indicators
+  - Current Git branch information
+
+## Helper Script Standards
+
+### File Naming
+- Use kebab-case: `update-v3-progress.sh`
+- Include version prefix: `v3-*` for V3-specific helpers
+- Use descriptive names that indicate purpose
+
+### Script Requirements
+- Must be executable (`chmod +x`)
+- Include proper error handling (`set -e`)
+- Provide usage help when called without arguments
+- Use consistent exit codes (0 = success, non-zero = error)
+
+### Configuration Integration
+Helpers are configured in `.claude/settings.json`:
+```json
+{
+  "helpers": {
+    "directory": ".claude/helpers",
+    "enabled": true,
+    "v3ProgressUpdater": ".claude/helpers/update-v3-progress.sh"
+  }
+}
+```
+
+## Development Guidelines
+
+1. **Security First**: All helpers must validate inputs
+2. **Idempotent**: Scripts should be safe to run multiple times
+3. **Fast Execution**: Keep helper execution under 1 second when possible
+4. **Clear Output**: Provide clear success/error messages
+5. **JSON Safe**: When updating JSON files, use `jq` for safety
+
+## Adding New Helpers
+
+1. Create script in `.claude/helpers/`
+2. Make executable: `chmod +x script-name.sh`
+3. Add to settings.json helpers section
+4. Test thoroughly before committing
+5. Update this README with usage documentation

package/.claude/helpers/adr-compliance.sh

@@ -0,0 +1,186 @@
+#!/bin/bash
+# Claude Flow V3 - ADR Compliance Checker Worker
+# Checks compliance with Architecture Decision Records
+
+set -euo pipefail
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+PROJECT_ROOT="$(cd "$SCRIPT_DIR/../.." && pwd)"
+METRICS_DIR="$PROJECT_ROOT/.claude-flow/metrics"
+ADR_FILE="$METRICS_DIR/adr-compliance.json"
+LAST_RUN_FILE="$METRICS_DIR/.adr-last-run"
+
+mkdir -p "$METRICS_DIR"
+
+# V3 ADRs to check
+declare -A ADRS=(
+  ["ADR-001"]="agentic-flow as core foundation"
+  ["ADR-002"]="Domain-Driven Design structure"
+  ["ADR-003"]="Single coordination engine"
+  ["ADR-004"]="Plugin-based architecture"
+  ["ADR-005"]="MCP-first API design"
+  ["ADR-006"]="Unified memory service"
+  ["ADR-007"]="Event sourcing for state"
+  ["ADR-008"]="Vitest over Jest"
+  ["ADR-009"]="Hybrid memory backend"
+  ["ADR-010"]="Remove Deno support"
+)
+
+should_run() {
+  if [ ! -f "$LAST_RUN_FILE" ]; then return 0; fi
+  local last_run=$(cat "$LAST_RUN_FILE" 2>/dev/null || echo "0")
+  local now=$(date +%s)
+  [ $((now - last_run)) -ge 900 ]  # 15 minutes
+}
+
+check_adr_001() {
+  # ADR-001: agentic-flow as core foundation
+  local score=0
+
+  # Check package.json for agentic-flow dependency
+  grep -q "agentic-flow" "$PROJECT_ROOT/package.json" 2>/dev/null && score=$((score + 50))
+
+  # Check for imports from agentic-flow
+  local imports=$(grep -r "from.*agentic-flow\|require.*agentic-flow" "$PROJECT_ROOT/v3" "$PROJECT_ROOT/src" 2>/dev/null | grep -v node_modules | wc -l)
+  [ "$imports" -gt 5 ] && score=$((score + 50))
+
+  echo "$score"
+}
+
+check_adr_002() {
+  # ADR-002: Domain-Driven Design structure
+  local score=0
+
+  # Check for domain directories
+  [ -d "$PROJECT_ROOT/v3" ] || [ -d "$PROJECT_ROOT/src/domains" ] && score=$((score + 30))
+
+  # Check for bounded contexts
+  local contexts=$(find "$PROJECT_ROOT/v3" "$PROJECT_ROOT/src" -type d -name "domain" 2>/dev/null | wc -l)
+  [ "$contexts" -gt 0 ] && score=$((score + 35))
+
+  # Check for anti-corruption layers
+  local acl=$(grep -r "AntiCorruption\|Adapter\|Port" "$PROJECT_ROOT/v3" "$PROJECT_ROOT/src" 2>/dev/null | grep -v node_modules | wc -l)
+  [ "$acl" -gt 0 ] && score=$((score + 35))
+
+  echo "$score"
+}
+
+check_adr_003() {
+  # ADR-003: Single coordination engine
+  local score=0
+
+  # Check for unified SwarmCoordinator
+  grep -rq "SwarmCoordinator\|UnifiedCoordinator" "$PROJECT_ROOT/v3" "$PROJECT_ROOT/src" 2>/dev/null && score=$((score + 50))
+
+  # Check for no duplicate coordinators
+  local coordinators=$(grep -r "class.*Coordinator" "$PROJECT_ROOT/v3" "$PROJECT_ROOT/src" 2>/dev/null | grep -v node_modules | grep -v ".test." | wc -l)
+  [ "$coordinators" -le 3 ] && score=$((score + 50))
+
+  echo "$score"
+}
+
+check_adr_005() {
+  # ADR-005: MCP-first API design
+  local score=0
+
+  # Check for MCP server implementation
+  [ -d "$PROJECT_ROOT/v3/@claude-flow/mcp" ] && score=$((score + 40))
+
+  # Check for MCP tools
+  local tools=$(grep -r "tool.*name\|registerTool" "$PROJECT_ROOT/v3" 2>/dev/null | wc -l)
+  [ "$tools" -gt 5 ] && score=$((score + 30))
+
+  # Check for MCP schemas
+  grep -rq "schema\|jsonSchema" "$PROJECT_ROOT/v3/@claude-flow/mcp" 2>/dev/null && score=$((score + 30))
+
+  echo "$score"
+}
+
+check_adr_008() {
+  # ADR-008: Vitest over Jest
+  local score=0
+
+  # Check for vitest in package.json
+  grep -q "vitest" "$PROJECT_ROOT/package.json" 2>/dev/null && score=$((score + 50))
+
+  # Check for no jest references
+  local jest_refs=$(grep -r "from.*jest\|jest\." "$PROJECT_ROOT/v3" "$PROJECT_ROOT/src" 2>/dev/null | grep -v node_modules | grep -v "vitest" | wc -l)
+  [ "$jest_refs" -eq 0 ] && score=$((score + 50))
+
+  echo "$score"
+}
+
+check_compliance() {
+  echo "[$(date +%H:%M:%S)] Checking ADR compliance..."
+
+  local total_score=0
+  local compliant_count=0
+  local results=""
+
+  # Check each ADR
+  local adr_001=$(check_adr_001)
+  local adr_002=$(check_adr_002)
+  local adr_003=$(check_adr_003)
+  local adr_005=$(check_adr_005)
+  local adr_008=$(check_adr_008)
+
+  # Simple checks for others (assume partial compliance)
+  local adr_004=50  # Plugin architecture
+  local adr_006=50  # Unified memory
+  local adr_007=50  # Event sourcing
+  local adr_009=75  # Hybrid memory
+  local adr_010=100 # No Deno (easy to verify)
+
+  # Calculate totals
+  for score in $adr_001 $adr_002 $adr_003 $adr_004 $adr_005 $adr_006 $adr_007 $adr_008 $adr_009 $adr_010; do
+    total_score=$((total_score + score))
+    [ "$score" -ge 50 ] && compliant_count=$((compliant_count + 1))
+  done
+
+  local avg_score=$((total_score / 10))
+
+  # Write ADR compliance metrics
+  cat > "$ADR_FILE" << EOF
+{
+  "timestamp": "$(date -Iseconds)",
+  "overallCompliance": $avg_score,
+  "compliantCount": $compliant_count,
+  "totalADRs": 10,
+  "adrs": {
+    "ADR-001": {"score": $adr_001, "title": "agentic-flow as core foundation"},
+    "ADR-002": {"score": $adr_002, "title": "Domain-Driven Design structure"},
+    "ADR-003": {"score": $adr_003, "title": "Single coordination engine"},
+    "ADR-004": {"score": $adr_004, "title": "Plugin-based architecture"},
+    "ADR-005": {"score": $adr_005, "title": "MCP-first API design"},
+    "ADR-006": {"score": $adr_006, "title": "Unified memory service"},
+    "ADR-007": {"score": $adr_007, "title": "Event sourcing for state"},
+    "ADR-008": {"score": $adr_008, "title": "Vitest over Jest"},
+    "ADR-009": {"score": $adr_009, "title": "Hybrid memory backend"},
+    "ADR-010": {"score": $adr_010, "title": "Remove Deno support"}
+  }
+}
+EOF
+
+  echo "[$(date +%H:%M:%S)] ✓ ADR Compliance: ${avg_score}% | Compliant: $compliant_count/10"
+
+  date +%s > "$LAST_RUN_FILE"
+}
+
+case "${1:-check}" in
+  "run") check_compliance ;;
+  "check") should_run && check_compliance || echo "[$(date +%H:%M:%S)] Skipping (throttled)" ;;
+  "force") rm -f "$LAST_RUN_FILE"; check_compliance ;;
+  "status")
+    if [ -f "$ADR_FILE" ]; then
+      jq -r '"Compliance: \(.overallCompliance)% | Compliant: \(.compliantCount)/\(.totalADRs)"' "$ADR_FILE"
+    else
+      echo "No ADR data available"
+    fi
+    ;;
+  "details")
+    if [ -f "$ADR_FILE" ]; then
+      jq -r '.adrs | to_entries[] | "\(.key): \(.value.score)% - \(.value.title)"' "$ADR_FILE"
+    fi
+    ;;
+  *) echo "Usage: $0 [run|check|force|status|details]" ;;
+esac