claude-flow-novice 2.15.11 → 2.16.1

package/.claude/skills/pre-edit-backup/backup.sh.backup

@@ -0,0 +1,107 @@
+#!/bin/bash
+
+##############################################################################
+# Pre-Edit Backup Script - Creates safe file backups before modifications
+# Version: 1.0.0
+##############################################################################
+
+set -euo pipefail
+
+# Function to create backup of a file before editing
+create_backup() {
+    local file_path="$1"
+    local agent_id="${2:-unknown}"
+    local project_root="${3:-$(pwd)}"
+
+    # Validate inputs
+    if [[ -z "$file_path" ]]; then
+        echo "Error: File path is required" >&2
+        exit 1
+    fi
+
+    # Check if file exists
+    if [[ ! -f "$file_path" ]]; then
+        echo "Warning: File does not exist: $file_path" >&2
+        # Create empty backup path for new files
+        echo "$project_root/.backups/$agent_id/new-file-$(date +%s)-$(echo "$file_path" | tr '/' '_' | tr ' ' '_')"
+        return 0
+    fi
+
+    # Create backup directory structure
+    local backup_dir="$project_root/.backups/$agent_id"
+    local timestamp=$(date +%s)
+    local file_hash=$(md5sum "$file_path" | cut -d' ' -f1)
+    local backup_name="${timestamp}_${file_hash}"
+
+    # Create full backup path
+    local full_backup_path="$backup_dir/$backup_name"
+
+    # Create backup directory
+    mkdir -p "$full_backup_path"
+
+    # Copy original file to backup location
+    cp "$file_path" "$full_backup_path/original"
+
+    # Store backup metadata
+    cat > "$full_backup_path/metadata.json" << EOF
+{
+  "timestamp": "$timestamp",
+  "agent_id": "$agent_id",
+  "original_file": "$file_path",
+  "file_hash": "$file_hash",
+  "backup_path": "$full_backup_path",
+  "created_at": "$(date -u +%Y-%m-%dT%H:%M:%SZ)"
+}
+EOF
+
+    # Create revert script
+    cat > "$full_backup_path/revert.sh" << EOF
+#!/bin/bash
+# Revert script for $file_path
+set -euo pipefail
+
+echo "Reverting file: $file_path"
+cp "$full_backup_path/original" "$file_path"
+echo "✅ File reverted successfully"
+EOF
+
+    chmod +x "$full_backup_path/revert.sh"
+
+    # Output backup path for caller
+    echo "$full_backup_path"
+
+    echo "✅ Backup created: $full_backup_path" >&2
+}
+
+# Main execution
+if [[ "${BASH_SOURCE[0]}" == "${0}" ]]; then
+    # Script called directly
+    if [[ $# -lt 1 ]]; then
+        echo "Usage: $0 <file_path> [--agent-id <id>] [--project-root <path>]" >&2
+        exit 1
+    fi
+
+    file_path="$1"
+    agent_id="unknown"
+    project_root="$(pwd)"
+
+    # Parse optional arguments
+    while [[ $# -gt 0 ]]; do
+        case $1 in
+            --agent-id)
+                agent_id="$2"
+                shift 2
+                ;;
+            --project-root)
+                project_root="$2"
+                shift 2
+                ;;
+            *)
+                # Skip unknown arguments
+                shift
+                ;;
+        esac
+    done
+
+    create_backup "$file_path" "$agent_id" "$project_root"
+fi

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
@@ -46,6 +46,7 @@ fi
 
 **Old (Deprecated):**
 ```bash
+```
 
 **New (Required):**
 ```bash
@@ -878,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/consensus-builder.md

@@ -53,6 +53,7 @@ fi
 
 **Old (Deprecated):**
 ```bash
+```
 
 **New (Required):**
 ```bash

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
@@ -44,6 +44,7 @@ fi
 
 **Old (Deprecated):**
 ```bash
+```
 
 **New (Required):**
 ```bash

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

@@ -45,6 +45,7 @@ fi
 
 **Old (Deprecated):**
 ```bash
+```
 
 **New (Required):**
 ```bash

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
@@ -128,6 +128,16 @@ You are an elite DevOps and platform engineer specializing in building scalable,
 
 Remember: The best infrastructure is invisible—seamless, scalable, and empowering developers to deliver value.
 
+## Skill References
+
+### Test-Driven Development
+→ **JSON Validation**: `.claude/skills/json-validation/SKILL.md` - Defensive AGENT_SUCCESS_CRITERIA parsing with injection prevention
+→ **Test Runner**: `.claude/skills/cfn-test-runner/SKILL.md` - Unified test execution with benchmarking and regression detection
+
+### Container & Infrastructure
+→ **Docker Build**: `.claude/skills/docker-build/SKILL.md` - Fast Docker builds using Linux native storage (96% faster)
+→ **Redis Data Extraction**: `.claude/skills/cfn-redis-data-extraction/SKILL.md` - Extract and analyze CFN Loop coordination data
+
 ## Completion Protocol
 
 Complete your work and provide a structured response with:

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]
@@ -17,30 +17,31 @@ model: glm-4.6
 
 ## Success Criteria Awareness (REQUIRED - Phase 2 TDD)
 
-### 1. Read Success Criteria
-Before starting work, read test requirements from environment:
+### 1. JSON Validation & Success Criteria Parsing
+Use the centralized JSON validation skill for defensive AGENT_SUCCESS_CRITERIA parsing:
+
+**Skill Reference:** `.claude/skills/json-validation/SKILL.md`
+
 ```bash
-if [[ -n "${AGENT_SUCCESS_CRITERIA:-}" ]]; then
-    # Validate JSON before parsing
-    if ! echo "$AGENT_SUCCESS_CRITERIA" | jq -e '.' >/dev/null 2>&1; then
-        echo "❌ Invalid JSON in AGENT_SUCCESS_CRITERIA" >&2
-        exit 1
-    fi
-
-    CRITERIA=$(echo "$AGENT_SUCCESS_CRITERIA" | jq -r '.')
-    TEST_SUITES=$(echo "$CRITERIA" | jq -r '.test_suites[] // empty')
-
-    if [[ -n "$TEST_SUITES" ]]; then
-        echo "📋 Success Criteria Loaded:"
-        echo "$TEST_SUITES" | jq -r '.name // "unnamed"'
-    fi
-fi
+# Source the skill for safe JSON validation
+source .claude/skills/json-validation/validate-success-criteria.sh
+
+# Validate and parse with injection attack prevention
+validate_success_criteria || exit 1
+
+# Access parsed data
+list_test_suites
 ```
 
+**Features:**
+- Prevents JSON injection attacks (CVSS 8.2)
+- Handles missing/malformed data gracefully
+- No external dependencies beyond jq
+
 ### 2. TDD Protocol (MANDATORY)
 
 **Write Tests First (15-20 min):**
-- Extract test requirements from success criteria
+- Extract test requirements from success criteria (via skill above)
 - Write failing tests for each requirement
 - Ensure test coverage ≥80%
 
@@ -54,26 +55,25 @@ fi
 - Verify pass rate meets threshold (Standard: ≥95%)
 - Check coverage: `npm run coverage`
 
-### 3. Report Test Results (NOT Confidence)
+### 3. Test Execution & Results Parsing
+Use the centralized test runner skill for consistent test result collection:
 
-**Old (Deprecated):**
-```bash
-# Not shown - deprecated pattern
-```
+**Skill Reference:** `.claude/skills/cfn-test-runner/SKILL.md`
 
-**New (Required):**
 ```bash
-# Execute tests and capture output
-TEST_OUTPUT=$(npm test 2>&1)
-
-# Parse natively (no external dependencies)
-PASS=$(echo "$TEST_OUTPUT" | grep -oP '\d+(?= passing)' || echo "0")
-FAIL=$(echo "$TEST_OUTPUT" | grep -oP '\d+(?= failing)' || echo "0")
-TOTAL=$((PASS + FAIL))
-RATE=$(awk "BEGIN {if ($TOTAL > 0) printf \"%.2f\", $PASS/$TOTAL; else print \"0.00\"}")
-
+# Execute tests with benchmarking
+./.claude/skills/cfn-test-runner/run-all-tests.sh \
+  --suite all \
+  --benchmark \
+  --detect-regressions
 ```
 
+**Captures:**
+- Test pass/fail counts
+- Performance metrics
+- Regression detection
+- Historical comparisons
+
 # Docker Specialist Agent
 
 ## 🚨 CRITICAL: WSL2 Build Performance Requirement
@@ -150,6 +150,29 @@ Fast Docker image building using Linux native storage for 96% faster builds (755
 
 **See:** `.claude/skills/docker-build/SKILL.md` for complete documentation
 
+### cfn-redis-data-extraction
+Extract and analyze complete Redis coordination data from completed CFN Loop tasks.
+
+**Use Cases:**
+- Analyze coordinator performance metrics
+- Extract task completion timelines
+- Review agent success/failure rates
+- Audit multi-agent coordination decisions
+
+**Quick Use:**
+```bash
+# Extract coordination data from completed task
+npx claude-flow-novice skill cfn-redis-data-extraction \
+  --task-id "cfn-cli-XXXXXXX-XXXXX"
+
+# Extract with performance metrics
+npx claude-flow-novice skill cfn-redis-data-extraction \
+  --task-id "cfn-cli-XXXXXXX-XXXXX" \
+  --include-performance=true
+```
+
+**See:** `.claude/skills/cfn-redis-data-extraction/SKILL.md` for complete documentation
+
 ---
 
 ## 🚨 CRITICAL: Docker Coordinator Known Issues

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
@@ -18,63 +18,63 @@ model: glm-4.6
 
 ## Success Criteria Awareness (REQUIRED - Phase 2 TDD)
 
-### 1. Read Success Criteria
-Before starting work, read test requirements from environment:
+### 1. JSON Validation & Success Criteria Parsing
+Use the centralized JSON validation skill for defensive AGENT_SUCCESS_CRITERIA parsing:
+
+**Skill Reference:** `.claude/skills/json-validation/SKILL.md`
+
 ```bash
-if [[ -n "${AGENT_SUCCESS_CRITERIA:-}" ]]; then
-    # Validate JSON before parsing
-    if ! echo "$AGENT_SUCCESS_CRITERIA" | jq -e '.' >/dev/null 2>&1; then
-        echo "❌ Invalid JSON in AGENT_SUCCESS_CRITERIA" >&2
-        exit 1
-    fi
-
-    CRITERIA=$(echo "$AGENT_SUCCESS_CRITERIA" | jq -r '.')
-    TEST_SUITES=$(echo "$CRITERIA" | jq -r '.test_suites[] // empty')
-
-    if [[ -n "$TEST_SUITES" ]]; then
-        echo "📋 Success Criteria Loaded:"
-        echo "$TEST_SUITES" | jq -r '.name // "unnamed"'
-    fi
-fi
+# Source the skill for safe JSON validation
+source .claude/skills/json-validation/validate-success-criteria.sh
+
+# Validate and parse with injection attack prevention
+validate_success_criteria || exit 1
+
+# Access parsed data
+list_test_suites
 ```
 
+**Features:**
+- Prevents JSON injection attacks (CVSS 8.2)
+- Handles missing/malformed data gracefully
+- No external dependencies beyond jq
+
 ### 2. TDD Protocol (MANDATORY)
 
 **Write Tests First (15-20 min):**
-- Extract test requirements from success criteria
+- Extract test requirements from success criteria (via skill above)
 - Write failing tests for each requirement
 - Ensure test coverage ≥80%
 
 **Implement (30-40 min):**
 - Write minimum code to pass tests
-- Run tests continuously (`npm test --watch` or framework equivalent)
+- Run tests continuously (kubectl test, helm test, or framework equivalent)
 - Refactor for quality
 
 **Validate (5 min):**
-- Run full test suite: `npm test` (or framework command from criteria)
+- Run full test suite: `npm test` or `kubectl test` (per framework)
 - Verify pass rate meets threshold (Standard: ≥95%)
-- Check coverage: `npm run coverage`
+- Check coverage: appropriate to your testing framework
 
-### 3. Report Test Results (NOT Confidence)
+### 3. Test Execution & Results Parsing
+Use the centralized test runner skill for consistent test result collection:
 
-**Old (Deprecated):**
-```bash
-# Not shown - deprecated pattern
-```
+**Skill Reference:** `.claude/skills/cfn-test-runner/SKILL.md`
 
-**New (Required):**
 ```bash
-# Execute tests and capture output
-TEST_OUTPUT=$(npm test 2>&1)
-
-# Parse natively (no external dependencies)
-PASS=$(echo "$TEST_OUTPUT" | grep -oP '\d+(?= passing)' || echo "0")
-FAIL=$(echo "$TEST_OUTPUT" | grep -oP '\d+(?= failing)' || echo "0")
-TOTAL=$((PASS + FAIL))
-RATE=$(awk "BEGIN {if ($TOTAL > 0) printf \"%.2f\", $PASS/$TOTAL; else print \"0.00\"}")
-
+# Execute tests with benchmarking
+./.claude/skills/cfn-test-runner/run-all-tests.sh \
+  --suite all \
+  --benchmark \
+  --detect-regressions
 ```
 
+**Captures:**
+- Test pass/fail counts
+- Performance metrics
+- Regression detection
+- Historical comparisons
+
 # Kubernetes Specialist Agent
 
 ## Core Responsibilities
@@ -595,6 +595,16 @@ Before reporting high confidence:
 4. **Monitoring Setup**: Prometheus metrics, Grafana dashboards
 5. **CI/CD Integration**: GitOps workflows, ArgoCD applications
 
+## Skill References
+
+### Test-Driven Development
+→ **JSON Validation**: `.claude/skills/json-validation/SKILL.md` - Defensive AGENT_SUCCESS_CRITERIA parsing with injection prevention
+→ **Test Runner**: `.claude/skills/cfn-test-runner/SKILL.md` - Unified test execution with benchmarking and regression detection
+
+### Container & Orchestration
+→ **Docker Build**: `.claude/skills/docker-build/SKILL.md` - Fast Docker builds using Linux native storage (96% faster)
+→ **Redis Data Extraction**: `.claude/skills/cfn-redis-data-extraction/SKILL.md` - Extract and analyze CFN Loop coordination data
+
 ## Completion Protocol
 
 Complete your work and provide a structured response with:

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
@@ -29,23 +29,18 @@ model: glm-4.6
 ## Success Criteria Awareness (REQUIRED - Phase 2 TDD)
 
 ### 1. Read Success Criteria
-Before starting work, read test requirements from environment:
+Before starting work, use the JSON validation skill:
+
+**Skill Reference:** `.claude/skills/json-validation/validate-success-criteria.sh`
+- Validates `AGENT_SUCCESS_CRITERIA` JSON safely
+- Prevents injection attacks
+- Provides error handling
+
+Usage:
 ```bash
-if [[ -n "${AGENT_SUCCESS_CRITERIA:-}" ]]; then
-    # Validate JSON before parsing
-    if ! echo "$AGENT_SUCCESS_CRITERIA" | jq -e '.' >/dev/null 2>&1; then
-        echo "❌ Invalid JSON in AGENT_SUCCESS_CRITERIA" >&2
-        exit 1
-    fi
-
-    CRITERIA=$(echo "$AGENT_SUCCESS_CRITERIA" | jq -r '.')
-    TEST_SUITES=$(echo "$CRITERIA" | jq -r '.test_suites[] // empty')
-
-    if [[ -n "$TEST_SUITES" ]]; then
-        echo "📋 Success Criteria Loaded:"
-        echo "$TEST_SUITES" | jq -r '.name // "unnamed"'
-    fi
-fi
+source .claude/skills/json-validation/validate-success-criteria.sh
+validate_success_criteria || exit 1
+list_test_suites
 ```
 
 ### 2. TDD Protocol (MANDATORY)
@@ -67,7 +62,12 @@ fi
 
 ### 3. Report Test Results (NOT Confidence)
 
-Execute tests and report objective pass/fail metrics:
+Use the test runner skill for parsing and reporting:
+
+**Skill Reference:** `.claude/skills/cfn-test-runner/run-all-tests.sh`
+- Executes test suite with native bash parsing
+- Calculates pass rates and coverage metrics
+- Handles Redis gracefully (automatic failure in Task mode)
 
 ```bash
 # Execute tests and capture output