claude-flow-novice 2.16.0 → 2.16.1

package/.claude/cfn-extras/skills/GOOGLE_SHEETS_SKILLS_README.md

@@ -371,7 +371,7 @@ find ./.claude/cfn-extras/skills/google-sheets-* -name "*.sh" \
 
 ## Related Documentation
 
-- **CFN Loop Guide**: `.claude/commands/cfn/CFN_LOOP_TASK_MODE.md`
+- **CFN Loop Guide**: `.claude/commands/CFN_LOOP_TASK_MODE.md`
 - **Progress Tracking**: `.claude/cfn-extras/skills/google-sheets-progress/SKILL.md`
 - **Validation Rules**: `.claude/cfn-extras/skills/google-sheets-validation/SKILL.md`
 - **Formula Templates**: `.claude/cfn-extras/skills/google-sheets-formula-builder/SKILL.md`

package/.claude/cfn-extras/skills/google-sheets-api-coordinator/SKILL.md

@@ -269,4 +269,4 @@ Rate limit state stored in: `.claude/cfn-extras/.gs-api-quota.json`
 - **Google Sheets API**: https://developers.google.com/sheets/api
 - **Rate Limiting Guide**: https://developers.google.com/sheets/api/guides/limits
 - **Quota Documentation**: `google-sheets-validation` skill
-- **CFN Loop Guide**: `.claude/commands/cfn/CFN_LOOP_TASK_MODE.md`
+- **CFN Loop Guide**: `.claude/commands/CFN_LOOP_TASK_MODE.md`

package/.claude/cfn-extras/skills/google-sheets-formula-builder/SKILL.md

@@ -234,4 +234,4 @@ fi
 
 - **Google Sheets API**: https://developers.google.com/sheets/api/reference/rest
 - **Formula Validation**: `google-sheets-validation` skill
-- **CFN Loop Guide**: `.claude/commands/cfn/CFN_LOOP_TASK_MODE.md`
+- **CFN Loop Guide**: `.claude/commands/CFN_LOOP_TASK_MODE.md`

package/.claude/cfn-extras/skills/google-sheets-progress/SKILL.md

@@ -281,7 +281,7 @@ The skill includes comprehensive test coverage:
 
 ## References
 
-- **CFN Loop Documentation**: `.claude/commands/cfn/CFN_LOOP_TASK_MODE.md`
+- **CFN Loop Documentation**: `.claude/commands/CFN_LOOP_TASK_MODE.md`
 - **State Management Pattern**: `.claude/skills/cfn-automatic-memory-persistence/SKILL.md`
 - **Coordination Protocols**: `.claude/skills/cfn-coordination/SKILL.md`
 - **Agent Output Standards**: `docs/AGENT_OUTPUT_STANDARDS.md`

package/.claude/commands/CFN_LOOP_FRONTEND.md

@@ -732,7 +732,7 @@ Not generic advice - specific fixes only.`
 
 ## Related Documentation
 
-- **Task Mode Guide**: `.claude/commands/cfn/CFN_LOOP_TASK_MODE.md`
+- **Task Mode Guide**: `.claude/commands/CFN_LOOP_TASK_MODE.md`
 - **Standard CFN Loop**: `.claude/commands/cfn/cfn-loop.md`
 - **Coordinator Parameters**: `.claude/commands/cfn/CFN_COORDINATOR_PARAMETERS.md`
 

package/.claude/commands/cfn-loop-cli.md

@@ -1,12 +1,12 @@
 ---
 description: "Execute CFN Loop in simplified CLI mode (Main Chat coordination, provider routing)"
-argument-hint: "<task description> [--mode=mvp|standard|enterprise] [--provider=zai|kimi|anthropic|openrouter] [--model=<model>]"
+argument-hint: "<task description> [--mode=mvp|standard|enterprise] [--provider=zai|kimi|anthropic|openrouter] [--model=<model>] [--agents=N] [--threshold=0.75]"
 allowed-tools: ["Task", "TodoWrite", "Read", "Bash", "SlashCommand"]
 ---
 
-# CFN Loop CLI Mode - Simplified Main Chat Coordination
+# CFN Loop CLI Mode - Parallel Agent Coordination
 
-🚨 **NEW ARCHITECTURE:** Main Chat directly coordinates CLI agents via Redis BLPOP signaling
+🚨 **v2.0 ARCHITECTURE:** Main Chat spawns parallel CLI agents with threshold-based completion
 
 ---
 
@@ -18,6 +18,8 @@ TASK_DESCRIPTION: $ARGUMENTS (extract task, remove flags)
 MODE: Parse from --mode flag or default to "standard"
 PROVIDER: Parse from --provider flag or use Main Chat setting
 MODEL: Parse from --model flag or use provider default
+AGENTS: Parse from --agents flag or default to 4
+THRESHOLD: Parse from --threshold flag or default to 0.75 (3/4 agents)
 ```
 
 **Step 2: Set Environment Variables**
@@ -27,6 +29,7 @@ TASK_ID="cfn-cli-$(date +%s%N | tail -c 7)-${RANDOM}"
 echo "📋 Task ID: $TASK_ID"
 echo "🎯 Mode: $MODE"
 echo "🤖 Provider: $PROVIDER (from --provider or Main Chat setting)"
+echo "👥 Agents: $AGENTS (threshold: $THRESHOLD)"
 if [ -n "$MODEL" ]; then
   echo "🧠 Model: $MODEL"
 fi
@@ -53,55 +56,88 @@ fi
 echo "✅ Redis available for Main Chat coordination"
 ```
 
-**Step 4: Spawn Initial CLI Agent (Main Chat Coordination Pattern)**
+**Step 4: Spawn Parallel CLI Agents**
 ```bash
-# Determine first agent type based on task
-# This is a simplified selection - could be enhanced with task classification
-AGENT_TYPE="backend-developer"
+# Define agent types based on task complexity
+# For comprehensive tasks, spawn multiple specialized agents
+AGENT_TYPES=("backend-developer" "tester" "code-reviewer" "security-specialist")
 
-# Spawn first CLI agent with provider routing
-echo "🚀 Spawning CLI agent: $AGENT_TYPE"
+echo "🚀 Spawning $AGENTS parallel CLI agents..."
 
-npx tsx src/cli/spawn-agent-cli.ts "$AGENT_TYPE" \
-  --task-id "$TASK_ID" \
-  --mode "$MODE" \
-  ${PROVIDER:+--provider "$PROVIDER"} \
-  ${MODEL:+--model "$MODEL"} \
-  --background
+# Spawn agents in BACKGROUND (use & to allow Main Chat to continue)
+for i in $(seq 1 $AGENTS); do
+  AGENT_TYPE="${AGENT_TYPES[$((i-1)) % ${#AGENT_TYPES[@]}]}"
+  AGENT_ID="${AGENT_TYPE}-${TASK_ID}-${i}"
 
-echo "✅ CLI agent spawned with Task ID: $TASK_ID"
-```
-
-**Step 5: Wait for Agent Completion (Main Chat BLPOP Pattern)**
-```bash
-# Main Chat waits for completion signal via Redis BLPOP
-echo "⏳ Waiting for CLI agent completion..."
+  echo "  → Spawning agent $i: $AGENT_TYPE ($AGENT_ID)"
 
-SIGNAL_KEY="cfn:mainchat:signal:$TASK_ID"
-TIMEOUT_SECONDS=120
+  npx claude-flow-novice agent "$AGENT_TYPE" \
+    --task-id "$TASK_ID" \
+    --mode "$MODE" \
+    --provider "$PROVIDER" \
+    --context "$TASK_DESCRIPTION" \
+    </dev/null >/tmp/agent-${AGENT_ID}.log 2>&1 &
+done
 
-# Wait for completion signal with timeout
-COMPLETION_SIGNAL=$(timeout $TIMEOUT_SECONDS redis-cli BLPOP "$SIGNAL_KEY" $((TIMEOUT_SECONDS + 10)))
+echo "✅ All $AGENTS CLI agents spawned with Task ID: $TASK_ID"
+```
 
-if [ $? -eq 0 ] && [ -n "$COMPLETION_SIGNAL" ]; then
-  echo "✅ CLI agent completed successfully"
-  echo "📊 Completion signal received via Redis"
+**Step 5: Wait for Threshold Completion (FOREGROUND - Required for Main Chat)**
+```bash
+# CRITICAL: Run monitor in FOREGROUND so Main Chat receives completion signal
+# DO NOT use run_in_background for this monitoring loop
+
+COMPLETION_QUEUE="cfn:cli:${TASK_ID}:completion"
+REQUIRED=$(echo "$AGENTS * $THRESHOLD" | bc | cut -d. -f1)
+
+echo "⏳ Monitoring for completion (${REQUIRED}/$AGENTS agents)..."
+echo "📊 Queue: $COMPLETION_QUEUE"
+echo ""
+
+COMPLETED=0
+END_TIME=$(($(date +%s) + 300))  # 5 minute timeout
+
+while [ $(date +%s) -lt $END_TIME ] && [ $COMPLETED -lt $REQUIRED ]; do
+  QUEUE_LEN=$(redis-cli LLEN "$COMPLETION_QUEUE" 2>/dev/null || echo "0")
+
+  if [ "$QUEUE_LEN" -gt 0 ]; then
+    SIGNAL=$(redis-cli LPOP "$COMPLETION_QUEUE")
+    if [ -n "$SIGNAL" ] && [ "$SIGNAL" != "(nil)" ]; then
+      COMPLETED=$((COMPLETED + 1))
+      AGENT_ID=$(echo "$SIGNAL" | jq -r '.agentId' 2>/dev/null || echo "unknown")
+      CONFIDENCE=$(echo "$SIGNAL" | jq -r '.confidence' 2>/dev/null || echo "N/A")
+      PROVIDER=$(echo "$SIGNAL" | jq -r '.provider' 2>/dev/null || echo "N/A")
+
+      echo "✅ Agent $COMPLETED completed: $AGENT_ID"
+      echo "   Confidence: $CONFIDENCE, Provider: $PROVIDER"
+      echo ""
+
+      if [ $COMPLETED -ge $REQUIRED ]; then
+        echo "🎉 THRESHOLD MET! ($COMPLETED/$AGENTS agents)"
+        echo "✅ CFN Loop CLI task completed"
+        exit 0
+      fi
+    fi
+  fi
+
+  sleep 3
+done
+
+echo "⏰ Timeout: Only $COMPLETED/$AGENTS agents completed"
+exit 1
+```
 
-  # Parse completion signal (second line contains JSON)
-  SIGNAL_DATA=$(echo "$COMPLETION_SIGNAL" | tail -n 1)
-  echo "🔍 Agent signal: $SIGNAL_DATA"
+**Step 6: Query Agent Status (Optional - Interactive)**
+```bash
+# Main Chat can query individual agent status during execution
+# Example: npx tsx src/cli/coordination/agent-messaging.ts status --task-id "$TASK_ID" --agent-id <agent-id>
 
-  # Could spawn additional agents here based on signal content
-  # For now, we'll consider the task complete
-  echo "🎉 CFN Loop CLI task completed"
-else
-  echo "⚠️  CLI agent did not complete within timeout ($TIMEOUT_SECONDS seconds)"
-  echo "💡 Check agent logs or increase timeout if needed"
-fi
+# Or send commands to running agents:
+# npx tsx src/cli/coordination/agent-messaging.ts send --task-id "$TASK_ID" --agent-id <agent-id> --command status
 ```
 
-**Step 6: Inform User**
-Report completion status and any additional information.
+**Step 7: Inform User**
+Report completion status, which agents completed, and any additional information.
 
 ---
 
@@ -111,13 +147,55 @@ Report completion status and any additional information.
 
 ## What is CLI Mode?
 
-**NEW CLI Mode Architecture (Simplified):**
-- **Main Chat** directly spawns CLI agents with provider routing
+**v2.0 CLI Mode Architecture (Parallel + Messaging):**
+- **Main Chat** spawns multiple CLI agents in parallel
 - **CLI agents** execute tasks and send Redis completion signals
-- **Main Chat** waits via Redis BLPOP for agent completion
-- **2-layer coordination** (Main Chat → CLI agents)
+- **Main Chat** waits for threshold completion (e.g., 3/4 agents)
+- **Bidirectional messaging** - Main Chat can send commands to running agents
 - **Provider routing** via `--provider` and `--model` flags
-- **Fallback behavior** to Z.ai glm-4.6 if no provider specified
+- **Graceful degradation** - continues when threshold met, doesn't wait for stragglers
+
+## New Features (v2.0)
+
+### Parallel Agent Spawning
+- Spawn multiple agents simultaneously (default: 4)
+- Each agent works independently on the task
+- Different agent types for comprehensive coverage
+
+### Threshold-Based Completion
+- Exit when N/M agents complete (default: 75%)
+- Don't wait for slow/stuck agents
+- Configurable via `--threshold` flag
+
+### Bidirectional Messaging
+Main Chat can communicate with running agents:
+
+**Query agent status:**
+```bash
+npx tsx src/cli/coordination/agent-messaging.ts status \
+  --task-id "$TASK_ID" --agent-id <agent-id>
+```
+
+**Send commands to agents:**
+```bash
+# Request status update
+npx tsx src/cli/coordination/agent-messaging.ts send \
+  --task-id "$TASK_ID" --agent-id <agent-id> --command status
+
+# Redirect agent to new task
+npx tsx src/cli/coordination/agent-messaging.ts send \
+  --task-id "$TASK_ID" --agent-id <agent-id> --command redirect \
+  --payload '{"newTask": "Focus on security tests"}'
+
+# Abort agent
+npx tsx src/cli/coordination/agent-messaging.ts send \
+  --task-id "$TASK_ID" --agent-id <agent-id> --command abort
+
+# Pause agent
+npx tsx src/cli/coordination/agent-messaging.ts send \
+  --task-id "$TASK_ID" --agent-id <agent-id> --command pause \
+  --payload '{"seconds": 30}'
+```
 
 ## Prerequisites
 

package/.claude/commands/cfn-loop-frontend.md

@@ -561,7 +561,7 @@ Before running frontend CFN Loop:
 
 - Guide: `.claude/commands/cfn/CFN_LOOP_FRONTEND.md` (742 lines, complete workflow)
 - Coordinator: `.claude/agents/cfn-dev-team/coordinators/cfn-frontend-coordinator.md`
-- Task Mode: `.claude/commands/cfn/CFN_LOOP_TASK_MODE.md`
+- Task Mode: `.claude/commands/CFN_LOOP_TASK_MODE.md`
 - Standard CFN Loop: `.claude/commands/cfn/cfn-loop.md`
 
 ---

package/.claude/commands/cfn-loop-task.md

@@ -106,7 +106,7 @@ You must execute this CFN Loop directly using the Task() tool to spawn agents.
 Read the complete Task Mode guide for detailed workflow:
 
 ```
-Read('.claude/commands/cfn/CFN_LOOP_TASK_MODE.md')
+Read('.claude/commands/CFN_LOOP_TASK_MODE.md')
 ```
 
 **Expected output:** Complete guide with agent selection, workflow steps, helper scripts
@@ -450,7 +450,7 @@ parse-decision.sh --output "$PO_OUTPUT"
 
 ## Related Documentation
 
-- **Task Mode Guide**: `.claude/commands/cfn/CFN_LOOP_TASK_MODE.md` (complete reference)
+- **Task Mode Guide**: `.claude/commands/CFN_LOOP_TASK_MODE.md` (complete reference)
 - Coordinator Parameters: `.claude/commands/cfn/CFN_COORDINATOR_PARAMETERS.md`
 - Agent Output Standards: `docs/AGENT_OUTPUT_STANDARDS.md`
 - ACE System: `.claude/skills/cfn-ace-system/SKILL.md`

package/.claude/commands/deprecated/cfn-loop.md

@@ -95,7 +95,7 @@ Extract parameters from command:
 
 ```javascript
 // Read Task Mode guide for agent specialization and workflow
-const taskModeGuide = await Read('.claude/commands/cfn/CFN_LOOP_TASK_MODE.md');
+const taskModeGuide = await Read('.claude/commands/CFN_LOOP_TASK_MODE.md');
 
 // Guide provides:
 // - Agent specialization (Loop 3: implementers, Loop 2: validators, Loop 4: PO)
@@ -274,7 +274,7 @@ Main Chat does NOT spawn a coordinator. Instead, it coordinates directly followi
 
 ```javascript
 // Step 1: Read Task Mode Guide
-const guide = await Read('.claude/commands/cfn/CFN_LOOP_TASK_MODE.md');
+const guide = await Read('.claude/commands/CFN_LOOP_TASK_MODE.md');
 
 // Step 2: Analyze Task Complexity (from guide)
 const complexity = analyzeComplexity({

package/.claude/hooks/cfn-invoke-post-edit.sh

@@ -38,6 +38,28 @@ set -euo pipefail
 SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
 CONFIG_FILE="$SCRIPT_DIR/cfn-post-edit.config.json"
 
+# Ensure jq is available (fallback to local download if sudo unavailable)
+JQ_CMD="jq"
+if ! command -v jq >/dev/null 2>&1; then
+    JQ_FALLBACK="$SCRIPT_DIR/../tools/jq"
+    if [ ! -x "$JQ_FALLBACK" ]; then
+        mkdir -p "$SCRIPT_DIR/../tools"
+        if command -v curl >/dev/null 2>&1; then
+            curl -fsSL -o "$JQ_FALLBACK" https://github.com/stedolan/jq/releases/download/jq-1.6/jq-linux64 && chmod +x "$JQ_FALLBACK" || true
+        elif command -v wget >/dev/null 2>&1; then
+            wget -q -O "$JQ_FALLBACK" https://github.com/stedolan/jq/releases/download/jq-1.6/jq-linux64 && chmod +x "$JQ_FALLBACK" || true
+        fi
+    fi
+    if [ -x "$JQ_FALLBACK" ]; then
+        JQ_CMD="$JQ_FALLBACK"
+    else
+        echo "Error: jq not found and download failed. Install jq or ensure curl/wget access." >&2
+        exit 1
+    fi
+else
+    JQ_CMD="$(command -v jq)"
+fi
+
 # Parse arguments
 FILE_PATH=""
 AGENT_ID="${AGENT_ID:-unknown}"
@@ -46,6 +68,10 @@ BLOCKING=false
 while [[ $# -gt 0 ]]; do
     case $1 in
         --agent-id)
+            if [[ -z "${2:-}" ]]; then
+                echo "Error: --agent-id requires a value" >&2
+                exit 1
+            fi
             AGENT_ID="$2"
             shift 2
             ;;
@@ -68,14 +94,14 @@ if [ -z "$FILE_PATH" ]; then
 fi
 
 # Check if hooks are enabled
-ENABLED=$(jq -r '.enabled // true' "$CONFIG_FILE" 2>/dev/null || echo "true")
+ENABLED=$("$JQ_CMD" -r '.enabled // true' "$CONFIG_FILE" 2>/dev/null || echo "true")
 if [ "$ENABLED" != "true" ]; then
     echo "Post-edit hooks disabled in config"
     exit 0
 fi
 
 # Get pipeline path from config
-PIPELINE=$(jq -r '.pipeline // "config/hooks/post-edit-pipeline.js"' "$CONFIG_FILE")
+PIPELINE=$("$JQ_CMD" -r '.pipeline // "config/hooks/post-edit-pipeline.js"' "$CONFIG_FILE")
 
 # Build memory key
 MEMORY_KEY="swarm/${AGENT_ID}/hook-results"
@@ -92,10 +118,10 @@ if [ "$BLOCKING" = true ] && [ $EXIT_CODE -ne 0 ]; then
 fi
 
 # Publish to Redis if enabled
-REDIS_ENABLED=$(jq -r '.redis.enabled // false' "$CONFIG_FILE")
+REDIS_ENABLED=$("$JQ_CMD" -r '.redis.enabled // false' "$CONFIG_FILE")
 if [ "$REDIS_ENABLED" = "true" ] && command -v redis-cli >/dev/null 2>&1; then
-    CHANNEL=$(jq -r '.redis.publishChannel // "swarm:hooks:post-edit"' "$CONFIG_FILE")
-    MESSAGE=$(jq -n \
+    CHANNEL=$("$JQ_CMD" -r '.redis.publishChannel // "swarm:hooks:post-edit"' "$CONFIG_FILE")
+    MESSAGE=$("$JQ_CMD" -n \
         --arg file "$FILE_PATH" \
         --arg agent "$AGENT_ID" \
         --arg exit "$EXIT_CODE" \

package/.claude/hooks/cfn-post-edit.config.json

@@ -10,7 +10,8 @@
     "1": "ERROR",
     "2": "SYNTAX_ERROR",
     "9": "BASH_VALIDATOR_ERROR",
-    "10": "BASH_VALIDATOR_WARNING"
+    "10": "BASH_VALIDATOR_WARNING",
+    "11": "CREDENTIAL_DETECTED"
   },
   "redis": {
     "enabled": true,
@@ -33,12 +34,18 @@
       "enabled": true,
       "validators": ["pipe-safety", "dependency-checker", "line-endings"],
       "timeout": 5000
+    },
+    "credentials": {
+      "enabled": true,
+      "validator": ".claude/hooks/validators/credential-scanner.sh",
+      "blocking": true,
+      "timeout": 10000
     }
   },
   "feedback": {
     "provideSuggestions": true,
     "autoFixable": ["LINT_ISSUES"],
     "nonBlocking": ["TYPE_WARNING", "LINT_ISSUES", "BASH_VALIDATOR_WARNING"],
-    "blocking": ["SYNTAX_ERROR", "BASH_VALIDATOR_ERROR"]
+    "blocking": ["SYNTAX_ERROR", "BASH_VALIDATOR_ERROR", "CREDENTIAL_DETECTED"]
   }
 }

package/.claude/root-claude-distribute/CFN-CLAUDE.md

@@ -486,7 +486,7 @@ Implement comprehensive test suites that validate both functional requirements a
 - CFN Loop Validation: `.claude/skills/cfn-loop-validation/SKILL.md`
 
 **CFN Loop Documentation:**
-- **Task Mode Guide**: `.claude/commands/cfn/CFN_LOOP_TASK_MODE.md` (agent specialization, sprint workflow, backlog management, adaptive validator scaling)
+- **Task Mode Guide**: `.claude/commands/CFN_LOOP_TASK_MODE.md` (agent specialization, sprint workflow, backlog management, adaptive validator scaling)
 - Coordinator Parameters: `.claude/commands/cfn/CFN_COORDINATOR_PARAMETERS.md`
 
 **Migration Analytics:**

package/.claude/skills/cfn-backlog-management/SKILL.md

@@ -195,5 +195,5 @@ grep -B 2 "Category: Optimization" readme/BACKLOG.md
 ## References
 
 - **STRAT-025**: Explicit Deliverable Tracking (adaptive context)
-- **CFN Loop Documentation**: `.claude/commands/cfn/CFN_LOOP_TASK_MODE.md`
+- **CFN Loop Documentation**: `.claude/commands/CFN_LOOP_TASK_MODE.md`
 - **Sprint Execution**: CLAUDE.md Section 6 - Sprint Context Injection

package/.claude/skills/cfn-loop-orchestration/NORTH_STAR_INDEX.md

@@ -289,7 +289,7 @@ The North Star test simulates a complete CFN Loop with progressive improvement:
 - [README.md](../../../README.md) - Project overview
 
 ### CFN Loop Documentation
-- [.claude/commands/cfn/CFN_LOOP_TASK_MODE.md](../../commands/cfn/CFN_LOOP_TASK_MODE.md) - Task mode guide
+- [.claude/commands/CFN_LOOP_TASK_MODE.md](../../commands/cfn/CFN_LOOP_TASK_MODE.md) - Task mode guide
 - [.claude/commands/cfn/CFN_COORDINATOR_PARAMETERS.md](../../commands/cfn/CFN_COORDINATOR_PARAMETERS.md) - Coordinator parameters
 
 ### Test Documentation

package/claude-assets/agents/cfn-dev-team/analysts/root-cause-analyst.md

@@ -1,8 +1,8 @@
 ---
 name: root-cause-analyst
 description: MUST BE USED when investigating technical issues, bugs, system failures to identify true root causes. Use PROACTIVELY for deep technical investigation, error analysis, failure diagnosis, debugging complex issues. Keywords - root cause, investigation, bug analysis, failure diagnosis, debugging, error tracing, issue investigation
-tools: [Bash, Grep, Glob]
-model: sonnet
+tools: [Bash, Grep, Glob, Read]
+model: opus
 type: specialist
 acl_level: 2
 capabilities: [root-cause-analysis, investigation, debugging, error-tracing, system-analysis]

package/claude-assets/agents/cfn-dev-team/architecture/base-template-generator.md

@@ -1,6 +1,6 @@
 ---
 name: base-template-generator
-description: MUST BE USED when creating foundational templates, boilerplate code, starter configurations, or scaffolding new projects/components/features. use PROACTIVELY for generating component templates, API endpoint skeletons, database model structures, configuration files, test suite scaffolding, documentation templates, build configurations, project initialization, starter kits, module boilerplate. ALWAYS delegate when user asks to "generate template", "create boilerplate", "scaffold", "initialize project", "setup starter", "create base structure", "generate skeleton", "setup configuration", "create starter template". Keywords - template, boilerplate, scaffold, generate, starter, skeleton, base structure, foundational code, setup, initialization, configuration template, component template, API template, model template, test template, documentation template, project setup, module template, starter kit, base configuration
+description: MUST BE USED when creating templates, boilerplate code, scaffolding projects/components. Use PROACTIVELY for component templates, API skeletons, configuration files. Keywords - template, boilerplate, scaffold, starter, skeleton
 tools: Read, Write, Edit, Bash, Glob, Grep, TodoWrite
 model: haiku
 color: orange

package/claude-assets/agents/cfn-dev-team/coordinators/cfn-frontend-coordinator.md

@@ -1,6 +1,6 @@
 ---
 name: cfn-frontend-coordinator
-description: MUST BE USED for frontend CFN Loops with visual iteration workflow. Coordinates mockup analysis, brand guidelines, screenshot/video validation. Use PROACTIVELY for UI development, visual design implementation, frontend components. Keywords - frontend, UI, mockup, visual, screenshot, video, brand-guidelines, design-first, playwright
+description: MUST BE USED for frontend development coordination, React workflows, UI implementation. Use PROACTIVELY for component development. Keywords - frontend, react, UI, coordination
 tools: [Read, Bash, Write, Grep, mcp__zai-mcp-server__analyze_image, mcp__zai-mcp-server__analyze_video]
 model: sonnet
 type: coordinator
@@ -879,7 +879,7 @@ Test Execution Summary:
 ## Related Documentation
 
 - Guide: `.claude/commands/cfn/CFN_LOOP_FRONTEND.md`
-- Task Mode Guide: `.claude/commands/cfn/CFN_LOOP_TASK_MODE.md`
+- Task Mode Guide: `.claude/commands/CFN_LOOP_TASK_MODE.md`
 - Coordinator Parameters: `.claude/commands/cfn/CFN_COORDINATOR_PARAMETERS.md`
 - Standard CFN Loop: `.claude/commands/cfn/cfn-loop.md`
 - Agent Coordination: Dynamic coordination layer

package/claude-assets/agents/cfn-dev-team/coordinators/handoff-coordinator.md

@@ -1,6 +1,6 @@
 ---
 name: handoff-coordinator
-description: MUST BE USED when creating session handoff documentation for team transitions or new session context reset. Use PROACTIVELY for session-transition, context-extraction, team-handoff, context-reset. Keywords - handoff, session-transition, context-extraction, team-handoff, session-documentation, context-reset, new-session, pickup-context
+description: MUST BE USED for agent handoffs, task delegation, workflow transitions. Use PROACTIVELY for multi-agent coordination, context transfer. Keywords - handoff, delegation, coordination, workflow
 tools: [Read, Bash, Grep, Glob, Write, TodoWrite]
 model: sonnet
 type: coordinator

package/claude-assets/agents/cfn-dev-team/dev-ops/devops-engineer.md

@@ -1,6 +1,6 @@
 ---
 name: devops-engineer
-description: MUST BE USED for cloud infrastructure, DevOps automation, and platform engineering. Use PROACTIVELY for CI/CD, containerization, Kubernetes, IaC, monitoring, security automation. ALWAYS delegate when user asks to deploy, setup infrastructure, configure pipelines. Keywords - DevOps, infrastructure, CI/CD, Kubernetes, Docker, Terraform, cloud
+description: MUST BE USED for CI/CD pipelines, infrastructure automation, deployment. Use PROACTIVELY for build automation, release management. Keywords - devops, CI/CD, deployment, automation
 tools: [Read, Write, Edit, Bash, TodoWrite]
 model: haiku
 color: green

package/claude-assets/agents/cfn-dev-team/dev-ops/docker-specialist.md

@@ -1,8 +1,8 @@
 ---
 name: docker-specialist
-description: MUST BE USED for Docker containerization, intelligent coordinator debugging, multi-stage builds, and container security. Use PROACTIVELY for Dockerfile creation, coordinator architectural fixes, Bug 4 resolution, wave spawning, memory budgets, Redis coordination patterns, container status tracking. ALWAYS delegate for Docker coordinator infinite wait loops, task distribution mismatches, integration testing. Keywords - Docker, coordinator, Bug 4, wave spawning, memory budget, Redis queue, container status, architectural mismatch, infinite wait, integration test
+description: MUST BE USED for Docker containerization, coordinator debugging, multi-stage builds, Bug 4 resolution. Keywords - Docker, coordinator, wave spawning, Redis, container status, integration test
 tools: [Read, Write, Edit, Bash, Grep, Glob, TodoWrite]
-model: sonnet
+model: opus
 type: specialist
 skills: [docker-build]
 capabilities: [docker-containerization, multi-stage-builds, container-security, image-optimization, docker-compose, registry-management, coordinator-debugging, wave-spawning, memory-budgeting]

package/claude-assets/agents/cfn-dev-team/dev-ops/github-commit-agent.md

@@ -1,6 +1,6 @@
 ---
 name: github-commit-agent
-description: MUST BE USED when creating git commits with CI/CD monitoring and automated workflows. Use PROACTIVELY for commit creation, push operations, pipeline monitoring, conventional commits. ALWAYS delegate when user asks to "commit changes", "create commit", "push to github", "monitor CI/CD". Keywords - git commit, github, CI/CD, pipeline, conventional commits, automated workflow
+description: MUST BE USED when creating git commits with CI/CD monitoring. Use PROACTIVELY for commit creation, push operations, conventional commits. Keywords - git, github, CI/CD, pipeline, commit
 tools: [Bash, Read, Grep, Glob, BashOutput, TodoWrite]
 model: haiku
 color: purple
@@ -112,4 +112,4 @@ Complete your work and provide a structured response with:
 - List of findings or deliverables
 - Any recommendations made
 
-**Note:** Coordination instructions are provided when spawned via CLI.
+**Note:** Coordination instructions are provided when spawned via CLI.

package/claude-assets/agents/cfn-dev-team/dev-ops/kubernetes-specialist.md

@@ -1,6 +1,6 @@
 ---
 name: kubernetes-specialist
-description: MUST BE USED for Kubernetes cluster management, Helm charts, operators, service mesh, and container orchestration. Use PROACTIVELY for K8s deployments, autoscaling, ingress, StatefulSets, CRDs, monitoring. ALWAYS delegate for "deploy to Kubernetes", "Helm chart", "K8s operator", "service mesh", "container orchestration". Keywords - Kubernetes, k8s, Helm, operators, containers, pods, deployments, ingress, service mesh, Istio, autoscaling
+description: MUST BE USED for Kubernetes cluster management, Helm charts, operators, service mesh. Use PROACTIVELY for K8s deployments, autoscaling, ingress. Keywords - kubernetes, k8s, helm, containers, pods
 tools: [Read, Write, Edit, Bash, Grep, Glob, TodoWrite]
 model: sonnet
 type: specialist

package/claude-assets/agents/cfn-dev-team/developers/api-gateway-specialist.md

@@ -1,6 +1,6 @@
 ---
 name: api-gateway-specialist
-description: MUST BE USED for API gateway configuration, Kong, AWS API Gateway, Nginx, rate limiting, authentication, and API management. Use PROACTIVELY for gateway setup, routing rules, OAuth2/JWT configuration, rate limiting, API versioning, load balancing. ALWAYS delegate for "API gateway", "Kong configuration", "rate limiting", "OAuth2 setup", "API routing", "reverse proxy". Keywords - API gateway, Kong, AWS API Gateway, Nginx, reverse proxy, rate limiting, OAuth2, JWT, authentication, routing, load balancing
+description: MUST BE USED for API gateway design, routing, rate limiting, authentication. Use PROACTIVELY for gateway configuration, API security, traffic management. Keywords - gateway, API, routing, security
 tools: [Read, Write, Edit, Bash, Grep, Glob, TodoWrite]
 model: sonnet
 type: specialist

package/claude-assets/agents/cfn-dev-team/developers/data/data-engineer.md

@@ -1,6 +1,6 @@
 ---
 name: data-engineer
-description: MUST BE USED for data pipeline design, ETL processes, data warehousing, and data quality. Use PROACTIVELY for data ingestion, transformation, orchestration, data lakes, streaming. ALWAYS delegate for "ETL pipeline", "data warehouse", "data lake", "Apache Airflow", "data quality". Keywords - ETL, data pipeline, Airflow, data warehouse, data lake, streaming, Kafka, Spark, dbt, data quality
+description: MUST BE USED for data pipelines, ETL processes, data warehousing. Use PROACTIVELY for data transformation, batch processing, streaming. Keywords - data, ETL, pipeline, warehouse, processing
 tools: [Read, Write, Edit, Bash, Grep, Glob, TodoWrite]
 model: sonnet
 type: specialist

package/claude-assets/agents/cfn-dev-team/developers/database/database-architect.md

@@ -1,6 +1,6 @@
 ---
 name: database-architect
-description: MUST BE USED for database schema design, migration strategies, query optimization, and data modeling. Use PROACTIVELY for relational/NoSQL design, indexing strategies, normalization, data integrity. ALWAYS delegate for "design schema", "database migration", "optimize queries", "data modeling". Keywords - database, schema, SQL, PostgreSQL, MongoDB, migrations, indexing, normalization, query optimization
+description: MUST BE USED for database design, schema optimization, query performance. Use PROACTIVELY for data modeling, indexing, migrations. Keywords - database, schema, SQL, optimization, modeling
 tools: [Read, Write, Edit, Bash, Grep, Glob, TodoWrite]
 model: sonnet
 type: specialist

package/claude-assets/agents/cfn-dev-team/developers/frontend/typescript-specialist.md

@@ -1,6 +1,6 @@
 ---
 name: typescript-specialist
-description: MUST BE USED for TypeScript development, type system design, and type safety implementation. Use PROACTIVELY for type definitions, generics, utility types, advanced TypeScript patterns, and compile-time validation. Keywords - TypeScript types, generics, interfaces, type safety, utility types, advanced patterns, type guards, conditional types
+description: MUST BE USED for TypeScript development, type safety, advanced typing. Use PROACTIVELY for type definitions, generics. Keywords - typescript, types, type safety, generics
 tools: [Read, Write, Edit, Bash, Grep, Glob, TodoWrite]
 model: haiku
 type: specialist

package/claude-assets/agents/cfn-dev-team/developers/frontend/ui-designer.md

@@ -1,6 +1,6 @@
 ---
 name: ui-designer
-description: MUST BE USED when designing user interfaces and user experience for web applications. Use PROACTIVELY for responsive design, component libraries, and modern UI/UX patterns. ALWAYS delegate when user asks to "UI design", "user interface", "UX design", "component design". Keywords - UI design, user experience, responsive design, component libraries, interface design
+description: MUST BE USED for UI/UX design, component libraries, design systems. Use PROACTIVELY for interface design, accessibility, responsive layouts. Keywords - UI, UX, design, components, accessibility
 tools: [Read, Write, Edit, Bash, TodoWrite]
 model: haiku
 color: mediumpurple

package/claude-assets/agents/cfn-dev-team/developers/graphql-specialist.md

@@ -1,6 +1,6 @@
 ---
 name: graphql-specialist
-description: MUST BE USED for GraphQL schema design, resolver implementation, federation, and performance optimization. Use PROACTIVELY for GraphQL APIs, schema stitching, Apollo Server, federation, subscriptions, DataLoader. ALWAYS delegate for "GraphQL API", "schema design", "resolvers", "federation", "GraphQL subscriptions". Keywords - GraphQL, schema, resolvers, mutations, queries, subscriptions, Apollo, federation, DataLoader, N+1
+description: MUST BE USED for GraphQL API design, schema definition, resolver implementation. Use PROACTIVELY for GraphQL optimization, federation. Keywords - GraphQL, schema, resolvers, API, federation
 tools: [Read, Write, Edit, Bash, Grep, Glob, TodoWrite]
 model: sonnet
 type: specialist

package/claude-assets/agents/cfn-dev-team/documentation/pseudocode.md

@@ -1,6 +1,6 @@
 ---
 name: pseudocode
-description: MUST BE USED when designing algorithms, logic flows, or data structures in SPARC methodology. Use PROACTIVELY for algorithm design, pseudocode creation, complexity analysis, data structure selection, logic flow mapping. Keywords - SPARC, pseudocode, algorithm, logic flow, complexity analysis, Big-O, optimization
+description: MUST BE USED for algorithm design, logic planning, code outline creation. Use PROACTIVELY for problem decomposition, planning. Keywords - pseudocode, algorithm, logic, planning
 tools: [Read, Write, Edit, Bash, Grep, Glob, TodoWrite]
 model: haiku
 color: indigo

package/claude-assets/agents/cfn-dev-team/product-owners/accessibility-advocate-persona.md

@@ -1,6 +1,6 @@
 ---
 name: accessibility-advocate-persona
-description: MUST BE USED when evaluating accessibility, WCAG compliance, assistive technology support, and inclusive design. Use PROACTIVELY for accessibility audits, ARIA implementation, keyboard navigation, screen reader testing, color contrast validation. Keywords - accessibility, WCAG, ARIA, screen reader, keyboard navigation, inclusive design, a11y
+description: MUST BE USED for accessibility compliance, WCAG validation, inclusive design. Use PROACTIVELY for a11y testing, screen reader support. Keywords - accessibility, a11y, WCAG, inclusive
 tools: [Read, Write, Edit, Bash, Grep, Glob, TodoWrite]
 model: haiku
 color: violet