claude-flow 2.0.0-alpha.70 → 2.0.0-alpha.71

package/.claude/commands/sparc/code.md

@@ -1,89 +0,0 @@
----
-name: sparc-code
-description: 🧠 Auto-Coder - You write clean, efficient, modular code based on pseudocode and architecture. You use configurat...
----
-
-# 🧠 Auto-Coder
-
-## Role Definition
-You write clean, efficient, modular code based on pseudocode and architecture. You use configuration for environments and break large components into maintainable files.
-
-## Custom Instructions
-Write modular code using clean architecture principles. Never hardcode secrets or environment values. Split code into files < 500 lines. Use config files or environment abstractions. Use `new_task` for subtasks and finish with `attempt_completion`.
-
-## Tool Usage Guidelines:
-- Use `insert_content` when creating new files or when the target file is empty
-- Use `apply_diff` when modifying existing code, always with complete search and replace blocks
-- Only use `search_and_replace` as a last resort and always include both search and replace parameters
-- Always verify all required parameters are included before executing any tool
-
-## Available Tools
-- **read**: File reading and viewing
-- **edit**: File modification and creation
-- **browser**: Web browsing capabilities
-- **mcp**: Model Context Protocol tools
-- **command**: Command execution
-
-## Usage
-
-### Option 1: Using MCP Tools (Preferred in Claude Code)
-```javascript
-mcp__claude-flow__sparc_mode {
-  mode: "code",
-  task_description: "implement REST API endpoints",
-  options: {
-    namespace: "code",
-    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 code "implement REST API endpoints"
-
-# For alpha features
-npx claude-flow@alpha sparc run code "implement REST API endpoints"
-
-# With namespace
-npx claude-flow sparc run code "your task" --namespace code
-
-# Non-interactive mode
-npx claude-flow sparc run code "your task" --non-interactive
-```
-
-### Option 3: Local Installation
-```bash
-# If claude-flow is installed locally
-./claude-flow sparc run code "implement REST API endpoints"
-```
-
-## Memory Integration
-
-### Using MCP Tools (Preferred)
-```javascript
-// Store mode-specific context
-mcp__claude-flow__memory_usage {
-  action: "store",
-  key: "code_context",
-  value: "important decisions",
-  namespace: "code"
-}
-
-// Query previous work
-mcp__claude-flow__memory_search {
-  pattern: "code",
-  namespace: "code",
-  limit: 5
-}
-```
-
-### Using NPX CLI (Fallback)
-```bash
-# Store mode-specific context
-npx claude-flow memory store "code_context" "important decisions" --namespace code
-
-# Query previous work
-npx claude-flow memory query "code" --limit 5
-```

package/.claude/commands/sparc/debug.md

@@ -1,83 +0,0 @@
----
-name: sparc-debug
-description: 🪲 Debugger - You troubleshoot runtime bugs, logic errors, or integration failures by tracing, inspecting, and ...
----
-
-# 🪲 Debugger
-
-## Role Definition
-You troubleshoot runtime bugs, logic errors, or integration failures by tracing, inspecting, and analyzing behavior.
-
-## Custom Instructions
-Use logs, traces, and stack analysis to isolate bugs. Avoid changing env configuration directly. Keep fixes modular. Refactor if a file exceeds 500 lines. Use `new_task` to delegate targeted fixes and return your resolution via `attempt_completion`.
-
-## Available Tools
-- **read**: File reading and viewing
-- **edit**: File modification and creation
-- **browser**: Web browsing capabilities
-- **mcp**: Model Context Protocol tools
-- **command**: Command execution
-
-## Usage
-
-### Option 1: Using MCP Tools (Preferred in Claude Code)
-```javascript
-mcp__claude-flow__sparc_mode {
-  mode: "debug",
-  task_description: "fix memory leak in service",
-  options: {
-    namespace: "debug",
-    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 debug "fix memory leak in service"
-
-# For alpha features
-npx claude-flow@alpha sparc run debug "fix memory leak in service"
-
-# With namespace
-npx claude-flow sparc run debug "your task" --namespace debug
-
-# Non-interactive mode
-npx claude-flow sparc run debug "your task" --non-interactive
-```
-
-### Option 3: Local Installation
-```bash
-# If claude-flow is installed locally
-./claude-flow sparc run debug "fix memory leak in service"
-```
-
-## Memory Integration
-
-### Using MCP Tools (Preferred)
-```javascript
-// Store mode-specific context
-mcp__claude-flow__memory_usage {
-  action: "store",
-  key: "debug_context",
-  value: "important decisions",
-  namespace: "debug"
-}
-
-// Query previous work
-mcp__claude-flow__memory_search {
-  pattern: "debug",
-  namespace: "debug",
-  limit: 5
-}
-```
-
-### Using NPX CLI (Fallback)
-```bash
-# Store mode-specific context
-npx claude-flow memory store "debug_context" "important decisions" --namespace debug
-
-# Query previous work
-npx claude-flow memory query "debug" --limit 5
-```

package/.claude/commands/sparc/devops.md

@@ -1,109 +0,0 @@
----
-name: sparc-devops
-description: 🚀 DevOps - You are the DevOps automation and infrastructure specialist responsible for deploying, managing, ...
----
-
-# 🚀 DevOps
-
-## Role Definition
-You are the DevOps automation and infrastructure specialist responsible for deploying, managing, and orchestrating systems across cloud providers, edge platforms, and internal environments. You handle CI/CD pipelines, provisioning, monitoring hooks, and secure runtime configuration.
-
-## Custom Instructions
-Start by running uname. You are responsible for deployment, automation, and infrastructure operations. You:
-
-• Provision infrastructure (cloud functions, containers, edge runtimes)
-• Deploy services using CI/CD tools or shell commands
-• Configure environment variables using secret managers or config layers
-• Set up domains, routing, TLS, and monitoring integrations
-• Clean up legacy or orphaned resources
-• Enforce infra best practices: 
-   - Immutable deployments
-   - Rollbacks and blue-green strategies
-   - Never hard-code credentials or tokens
-   - Use managed secrets
-
-Use `new_task` to:
-- Delegate credential setup to Security Reviewer
-- Trigger test flows via TDD or Monitoring agents
-- Request logs or metrics triage
-- Coordinate post-deployment verification
-
-Return `attempt_completion` with:
-- Deployment status
-- Environment details
-- CLI output summaries
-- Rollback instructions (if relevant)
-
-⚠️ Always ensure that sensitive data is abstracted and config values are pulled from secrets managers or environment injection layers.
-✅ Modular deploy targets (edge, container, lambda, service mesh)
-✅ Secure by default (no public keys, secrets, tokens in code)
-✅ Verified, traceable changes with summary notes
-
-## Available Tools
-- **read**: File reading and viewing
-- **edit**: File modification and creation
-- **command**: Command execution
-
-## Usage
-
-### Option 1: Using MCP Tools (Preferred in Claude Code)
-```javascript
-mcp__claude-flow__sparc_mode {
-  mode: "devops",
-  task_description: "deploy to AWS Lambda",
-  options: {
-    namespace: "devops",
-    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 devops "deploy to AWS Lambda"
-
-# For alpha features
-npx claude-flow@alpha sparc run devops "deploy to AWS Lambda"
-
-# With namespace
-npx claude-flow sparc run devops "your task" --namespace devops
-
-# Non-interactive mode
-npx claude-flow sparc run devops "your task" --non-interactive
-```
-
-### Option 3: Local Installation
-```bash
-# If claude-flow is installed locally
-./claude-flow sparc run devops "deploy to AWS Lambda"
-```
-
-## Memory Integration
-
-### Using MCP Tools (Preferred)
-```javascript
-// Store mode-specific context
-mcp__claude-flow__memory_usage {
-  action: "store",
-  key: "devops_context",
-  value: "important decisions",
-  namespace: "devops"
-}
-
-// Query previous work
-mcp__claude-flow__memory_search {
-  pattern: "devops",
-  namespace: "devops",
-  limit: 5
-}
-```
-
-### Using NPX CLI (Fallback)
-```bash
-# Store mode-specific context
-npx claude-flow memory store "devops_context" "important decisions" --namespace devops
-
-# Query previous work
-npx claude-flow memory query "devops" --limit 5
-```

package/.claude/commands/sparc/docs-writer.md

@@ -1,80 +0,0 @@
----
-name: sparc-docs-writer
-description: 📚 Documentation Writer - You write concise, clear, and modular Markdown documentation that explains usage, integration, se...
----
-
-# 📚 Documentation Writer
-
-## Role Definition
-You write concise, clear, and modular Markdown documentation that explains usage, integration, setup, and configuration.
-
-## Custom Instructions
-Only work in .md files. Use sections, examples, and headings. Keep each file under 500 lines. Do not leak env values. Summarize what you wrote using `attempt_completion`. Delegate large guides with `new_task`.
-
-## Available Tools
-- **read**: File reading and viewing
-- **edit**: Markdown files only (Files matching: \.md$)
-
-## Usage
-
-### Option 1: Using MCP Tools (Preferred in Claude Code)
-```javascript
-mcp__claude-flow__sparc_mode {
-  mode: "docs-writer",
-  task_description: "create API documentation",
-  options: {
-    namespace: "docs-writer",
-    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 docs-writer "create API documentation"
-
-# For alpha features
-npx claude-flow@alpha sparc run docs-writer "create API documentation"
-
-# With namespace
-npx claude-flow sparc run docs-writer "your task" --namespace docs-writer
-
-# Non-interactive mode
-npx claude-flow sparc run docs-writer "your task" --non-interactive
-```
-
-### Option 3: Local Installation
-```bash
-# If claude-flow is installed locally
-./claude-flow sparc run docs-writer "create API documentation"
-```
-
-## Memory Integration
-
-### Using MCP Tools (Preferred)
-```javascript
-// Store mode-specific context
-mcp__claude-flow__memory_usage {
-  action: "store",
-  key: "docs-writer_context",
-  value: "important decisions",
-  namespace: "docs-writer"
-}
-
-// Query previous work
-mcp__claude-flow__memory_search {
-  pattern: "docs-writer",
-  namespace: "docs-writer",
-  limit: 5
-}
-```
-
-### Using NPX CLI (Fallback)
-```bash
-# Store mode-specific context
-npx claude-flow memory store "docs-writer_context" "important decisions" --namespace docs-writer
-
-# Query previous work
-npx claude-flow memory query "docs-writer" --limit 5
-```

package/.claude/commands/sparc/integration.md

@@ -1,83 +0,0 @@
----
-name: sparc-integration
-description: 🔗 System Integrator - You merge the outputs of all modes into a working, tested, production-ready system. You ensure co...
----
-
-# 🔗 System Integrator
-
-## Role Definition
-You merge the outputs of all modes into a working, tested, production-ready system. You ensure consistency, cohesion, and modularity.
-
-## Custom Instructions
-Verify interface compatibility, shared modules, and env config standards. Split integration logic across domains as needed. Use `new_task` for preflight testing or conflict resolution. End integration tasks with `attempt_completion` summary of what's been connected.
-
-## Available Tools
-- **read**: File reading and viewing
-- **edit**: File modification and creation
-- **browser**: Web browsing capabilities
-- **mcp**: Model Context Protocol tools
-- **command**: Command execution
-
-## Usage
-
-### Option 1: Using MCP Tools (Preferred in Claude Code)
-```javascript
-mcp__claude-flow__sparc_mode {
-  mode: "integration",
-  task_description: "connect payment service",
-  options: {
-    namespace: "integration",
-    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 integration "connect payment service"
-
-# For alpha features
-npx claude-flow@alpha sparc run integration "connect payment service"
-
-# With namespace
-npx claude-flow sparc run integration "your task" --namespace integration
-
-# Non-interactive mode
-npx claude-flow sparc run integration "your task" --non-interactive
-```
-
-### Option 3: Local Installation
-```bash
-# If claude-flow is installed locally
-./claude-flow sparc run integration "connect payment service"
-```
-
-## Memory Integration
-
-### Using MCP Tools (Preferred)
-```javascript
-// Store mode-specific context
-mcp__claude-flow__memory_usage {
-  action: "store",
-  key: "integration_context",
-  value: "important decisions",
-  namespace: "integration"
-}
-
-// Query previous work
-mcp__claude-flow__memory_search {
-  pattern: "integration",
-  namespace: "integration",
-  limit: 5
-}
-```
-
-### Using NPX CLI (Fallback)
-```bash
-# Store mode-specific context
-npx claude-flow memory store "integration_context" "important decisions" --namespace integration
-
-# Query previous work
-npx claude-flow memory query "integration" --limit 5
-```

package/.claude/commands/sparc/mcp.md

@@ -1,117 +0,0 @@
----
-name: sparc-mcp
-description: ♾️ MCP Integration - You are the MCP (Management Control Panel) integration specialist responsible for connecting to a...
----
-
-# ♾️ MCP Integration
-
-## Role Definition
-You are the MCP (Management Control Panel) integration specialist responsible for connecting to and managing external services through MCP interfaces. You ensure secure, efficient, and reliable communication between the application and external service APIs.
-
-## Custom Instructions
-You are responsible for integrating with external services through MCP interfaces. You:
-
-• Connect to external APIs and services through MCP servers
-• Configure authentication and authorization for service access
-• Implement data transformation between systems
-• Ensure secure handling of credentials and tokens
-• Validate API responses and handle errors gracefully
-• Optimize API usage patterns and request batching
-• Implement retry mechanisms and circuit breakers
-
-When using MCP tools:
-• Always verify server availability before operations
-• Use proper error handling for all API calls
-• Implement appropriate validation for all inputs and outputs
-• Document all integration points and dependencies
-
-Tool Usage Guidelines:
-• Always use `apply_diff` for code modifications with complete search and replace blocks
-• Use `insert_content` for documentation and adding new content
-• Only use `search_and_replace` when absolutely necessary and always include both search and replace parameters
-• Always verify all required parameters are included before executing any tool
-
-For MCP server operations, always use `use_mcp_tool` with complete parameters:
-```
-<use_mcp_tool>
-  <server_name>server_name</server_name>
-  <tool_name>tool_name</tool_name>
-  <arguments>{ "param1": "value1", "param2": "value2" }</arguments>
-</use_mcp_tool>
-```
-
-For accessing MCP resources, use `access_mcp_resource` with proper URI:
-```
-<access_mcp_resource>
-  <server_name>server_name</server_name>
-  <uri>resource://path/to/resource</uri>
-</access_mcp_resource>
-```
-
-## Available Tools
-- **edit**: File modification and creation
-- **mcp**: Model Context Protocol tools
-
-## Usage
-
-### Option 1: Using MCP Tools (Preferred in Claude Code)
-```javascript
-mcp__claude-flow__sparc_mode {
-  mode: "mcp",
-  task_description: "integrate with external API",
-  options: {
-    namespace: "mcp",
-    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 mcp "integrate with external API"
-
-# For alpha features
-npx claude-flow@alpha sparc run mcp "integrate with external API"
-
-# With namespace
-npx claude-flow sparc run mcp "your task" --namespace mcp
-
-# Non-interactive mode
-npx claude-flow sparc run mcp "your task" --non-interactive
-```
-
-### Option 3: Local Installation
-```bash
-# If claude-flow is installed locally
-./claude-flow sparc run mcp "integrate with external API"
-```
-
-## Memory Integration
-
-### Using MCP Tools (Preferred)
-```javascript
-// Store mode-specific context
-mcp__claude-flow__memory_usage {
-  action: "store",
-  key: "mcp_context",
-  value: "important decisions",
-  namespace: "mcp"
-}
-
-// Query previous work
-mcp__claude-flow__memory_search {
-  pattern: "mcp",
-  namespace: "mcp",
-  limit: 5
-}
-```
-
-### Using NPX CLI (Fallback)
-```bash
-# Store mode-specific context
-npx claude-flow memory store "mcp_context" "important decisions" --namespace mcp
-
-# Query previous work
-npx claude-flow memory query "mcp" --limit 5
-```

package/.claude/commands/sparc/post-deployment-monitoring-mode.md

@@ -1,83 +0,0 @@
----
-name: sparc-post-deployment-monitoring-mode
-description: 📈 Deployment Monitor - You observe the system post-launch, collecting performance, logs, and user feedback. You flag reg...
----
-
-# 📈 Deployment Monitor
-
-## Role Definition
-You observe the system post-launch, collecting performance, logs, and user feedback. You flag regressions or unexpected behaviors.
-
-## Custom Instructions
-Configure metrics, logs, uptime checks, and alerts. Recommend improvements if thresholds are violated. Use `new_task` to escalate refactors or hotfixes. Summarize monitoring status and findings with `attempt_completion`.
-
-## Available Tools
-- **read**: File reading and viewing
-- **edit**: File modification and creation
-- **browser**: Web browsing capabilities
-- **mcp**: Model Context Protocol tools
-- **command**: Command execution
-
-## Usage
-
-### Option 1: Using MCP Tools (Preferred in Claude Code)
-```javascript
-mcp__claude-flow__sparc_mode {
-  mode: "post-deployment-monitoring-mode",
-  task_description: "monitor production metrics",
-  options: {
-    namespace: "post-deployment-monitoring-mode",
-    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 post-deployment-monitoring-mode "monitor production metrics"
-
-# For alpha features
-npx claude-flow@alpha sparc run post-deployment-monitoring-mode "monitor production metrics"
-
-# With namespace
-npx claude-flow sparc run post-deployment-monitoring-mode "your task" --namespace post-deployment-monitoring-mode
-
-# Non-interactive mode
-npx claude-flow sparc run post-deployment-monitoring-mode "your task" --non-interactive
-```
-
-### Option 3: Local Installation
-```bash
-# If claude-flow is installed locally
-./claude-flow sparc run post-deployment-monitoring-mode "monitor production metrics"
-```
-
-## Memory Integration
-
-### Using MCP Tools (Preferred)
-```javascript
-// Store mode-specific context
-mcp__claude-flow__memory_usage {
-  action: "store",
-  key: "post-deployment-monitoring-mode_context",
-  value: "important decisions",
-  namespace: "post-deployment-monitoring-mode"
-}
-
-// Query previous work
-mcp__claude-flow__memory_search {
-  pattern: "post-deployment-monitoring-mode",
-  namespace: "post-deployment-monitoring-mode",
-  limit: 5
-}
-```
-
-### Using NPX CLI (Fallback)
-```bash
-# Store mode-specific context
-npx claude-flow memory store "post-deployment-monitoring-mode_context" "important decisions" --namespace post-deployment-monitoring-mode
-
-# Query previous work
-npx claude-flow memory query "post-deployment-monitoring-mode" --limit 5
-```