@claude-flow/cli 3.7.0-alpha.1 → 3.7.0-alpha.11

package/.claude/commands/workflows/development.md

@@ -1,78 +1,78 @@
-# Development Workflow Coordination
-
-## Purpose
-Structure Claude Code's approach to complex development tasks for maximum efficiency.
-
-## Step-by-Step Coordination
-
-### 1. Initialize Development Framework
-```
-Tool: mcp__claude-flow__swarm_init
-Parameters: {"topology": "hierarchical", "maxAgents": 8, "strategy": "specialized"}
-```
-Creates hierarchical structure for organized, top-down development.
-
-### 2. Define Development Perspectives
-```
-Tool: mcp__claude-flow__agent_spawn
-Parameters: {
-  "type": "architect",
-  "name": "System Design",
-  "capabilities": ["api-design", "database-schema"]
-}
-```
-```
-Tool: mcp__claude-flow__agent_spawn
-Parameters: {
-  "type": "coder",
-  "name": "Implementation Focus",
-  "capabilities": ["nodejs", "typescript", "express"]
-}
-```
-```
-Tool: mcp__claude-flow__agent_spawn
-Parameters: {
-  "type": "tester",
-  "name": "Quality Assurance",
-  "capabilities": ["unit-testing", "integration-testing"]
-}
-```
-Sets up architectural and implementation thinking patterns.
-
-### 3. Coordinate Implementation
-```
-Tool: mcp__claude-flow__task_orchestrate
-Parameters: {
-  "task": "Build REST API with authentication",
-  "strategy": "parallel",
-  "priority": "high",
-  "dependencies": ["database setup", "auth system"]
-}
-```
-
-### 4. Monitor Progress
-```
-Tool: mcp__claude-flow__task_status
-Parameters: {"taskId": "api-build-task-123"}
-```
-
-## What Claude Code Actually Does
-1. Uses **Write** tool to create new files
-2. Uses **Edit/MultiEdit** tools for code modifications
-3. Uses **Bash** tool for testing and building
-4. Uses **TodoWrite** tool for task tracking
-5. Follows coordination patterns for systematic implementation
-
-Remember: All code is written by Claude Code using its native tools!
-
-## CLI Usage
-```bash
-# Start development workflow via CLI
-npx claude-flow workflow dev "REST API with auth"
-
-# Create custom workflow
-npx claude-flow workflow create --name "api-dev" --steps "design,implement,test,deploy"
-
-# Execute saved workflow
-npx claude-flow workflow execute api-dev
+# Development Workflow Coordination
+
+## Purpose
+Structure Claude Code's approach to complex development tasks for maximum efficiency.
+
+## Step-by-Step Coordination
+
+### 1. Initialize Development Framework
+```
+Tool: mcp__claude-flow__swarm_init
+Parameters: {"topology": "hierarchical", "maxAgents": 8, "strategy": "specialized"}
+```
+Creates hierarchical structure for organized, top-down development.
+
+### 2. Define Development Perspectives
+```
+Tool: mcp__claude-flow__agent_spawn
+Parameters: {
+  "type": "architect",
+  "name": "System Design",
+  "capabilities": ["api-design", "database-schema"]
+}
+```
+```
+Tool: mcp__claude-flow__agent_spawn
+Parameters: {
+  "type": "coder",
+  "name": "Implementation Focus",
+  "capabilities": ["nodejs", "typescript", "express"]
+}
+```
+```
+Tool: mcp__claude-flow__agent_spawn
+Parameters: {
+  "type": "tester",
+  "name": "Quality Assurance",
+  "capabilities": ["unit-testing", "integration-testing"]
+}
+```
+Sets up architectural and implementation thinking patterns.
+
+### 3. Coordinate Implementation
+```
+Tool: mcp__claude-flow__task_orchestrate
+Parameters: {
+  "task": "Build REST API with authentication",
+  "strategy": "parallel",
+  "priority": "high",
+  "dependencies": ["database setup", "auth system"]
+}
+```
+
+### 4. Monitor Progress
+```
+Tool: mcp__claude-flow__task_status
+Parameters: {"taskId": "api-build-task-123"}
+```
+
+## What Claude Code Actually Does
+1. Uses **Write** tool to create new files
+2. Uses **Edit/MultiEdit** tools for code modifications
+3. Uses **Bash** tool for testing and building
+4. Uses **TodoWrite** tool for task tracking
+5. Follows coordination patterns for systematic implementation
+
+Remember: All code is written by Claude Code using its native tools!
+
+## CLI Usage
+```bash
+# Start development workflow via CLI
+npx claude-flow workflow dev "REST API with auth"
+
+# Create custom workflow
+npx claude-flow workflow create --name "api-dev" --steps "design,implement,test,deploy"
+
+# Execute saved workflow
+npx claude-flow workflow execute api-dev
 ```

package/.claude/commands/workflows/research.md

@@ -1,63 +1,63 @@
-# Research Workflow Coordination
-
-## Purpose
-Coordinate Claude Code's research activities for comprehensive, systematic exploration.
-
-## Step-by-Step Coordination
-
-### 1. Initialize Research Framework
-```
-Tool: mcp__claude-flow__swarm_init
-Parameters: {"topology": "mesh", "maxAgents": 5, "strategy": "balanced"}
-```
-Creates a mesh topology for comprehensive exploration from multiple angles.
-
-### 2. Define Research Perspectives
-```
-Tool: mcp__claude-flow__agent_spawn
-Parameters: {"type": "researcher", "name": "Literature Review"}
-```
-```
-Tool: mcp__claude-flow__agent_spawn  
-Parameters: {"type": "analyst", "name": "Data Analysis"}
-```
-Sets up different analytical approaches for Claude Code to use.
-
-### 3. Execute Coordinated Research
-```
-Tool: mcp__claude-flow__task_orchestrate
-Parameters: {
-  "task": "Research modern web frameworks performance",
-  "strategy": "adaptive",
-  "priority": "medium"
-}
-```
-
-### 4. Store Research Findings
-```
-Tool: mcp__claude-flow__memory_usage
-Parameters: {
-  "action": "store",
-  "key": "research_findings",
-  "value": "framework performance analysis results",
-  "namespace": "research"
-}
-```
-
-## What Claude Code Actually Does
-1. Uses **WebSearch** tool for finding resources
-2. Uses **Read** tool for analyzing documentation
-3. Uses **Task** tool for parallel exploration
-4. Synthesizes findings using coordination patterns
-5. Stores insights in memory for future reference
-
-Remember: The swarm coordinates HOW Claude Code researches, not WHAT it finds.
-
-## CLI Usage
-```bash
-# Start research workflow via CLI
-npx claude-flow workflow research "modern web frameworks"
-
-# Export research workflow
-npx claude-flow workflow export research --format json
+# Research Workflow Coordination
+
+## Purpose
+Coordinate Claude Code's research activities for comprehensive, systematic exploration.
+
+## Step-by-Step Coordination
+
+### 1. Initialize Research Framework
+```
+Tool: mcp__claude-flow__swarm_init
+Parameters: {"topology": "mesh", "maxAgents": 5, "strategy": "balanced"}
+```
+Creates a mesh topology for comprehensive exploration from multiple angles.
+
+### 2. Define Research Perspectives
+```
+Tool: mcp__claude-flow__agent_spawn
+Parameters: {"type": "researcher", "name": "Literature Review"}
+```
+```
+Tool: mcp__claude-flow__agent_spawn  
+Parameters: {"type": "analyst", "name": "Data Analysis"}
+```
+Sets up different analytical approaches for Claude Code to use.
+
+### 3. Execute Coordinated Research
+```
+Tool: mcp__claude-flow__task_orchestrate
+Parameters: {
+  "task": "Research modern web frameworks performance",
+  "strategy": "adaptive",
+  "priority": "medium"
+}
+```
+
+### 4. Store Research Findings
+```
+Tool: mcp__claude-flow__memory_usage
+Parameters: {
+  "action": "store",
+  "key": "research_findings",
+  "value": "framework performance analysis results",
+  "namespace": "research"
+}
+```
+
+## What Claude Code Actually Does
+1. Uses **WebSearch** tool for finding resources
+2. Uses **Read** tool for analyzing documentation
+3. Uses **Task** tool for parallel exploration
+4. Synthesizes findings using coordination patterns
+5. Stores insights in memory for future reference
+
+Remember: The swarm coordinates HOW Claude Code researches, not WHAT it finds.
+
+## CLI Usage
+```bash
+# Start research workflow via CLI
+npx claude-flow workflow research "modern web frameworks"
+
+# Export research workflow
+npx claude-flow workflow export research --format json
 ```

package/.claude/commands/workflows/workflow-create.md

@@ -1,25 +1,25 @@
-# workflow-create
-
-Create reusable workflow templates.
-
-## Usage
-```bash
-npx claude-flow workflow create [options]
-```
-
-## Options
-- `--name <name>` - Workflow name
-- `--from-history` - Create from history
-- `--interactive` - Interactive creation
-
-## Examples
-```bash
-# Create workflow
-npx claude-flow workflow create --name "deploy-api"
-
-# From history
-npx claude-flow workflow create --name "test-suite" --from-history
-
-# Interactive mode
-npx claude-flow workflow create --interactive
-```
+# workflow-create
+
+Create reusable workflow templates.
+
+## Usage
+```bash
+npx claude-flow workflow create [options]
+```
+
+## Options
+- `--name <name>` - Workflow name
+- `--from-history` - Create from history
+- `--interactive` - Interactive creation
+
+## Examples
+```bash
+# Create workflow
+npx claude-flow workflow create --name "deploy-api"
+
+# From history
+npx claude-flow workflow create --name "test-suite" --from-history
+
+# Interactive mode
+npx claude-flow workflow create --interactive
+```

package/.claude/commands/workflows/workflow-execute.md

@@ -1,25 +1,25 @@
-# workflow-execute
-
-Execute saved workflows.
-
-## Usage
-```bash
-npx claude-flow workflow execute [options]
-```
-
-## Options
-- `--name <name>` - Workflow name
-- `--params <json>` - Workflow parameters
-- `--dry-run` - Preview execution
-
-## Examples
-```bash
-# Execute workflow
-npx claude-flow workflow execute --name "deploy-api"
-
-# With parameters
-npx claude-flow workflow execute --name "test-suite" --params '{"env": "staging"}'
-
-# Dry run
-npx claude-flow workflow execute --name "deploy-api" --dry-run
-```
+# workflow-execute
+
+Execute saved workflows.
+
+## Usage
+```bash
+npx claude-flow workflow execute [options]
+```
+
+## Options
+- `--name <name>` - Workflow name
+- `--params <json>` - Workflow parameters
+- `--dry-run` - Preview execution
+
+## Examples
+```bash
+# Execute workflow
+npx claude-flow workflow execute --name "deploy-api"
+
+# With parameters
+npx claude-flow workflow execute --name "test-suite" --params '{"env": "staging"}'
+
+# Dry run
+npx claude-flow workflow execute --name "deploy-api" --dry-run
+```

package/.claude/commands/workflows/workflow-export.md

@@ -1,25 +1,25 @@
-# workflow-export
-
-Export workflows for sharing.
-
-## Usage
-```bash
-npx claude-flow workflow export [options]
-```
-
-## Options
-- `--name <name>` - Workflow to export
-- `--format <type>` - Export format
-- `--include-history` - Include execution history
-
-## Examples
-```bash
-# Export workflow
-npx claude-flow workflow export --name "deploy-api"
-
-# As YAML
-npx claude-flow workflow export --name "test-suite" --format yaml
-
-# With history
-npx claude-flow workflow export --name "deploy-api" --include-history
-```
+# workflow-export
+
+Export workflows for sharing.
+
+## Usage
+```bash
+npx claude-flow workflow export [options]
+```
+
+## Options
+- `--name <name>` - Workflow to export
+- `--format <type>` - Export format
+- `--include-history` - Include execution history
+
+## Examples
+```bash
+# Export workflow
+npx claude-flow workflow export --name "deploy-api"
+
+# As YAML
+npx claude-flow workflow export --name "test-suite" --format yaml
+
+# With history
+npx claude-flow workflow export --name "deploy-api" --include-history
+```

package/.claude/helpers/README.md

@@ -1,97 +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
+# 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