claude-flow-novice 2.14.35 → 2.14.37

package/claude-assets/agents/cfn-dev-team/reviewers/README.md

@@ -1,11 +1,3 @@
----
-name: reviewers-readme
-description: Documentation file for CFN dev team reviewers overview and code review standards
-tools: []
-model: haiku
-type: documentation
----
-
 # Reviewers
 
 Code review and validation agents focused on quality assurance.
@@ -63,4 +55,4 @@ Structured feedback with:
 - Critical issues (blocking)
 - Warnings (should fix)
 - Suggestions (improvements)
-- Specific file/line references
+- Specific file/line references

package/claude-assets/agents/cfn-dev-team/reviewers/quality/quality-metrics.md

@@ -1,13 +1,3 @@
----
-name: quality-metrics
-description: MUST BE USED when measuring agent effectiveness and code quality validation. Use PROACTIVELY for metrics analysis, quality assessment, performance validation. Keywords - quality, metrics, validation, measurement, effectiveness
-tools: [Read, Write, Edit, Bash, Grep, Glob, TodoWrite]
-model: haiku
-type: validator
-acl_level: 2
-capabilities: [quality-metrics, performance-analysis, validation]
----
-
 # Quality Metrics & Validation
 
 **Version:** 2.0.0

package/claude-assets/agents/cfn-dev-team/test-agent.md

@@ -1,13 +1,3 @@
----
-name: test-agent
-description: MUST BE USED when documenting epic creator deletion issues and bug fixes. Use PROACTIVELY for issue tracking, bug documentation, resolution summaries. Keywords - test, bug, issue, documentation, epic, deletion
-tools: [Read, Write, Edit, Bash, Grep, Glob, TodoWrite]
-model: haiku
-type: specialist
-acl_level: 1
-capabilities: [bug-documentation, issue-tracking, test-summary]
----
-
 # Epic Creator Deletion Issue - Complete Summary
 
 **Date:** 2025-11-03

package/claude-assets/agents/cfn-dev-team/testers/README.md

@@ -1,11 +1,3 @@
----
-name: testers-readme
-description: Documentation file for CFN dev team testers overview and testing standards
-tools: []
-model: haiku
-type: documentation
----
-
 # Testers
 
 Testing and validation specialists ensuring code quality and correctness.
@@ -99,4 +91,4 @@ Structured report with:
 - Test execution summary
 - Coverage analysis
 - Failed test details
-- Recommendations for improvement
+- Recommendations for improvement

package/claude-assets/agents/csuite/cto-agent.md

@@ -1,13 +1,3 @@
----
-name: cto-agent
-description: MUST BE USED when making strategic technical decisions and architectural oversight. Use PROACTIVELY for technical roadmap planning, architecture reviews, strategic guidance. Keywords - CTO, technical strategy, architecture, leadership, oversight
-tools: [Read, Write, Edit, Bash, Grep, Glob, TodoWrite]
-model: sonnet
-type: coordinator
-acl_level: 4
-capabilities: [technical-strategy, architecture-oversight, leadership]
----
-
 # CTO Agent - Dr. Tech
 
 ## Role Identity

package/claude-assets/agents/custom/cfn-system-expert.md

@@ -256,131 +256,4 @@ redis-cli lpush "swarm:${TASK_ID}:${AGENT_ID}:done" "complete"
 - `.claude/skills/cfn-redis-coordination/SKILL.md`: Coordination patterns
 - `.claude/commands/cfn/CFN_COORDINATOR_PARAMETERS.md`: Parameter specifications
 - `planning/cfn-v3/DUAL_MODE_IMPLEMENTATION.md`: Architecture details
-- Planning documents: Sprint lessons and adaptive context insights
-
-## CFN Implementation Patterns & Lessons Learned
-
-### Core Architecture Patterns
-
-#### STRAT-007: Background Execution Strategy
-- **Insight**: Use background execution with coordination monitoring for long-running orchestration workflows (>10 minutes). Bash tool has hard 10-minute timeout that cannot be extended.
-- **Application**: Essential for CFN Loop orchestration that exceeds standard timeout limits.
-
-#### PATTERN-008: Product Owner Decision Flow
-- **Insight**: Implement explicit Product Owner decision flow after Loop 2 consensus to prevent validator scope creep and enforce strategic boundaries.
-- **Application**: Core CFN Loop governance pattern ensuring proper decision hierarchy.
-
-#### PATTERN-010: Parallel Execution with Temp Files
-- **Insight**: Use background processes with temporary files to eliminate race conditions in parallel agent coordination. Pattern: spawn all agents in background with `(skill-execution > /tmp/output-file) &`, collect PIDs, use `wait` to synchronize, read results from temp files after completion.
-- **Application**: Optimizes CFN Loop parallel agent execution while maintaining coordination integrity.
-
-### Context Management Patterns
-
-#### STRAT-021: Standardized Context Extraction Templates
-- **Insight**: Use standardized context extraction templates in coordinators. Template structure: epicGoal (1-2 sentences), inScope (list), outOfScope (list), deliverables (file paths), directory (creation path), acceptanceCriteria (measurable requirements).
-- **Application**: Prevents minimal context that causes wrong deliverables in CFN execution.
-
-#### PATTERN-020: Multi-Layer Context Injection
-- **Context**: Coordinator → Orchestrator → Agent Flow
-- **Insight**: When implementing multi-layer coordination, ensure context flows through ALL layers. Breaking this chain causes 'consensus on vapor' (high confidence, zero deliverables).
-- **Application**: Critical for CFN Loop context integrity across coordinator-orchestrator-agent chain.
-
-#### PATTERN-021: Context Validation Pipeline
-- **Context**: Multi-Layer Coordination
-- **Insight**: Design context validation pipeline with checkpoints at each layer. Pattern: (1) Coordinator validates extracted context, (2) Orchestrator validates persistence retrieval, (3) Agents validate received context.
-- **Application**: Fail-fast prevents cascading context loss in CFN workflows.
-
-#### PATTERN-022: Agent Lifecycle - Clean Exit Protocol
-- **Insight**: Agents must exit cleanly after reporting confidence. Pattern: (1) Signal done via coordination protocol, (2) Report confidence score, (3) Exit immediately.
-- **Application**: Enables adaptive agent specialization and prevents orchestrator blocking.
-
-### Sprint Execution Patterns
-
-#### Sprint Context Structure
-```json
-{
-  "sprint_name": "P1 Coordinator Monitoring",
-  "sprint_num": 1,
-  "total_sprints": 7,
-  "deliverables": [
-    "test-p1-monitoring.sh",
-    "docs/P1_MONITORING_RESULTS.md"
-  ],
-  "in_scope": [
-    "P1 coordinator monitoring validation",
-    "Test timeout mechanisms",
-    "Logging verification"
-  ],
-  "out_of_scope": [
-    "P2-P7 monitoring",
-    "Cross-priority integration",
-    "Epic-level summary"
-  ],
-  "directory": "/mnt/c/Users/masha/Documents/claude-flow-novice/tests/p1"
-}
-```
-
-#### Sprint Execution Tool: `execute-sprint-task.sh`
-- **Purpose**: Enables sprint-aware agent execution with focused context injection
-- **Usage**: Decompose large epics into focused sprints with clear deliverables and scope boundaries
-- **Key Principles**: Focused scope, incremental progress, precise deliverables, context specificity
-
-### CFN v3 Advanced Patterns
-
-#### STRAT-026: Persistence Context Storage Over CLI Parameters
-- **Insight**: Use persistence layer for complex JSON context storage instead of CLI parameters. Eliminates shell escaping issues, enables swarm recovery, and provides single source of truth.
-- **Application**: Foundation for CFN v3 dual-mode architecture.
-
-#### PATTERN-023: Dual-Mode Architecture Pattern
-- **Insight**: Implement dual execution modes (optimized vs simplified) sharing core logic. CLI mode for production (cost-optimized), Task mode for debugging (full visibility).
-- **Application**: Enables flexible CFN execution based on user needs.
-
-#### PATTERN-024: Swarm Recovery via Persistence
-- **Insight**: Store swarm state in persistence layer with TTL to enable crash recovery. Agents can resume from last known state using task_id as recovery key.
-- **Application**: Critical for long-running CFN Loops and system reliability.
-
-#### STRAT-028: Modular Skill Architecture
-- **Insight**: Decompose complex systems into independent skills (20 skills in CFN v3). Enables reuse, testing isolation, and incremental enhancement.
-- **Application**: Core architectural principle for CFN system maintainability.
-
-### CFN Anti-Patterns & Prevention
-
-#### ANTI-020: Context Storage Without Injection
-- **Context**: Coordination Systems
-- **Insight**: Avoid storing context in persistence layer without retrieving and injecting it into agent prompts.
-- **Prevention**: Always validate context injection chain: storage → retrieval → agent delivery.
-
-#### ANTI-021: Generic Context When Specifics Exist
-- **Context**: Agent Spawning
-- **Insight**: Never pass generic iteration-level context when task-specific deliverables exist.
-- **Prevention**: Always inject complete deliverables, directory paths, and acceptance criteria.
-
-#### ANTI-023: Task-Spawned Validators Without Completion Protocol
-- **Context**: Loop 2 Validation (Task Mode)
-- **Insight**: Main Chat spawns validators via Task() without clear scope boundaries or mode-aware completion protocols.
-- **Prevention**: Task-spawned validators should return structured output only - no coordination signals.
-
-### CFN Testing & Debugging
-
-#### EDGE-020: Comparative Agent Spawn Testing
-- **Context**: Context Debugging
-- **Insight**: When debugging context issues, use comparative agent spawn testing. Manual spawn with explicit context vs CFN Loop with generic context reveals injection failures.
-- **Application**: Primary debugging technique for context-related CFN issues.
-
-### Universal Anti-Patterns (CFN Relevance)
-
-#### ANTI-004: Regex Validation Anti-Pattern
-- **Insight**: Avoid simplistic regex matching for agent validation. Pattern `[[ $AGENTS =~ $AGENTS ]]` always returns true.
-- **CFN Relevance**: Critical for agent validation logic in CFN coordination.
-
-#### PATTERN-025: Comprehensive File Validation
-- **Insight**: Implement multi-stage validation including file type, permissions, size constraints, and content integrity.
-- **CFN Relevance**: Essential for CFN deliverable verification and security.
-
-#### PATTERN-026: Shell Strict Mode
-- **Insight**: Enable shell strict mode using `set -euo pipefail` for robust and predictable shell scripts.
-- **CFN Relevance**: Critical reliability pattern for all CFN skill scripts.
-
-#### PATTERN-028: Process Group Management
-- **Insight**: Implement comprehensive process group management for clean termination and resource cleanup.
-- **CFN Relevance**: Essential for CFN background process orchestration and preventing resource leaks.
+- Planning documents: Sprint lessons and adaptive context insights

package/claude-assets/agents/custom/claude-code-expert.md

@@ -1,7 +1,7 @@
 ---
 name: claude-code-expert
-description: MUST BE USED when answering questions about Claude Code features, documentation, and best practices. Use PROACTIVELY for Claude Code guidance, sub-agent creation, workflow questions. Keywords - claude-code, sub-agents, documentation, guides, best-practices, workflows
-tools: [WebFetch, Read, Grep, Glob]
+description: MUST BE USED when answering questions about Claude Code features, documentation, and best practices or adding/removing MCPs. Use PROACTIVELY for Claude Code guidance, sub-agent creation, workflow questions. Keywords - claude-code, sub-agents, documentation, guides, best-practices, workflows, MCP
+tools: [WebFetch, Read, Grep, Glob, Bash, Write]
 model: sonnet
 type: specialist
 capabilities:
@@ -80,6 +80,155 @@ You are a specialized agent with deep expertise in Claude Code, Anthropic's offi
 - "How do I use MCP tools in Claude Code?"
 - "How do I monitor agent execution?"
 
+## MCP Server Configuration
+
+### Configuration Files
+MCP servers are configured in two locations:
+1. **Global config**: `~/.claude.json` (user-level, applies to all projects)
+2. **Project config**: `.claude/settings.json` (project-specific overrides)
+
+### Adding MCP Servers Globally
+
+**Location**: `~/.claude.json`
+
+Add to the `mcpServers` object:
+```json
+{
+  "mcpServers": {
+    "server-name": {
+      "type": "stdio",
+      "command": "npx",
+      "args": ["-y", "@package/mcp-server"],
+      "env": {}
+    }
+  }
+}
+```
+
+**HTTP-based MCP servers**:
+```json
+{
+  "mcpServers": {
+    "shadcn": {
+      "type": "http",
+      "url": "https://www.shadcn.io/api/mcp"
+    }
+  }
+}
+```
+
+### Enabling/Disabling MCP Servers
+
+**Enable globally** (add to `enabledMcpjsonServers` array):
+```json
+{
+  "enabledMcpjsonServers": ["sequential-thinking", "n8n-mcp"]
+}
+```
+
+**Disable globally** (add to `disabledMcpjsonServers` array):
+```json
+{
+  "disabledMcpjsonServers": ["playwright", "shadcn", "chrome-devtools"]
+}
+```
+
+**Disable for specific project** (in `~/.claude.json` under `projects` key):
+```json
+{
+  "projects": {
+    "/path/to/project": {
+      "disabledMcpServers": ["claude-flow", "ruv-swarm", "playwright"]
+    }
+  }
+}
+```
+
+### Project-Level MCP Configuration
+
+**Location**: `.claude/settings.json` (in project root)
+
+```json
+{
+  "mcpServers": {
+    "n8n-mcp": {
+      "command": "npx",
+      "args": ["-y", "n8n-mcp"],
+      "env": {
+        "N8N_API_KEY": "${N8N_API_KEY}"
+      }
+    }
+  },
+  "enabledMcpjsonServers": ["n8n-mcp"]
+}
+```
+
+### Configuration Precedence
+1. Project-level `disabledMcpServers` overrides global settings
+2. Project-level `mcpServers` supplements global servers
+3. `enabledMcpjsonServers` must explicitly list servers to enable
+
+### Common MCP Servers
+
+**Sequential Thinking** (multi-step reasoning):
+```json
+{
+  "sequential-thinking": {
+    "type": "stdio",
+    "command": "npx",
+    "args": ["-y", "@modelcontextprotocol/server-sequential-thinking"],
+    "env": {}
+  }
+}
+```
+
+**Playwright** (browser automation):
+```json
+{
+  "playwright": {
+    "type": "stdio",
+    "command": "npx",
+    "args": ["-y", "@playwright/mcp"],
+    "env": {}
+  }
+}
+```
+
+**Chrome DevTools** (browser debugging):
+```json
+{
+  "chrome-devtools": {
+    "type": "stdio",
+    "command": "npx",
+    "args": ["-y", "chrome-devtools-mcp@latest"],
+    "env": {}
+  }
+}
+```
+
+**Z.ai MCP** (AI routing):
+```json
+{
+  "zai-mcp-server": {
+    "type": "stdio",
+    "command": "npx",
+    "args": ["-y", "@z_ai/mcp-server"],
+    "env": {
+      "Z_AI_API_KEY": "${Z_AI_API_KEY}",
+      "Z_AI_MODE": "ZAI"
+    }
+  }
+}
+```
+
+### Auto-Discovery
+Claude Code auto-discovers MCP servers from:
+- Globally installed npm packages with MCP exports
+- Tool permissions (e.g., `mcp__package-name__tool`)
+- `.mcp.json` files in project roots
+
+To prevent auto-discovered servers from connecting, add them to `disabledMcpServers`.
+
 ## Documentation URLs to Reference
 
 Primary resources:

package/claude-assets/agents/docker-coordinators/cfn-docker-v3-coordinator.md

@@ -1,16 +1,17 @@
 ---
 name: cfn-docker-v3-coordinator
-description: MUST BE USED when orchestrating container-based CFN Loop execution with MCP isolation. Use PROACTIVELY for docker-based agent coordination, skill selection, resource management. Keywords - docker, containers, orchestration, MCP, isolation
+description: "MUST BE USED when orchestrating container-based CFN Loop execution with skill-based MCP isolation and resource management"
 argument-hint: "[task-description] --mode=mvp|standard|enterprise --memory-limit=1g --docker-network=mcp-network"
-allowed-tools: ["Bash", "Read", "Write", "Edit", "Grep", "Glob", "TodoWrite", "Task"]
+tools: [Bash, Read, Write, Edit, Grep, Glob, TodoWrite]
 model: sonnet
 type: coordinator
 acl_level: 3
+capabilities: [docker-orchestration, container-management, mcp-authentication, redis-coordination, skill-based-selection, resource-management, swarm-recovery, cost-optimization, security-isolation, monitoring]
 ---
 
 # CFN Docker V3 Coordinator
 
-**Purpose:** Orchestrate container-based CFN Loop execution with skill-based MCP isolation and resource management.
+I am the cfn-docker-v3-coordinator, a specialized coordinator agent for container-based CFN Loop execution with skill-based MCP isolation and resource management.
 
 ## Architecture
 
@@ -180,6 +181,41 @@ CFN_DOCKER_MCP_TOKEN_EXPIRY=24h
 - Skill requirements: `config/skill-requirements.json`
 - MCP server definitions: `config/mcp-servers.json`
 
+## Core Responsibilities
+
+1. **Task Analysis and Context Extraction**: Parse task descriptions for deliverables and acceptance criteria, determine required agent types based on complexity, extract sprint/epic context for proper coordination
+
+2. **Agent Container Spawning**: Use `cfn-docker-agent-spawning` skill for container creation, apply memory limits and resource constraints, mount codebase and skills as read-only volumes, configure environment variables for agent identity
+
+3. **Skill-Based MCP Selection**: Use `cfn-docker-skill-mcp-selection` to map agent skills to MCP servers, generate authentication tokens for MCP access, configure MCP server connections for each container
+
+4. **Redis Coordination**: Use `cfn-docker-redis-coordination` for swarm communication, store context and agent state in Redis for swarm recovery, manage agent completion signaling and consensus collection
+
+5. **Loop Orchestration**: Use `cfn-docker-loop-orchestration` for CFN Loop execution, handle Loop 3 (implementer) → Loop 2 (validator) → Product Owner decision flow, manage iterations and adaptive agent specialization
+
+6. **Resource Management**: Monitor container resource usage (memory, CPU, network), enforce resource limits and constraints, optimize resource allocation for cost efficiency
+
+7. **Security and Compliance**: Enforce multi-layer security architecture, manage token-based authentication, implement rate limiting and audit logging, ensure container isolation and access control
+
+## Completion Protocol
+
+1. **Task Completion**: All containers terminated gracefully, Redis coordination state cleaned up, resource usage reported, cost savings documented
+
+2. **Error Handling**: Swarm recovery initiated via Redis state, failed containers restarted with clean state, fallback mechanisms activated when needed, manual intervention hooks triggered for critical issues
+
+3. **State Cleanup**: Docker containers removed, temporary volumes cleaned up, authentication tokens revoked, coordination keys expired in Redis
+
+4. **Reporting**: Generate comprehensive completion report with metrics, document container performance and resource usage, provide cost optimization recommendations, log security events and compliance status
+
+## Success Metrics
+
+- **Container Success Rate**: ≥95% of containers complete tasks successfully (confidence threshold: 0.85)
+- **Resource Efficiency**: Achieve 50%+ memory savings vs monolithic agent approach
+- **Cost Optimization**: Maintain 95%+ cost savings vs Task-based spawning
+- **Security Compliance**: 100% authentication token validation success
+- **Recovery Capability**: ≤90 seconds for swarm recovery from container failure
+- **MCP Connection Success**: ≥98% successful MCP server connections
+
 ## Implementation Status
 
 ✅ **Complete Implementation:**

package/claude-assets/agents/docker-team/csuite/c-suite-template.md

@@ -1,12 +1,8 @@
 ---
-name: c-suite-template
-description: MUST BE USED when creating C-Suite executive personas for strategic decision-making. Use PROACTIVELY for organizational architecture, executive strategy, decision authority. Keywords - c-suite, executive, strategy, decision-making, leadership
+description: C-Suite executive personas for strategic decision-making in organizational architecture
 tools: [Read, Write, TodoWrite, Bash]
 priority: medium
 tags: [csuite, executive, strategy, decision-making, cmo, cfo, coo, ceo]
-model: sonnet
-type: specialist
-acl_level: 4
 ---
 
 # C-Suite Agent Template

package/claude-assets/agents/docker-team/infrastructure/team-coordinator-template.md

@@ -1,12 +1,8 @@
 ---
-name: team-coordinator-template
-description: MUST BE USED when generating team-specific coordinator configurations for Docker architecture. Use PROACTIVELY for infrastructure templating, team configuration, Docker services. Keywords - docker, infrastructure, templating, coordinator, team-config
+description: Generate team-specific coordinator configurations for Docker organizational architecture
 tools: [Read, Write, Edit, Bash, Grep, Glob]
 priority: high
 tags: [docker, infrastructure, templating, coordinator, team-config]
-model: haiku
-type: specialist
-acl_level: 3
 ---
 
 # Team Coordinator Template Agent

package/claude-assets/agents/marketing_hybrid/cost_tracker.md

@@ -1,13 +1,3 @@
----
-name: cost-tracker
-description: MUST BE USED when monitoring Z.ai worker costs during pilot testing. Use PROACTIVELY for cost tracking, budget monitoring, expense reporting. Keywords - cost, tracking, monitoring, Z.ai, budget, expenses
-tools: [Read, Write, Edit, Bash, Grep, Glob, TodoWrite]
-model: haiku
-type: specialist
-acl_level: 2
-capabilities: [cost-monitoring, budget-tracking, expense-reporting]
----
-
 # Cost Tracking Agent
 ## Role
 Monitor Z.ai worker costs during 48-hour pilot

package/claude-assets/agents/marketing_hybrid/docker_deployer.md

@@ -1,13 +1,3 @@
----
-name: docker-deployer
-description: MUST BE USED when deploying marketing coordinator services via Docker. Use PROACTIVELY for container deployment, service configuration, docker-compose management. Keywords - docker, deploy, containers, docker-compose, services
-tools: [Read, Write, Edit, Bash, Grep, Glob, TodoWrite]
-model: haiku
-type: specialist
-acl_level: 2
-capabilities: [docker-deployment, container-management, service-configuration]
----
-
 # Docker Deployer Agent
 ## Role
 Deploy marketing coordinator using docker-compose.hybrid.yml

package/claude-assets/agents/marketing_hybrid/zai_worker_spawner.md

@@ -1,13 +1,3 @@
----
-name: zai-worker-spawner
-description: MUST BE USED when spawning Z.ai workers for marketing pilot testing. Use PROACTIVELY for worker orchestration, API configuration, service scaling. Keywords - Z.ai, worker, spawner, scaling, orchestration
-tools: [Read, Write, Edit, Bash, Grep, Glob, TodoWrite]
-model: haiku
-type: specialist
-acl_level: 2
-capabilities: [worker-spawning, service-orchestration, api-configuration]
----
-
 # Z.ai Worker Spawner Agent
 ## Role
 Spawn 3 Z.ai workers for marketing pilot

package/claude-assets/commands/CFN_LOOP_TASK_MODE.md

@@ -467,7 +467,7 @@ Complex/Enterprise (>5 files, >500 LOC): +code-analyzer
 ### Complexity Analysis CLI
 ```bash
 ./.claude/skills/task-complexity/analyze.sh --task "$DESC" --files "$LIST"
-# Output: {"score": 85, "category": "standard", "validators": ["reviewer","tester","system-architect","security-specialist"], "threshold": 0.90}
+# Output: {"score": 85, "category": "standard", "validators": ["reviewer","tester","architect","security-specialist"], "threshold": 0.90}
 ```
 
 ---