moflo 4.8.16 → 4.8.19

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

@@ -1,109 +1,109 @@
----
-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__moflo__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__moflo__memory_usage {
-  action: "store",
-  key: "devops_context",
-  value: "important decisions",
-  namespace: "devops"
-}
-
-// Query previous work
-mcp__moflo__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
-```
+---
+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__moflo__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__moflo__memory_usage {
+  action: "store",
+  key: "devops_context",
+  value: "important decisions",
+  namespace: "devops"
+}
+
+// Query previous work
+mcp__moflo__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 +1,80 @@
----
-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__moflo__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__moflo__memory_usage {
-  action: "store",
-  key: "docs-writer_context",
-  value: "important decisions",
-  namespace: "docs-writer"
-}
-
-// Query previous work
-mcp__moflo__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
-```
+---
+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__moflo__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__moflo__memory_usage {
+  action: "store",
+  key: "docs-writer_context",
+  value: "important decisions",
+  namespace: "docs-writer"
+}
+
+// Query previous work
+mcp__moflo__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/documenter.md

@@ -1,54 +1,54 @@
-# SPARC Documenter Mode
-
-## Purpose
-Documentation with batch file operations for comprehensive docs.
-
-## Activation
-
-### Option 1: Using MCP Tools (Preferred in Claude Code)
-```javascript
-mcp__moflo__sparc_mode {
-  mode: "documenter",
-  task_description: "create API documentation",
-  options: {
-    format: "markdown",
-    include_examples: 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 documenter "create API documentation"
-
-# For alpha features
-npx claude-flow@alpha sparc run documenter "create API documentation"
-```
-
-### Option 3: Local Installation
-```bash
-# If claude-flow is installed locally
-./claude-flow sparc run documenter "create API documentation"
-```
-
-## Core Capabilities
-- API documentation
-- Code documentation
-- User guides
-- Architecture docs
-- README files
-
-## Documentation Types
-- Markdown documentation
-- JSDoc comments
-- API specifications
-- Integration guides
-- Deployment docs
-
-## Batch Features
-- Parallel doc generation
-- Bulk file updates
-- Cross-reference management
-- Example generation
-- Diagram creation
+# SPARC Documenter Mode
+
+## Purpose
+Documentation with batch file operations for comprehensive docs.
+
+## Activation
+
+### Option 1: Using MCP Tools (Preferred in Claude Code)
+```javascript
+mcp__moflo__sparc_mode {
+  mode: "documenter",
+  task_description: "create API documentation",
+  options: {
+    format: "markdown",
+    include_examples: 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 documenter "create API documentation"
+
+# For alpha features
+npx claude-flow@alpha sparc run documenter "create API documentation"
+```
+
+### Option 3: Local Installation
+```bash
+# If claude-flow is installed locally
+./claude-flow sparc run documenter "create API documentation"
+```
+
+## Core Capabilities
+- API documentation
+- Code documentation
+- User guides
+- Architecture docs
+- README files
+
+## Documentation Types
+- Markdown documentation
+- JSDoc comments
+- API specifications
+- Integration guides
+- Deployment docs
+
+## Batch Features
+- Parallel doc generation
+- Bulk file updates
+- Cross-reference management
+- Example generation
+- Diagram creation

package/.claude/commands/sparc/innovator.md

@@ -1,54 +1,54 @@
-# SPARC Innovator Mode
-
-## Purpose
-Creative problem solving with WebSearch and Memory integration.
-
-## Activation
-
-### Option 1: Using MCP Tools (Preferred in Claude Code)
-```javascript
-mcp__moflo__sparc_mode {
-  mode: "innovator",
-  task_description: "innovative solutions for scaling",
-  options: {
-    research_depth: "comprehensive",
-    creativity_level: "high"
-  }
-}
-```
-
-### 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 innovator "innovative solutions for scaling"
-
-# For alpha features
-npx claude-flow@alpha sparc run innovator "innovative solutions for scaling"
-```
-
-### Option 3: Local Installation
-```bash
-# If claude-flow is installed locally
-./claude-flow sparc run innovator "innovative solutions for scaling"
-```
-
-## Core Capabilities
-- Creative ideation
-- Solution brainstorming
-- Technology exploration
-- Pattern innovation
-- Proof of concept
-
-## Innovation Process
-- Divergent thinking phase
-- Research and exploration
-- Convergent synthesis
-- Prototype planning
-- Feasibility analysis
-
-## Knowledge Sources
-- WebSearch for trends
-- Memory for context
-- Cross-domain insights
-- Pattern recognition
-- Analogical reasoning
+# SPARC Innovator Mode
+
+## Purpose
+Creative problem solving with WebSearch and Memory integration.
+
+## Activation
+
+### Option 1: Using MCP Tools (Preferred in Claude Code)
+```javascript
+mcp__moflo__sparc_mode {
+  mode: "innovator",
+  task_description: "innovative solutions for scaling",
+  options: {
+    research_depth: "comprehensive",
+    creativity_level: "high"
+  }
+}
+```
+
+### 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 innovator "innovative solutions for scaling"
+
+# For alpha features
+npx claude-flow@alpha sparc run innovator "innovative solutions for scaling"
+```
+
+### Option 3: Local Installation
+```bash
+# If claude-flow is installed locally
+./claude-flow sparc run innovator "innovative solutions for scaling"
+```
+
+## Core Capabilities
+- Creative ideation
+- Solution brainstorming
+- Technology exploration
+- Pattern innovation
+- Proof of concept
+
+## Innovation Process
+- Divergent thinking phase
+- Research and exploration
+- Convergent synthesis
+- Prototype planning
+- Feasibility analysis
+
+## Knowledge Sources
+- WebSearch for trends
+- Memory for context
+- Cross-domain insights
+- Pattern recognition
+- Analogical reasoning