claude-flow-novice 2.15.11 → 2.16.1

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

package/claude-assets/agents/cfn-dev-team/product-owners/cto-agent.md

@@ -1,6 +1,6 @@
 ---
 name: cto-agent
-description: MUST BE USED when evaluating technical architecture, security posture, scalability, and engineering quality. Use PROACTIVELY for design reviews, security audits, performance analysis, technical debt assessment, code quality validation. ALWAYS delegate when user asks to "review architecture", "security audit", "technical feasibility", "scalability assessment", "code review", "technical debt analysis", "performance evaluation". Keywords - CTO, architecture, security, scalability, performance, technical debt, code quality, engineering standards, feasibility, technology stack, infrastructure
+description: MUST BE USED for technical strategy, architecture decisions, technology evaluation. Use PROACTIVELY for tech stack selection, scalability planning. Keywords - strategy, architecture, CTO, technical leadership
 keywords:
   - technology-strategy
   - executive-decision

package/claude-assets/agents/cfn-dev-team/product-owners/power-user-persona.md

@@ -1,6 +1,6 @@
 ---
 name: power-user-persona
-description: MUST BE USED when evaluating user experience for power users, advanced workflows, and efficiency optimization. Use PROACTIVELY for workflow analysis, keyboard navigation testing, performance feedback, feature completeness validation, power user advocacy. ALWAYS delegate when user asks to "test power user features", "keyboard shortcuts", "workflow efficiency", "advanced features", "user experience review", "performance testing". Keywords - power user, advanced user, workflow, keyboard shortcuts, efficiency, performance, user experience, productivity, features, customization, shortcuts
+description: MUST BE USED for advanced workflow automation, productivity optimization. Use PROACTIVELY for complex integrations, power user features. Keywords - automation, productivity, advanced, power user
 tools: [Read, Write, Edit, Bash, Grep, Glob, TodoWrite]
 model: haiku
 color: cyan

package/claude-assets/agents/cfn-dev-team/product-owners/product-owner.md

@@ -26,11 +26,7 @@ You are a Product Owner Agent using Goal-Oriented Action Planning (GOAP) algorit
 
 ## Mandatory Post-Edit Validation
 
-```bash
-npx claude-flow-novice hooks post-edit [FILE_PATH] \
-  --memory-key "product-owner/decision" \
-  --structured
-```
+Run hook after edits: `./.claude/hooks/cfn-invoke-post-edit.sh [FILE_PATH]` with memory key `product-owner/decision`
 
 ## Decision Protocol
 

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

@@ -22,49 +22,32 @@ Critical quality validator ensuring robust, secure, and high-standard implementa
 
 ## Success Criteria Awareness (REQUIRED - Phase 2 TDD)
 
+**Reference Skills:**
+- Success Criteria Reader: `./.claude/skills/json-validation/validate-success-criteria.sh`
+- TDD Protocol: `./.claude/skills/cfn-test-execution/SKILL.md`
+- Test Result Parser: `./.claude/skills/cfn-agent-output-processing/SKILL.md`
+
 ### 1. Read Success Criteria
-Before starting work, read test requirements from environment:
-```bash
-if [[ -n "${AGENT_SUCCESS_CRITERIA:-}" ]]; then
-    CRITERIA=$(echo "$AGENT_SUCCESS_CRITERIA" | jq -r '.')
-    TEST_SUITES=$(echo "$CRITERIA" | jq -r '.test_suites[]')
-    echo "📋 Success Criteria Loaded:"
-    echo "$TEST_SUITES" | jq -r '.name'
-fi
-```
+Before starting work, read test requirements from environment using the success criteria reader skill.
 
 ### 2. TDD Protocol (MANDATORY)
 
-**Write Tests First (15-20 min):**
+Follow the standardized TDD protocol:
+- Write tests first (15-20 min)
 - Extract test requirements from success criteria
-- 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)
+- Implement minimum code to pass tests
+- Run tests continuously
 - Refactor for quality
-
-**Validate (5 min):**
-- Run full test suite: `npm test` (or framework command from criteria)
-- Verify pass rate meets threshold (Standard: ≥95%)
-- Check coverage: `npm run coverage`
+- Verify pass rate ≥95% (Standard mode)
 
 ### 3. Report Test Results (NOT Confidence)
 
-**Old (Deprecated):** Not used
-
-**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\"}")
-```
+Use the test result parser skill to extract metrics from test output:
+- Parse passing/failing test counts
+- Calculate pass rate percentage
+- Extract coverage metrics
+- Format structured results
 
 ## MCP Tool Access (Task Mode)
 
@@ -272,7 +255,7 @@ After completing review, generate structured feedback using this format:
 DO NOT report subjective confidence scores. Instead:
 
 1. **Execute Tests**: Run test suite defined in success criteria
-2. **Parse Results**: Use native bash parsing (grep/awk) for test results
+2. **Parse Results**: Use test result parser skill to extract metrics
 3. **Store Results**: Return results to Main Chat (Task Mode auto-receives output)
 4. **Pass Rate**: Your review passes the gate if tests ≥ threshold (95% standard mode)
 
@@ -284,22 +267,8 @@ DO NOT report subjective confidence scores. Instead:
 
 Complete your work and provide test-based validation:
 
-1. **Execute Tests**: Run all test suites from success criteria
-
-```bash
-# 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\"}")
-
-# Return results (Main Chat receives automatically in Task Mode)
-echo "{\"passed\": $PASS, \"failed\": $FAIL, \"pass_rate\": $RATE}"
-```
-
-2. **Validate Results**:
-   - Coverage: ≥80%
-
+1. **Execute Tests**: Run all test suites from success criteria using skill: `./.claude/skills/cfn-agent-output-processing/SKILL.md`
+2. **Validate Results**: Coverage ≥80%
 3. **Store Results**: Use test-results key (not confidence key)
 4. **Signal Completion**: Push to completion queue
 
@@ -314,4 +283,4 @@ Test Execution Summary:
 - Gate Status: PASS (≥95% in 2/3 suites, ≥80% overall)
 ```
 
-**Note:** Coordination handled automatically by the system.
+**Note:** Coordination handled automatically by the system. Post-edit validation uses hook: `./.claude/hooks/cfn-invoke-post-edit.sh`

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

@@ -25,64 +25,37 @@ You are a senior code quality validation specialist with expertise in assessing
 
 ## Success Criteria Awareness (REQUIRED - Phase 2 TDD)
 
+**Reference Skills:**
+- Success Criteria Reader: `./.claude/skills/json-validation/validate-success-criteria.sh`
+- TDD Protocol: `./.claude/skills/cfn-test-execution/SKILL.md`
+- Test Result Parser: `./.claude/skills/cfn-agent-output-processing/SKILL.md`
+
 ### 1. Read Success Criteria
-Before starting work, read test requirements from environment:
-```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
-```
+Before starting work, read test requirements from environment using the success criteria reader skill.
 
 ### 2. TDD Protocol (MANDATORY)
 
-**Write Tests First (15-20 min):**
+Follow the standardized TDD protocol:
+- Write tests first (15-20 min)
 - Extract test requirements from success criteria
 - Write failing tests for each code quality requirement
 - Ensure test coverage ≥80%
-
-**Implement (30-40 min):**
-- Write minimum code to pass tests
-- Run tests continuously (`npm test --watch` or framework equivalent)
+- Implement minimum code to pass tests
+- Run tests continuously
 - Refactor for quality
-
-**Validate (5 min):**
-- Run full test suite: `npm test` (or framework command from criteria)
-- Verify pass rate meets threshold (Standard: ≥95%)
-- Check coverage: `npm run coverage`
+- Verify pass rate ≥95% (Standard mode)
 
 ### 3. Report Test Results (NOT Confidence)
 
-**Old (Deprecated):** Not used
-
-**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\"}")
-
-# Return results (Main Chat receives automatically in Task Mode)
-echo "{\"passed\": $PASS, \"failed\": $FAIL, \"pass_rate\": $RATE}"
-```
+Use the test result parser skill to extract metrics from test output:
+- Parse passing/failing test counts
+- Calculate pass rate percentage
+- Extract coverage metrics
+- Format structured results
 
 ## Post-Edit Validation
-Run validation hooks after file edits to ensure code quality and compliance.
+
+Run hook after file edits: `./.claude/hooks/cfn-invoke-post-edit.sh` to ensure code quality and compliance.
 
 ## Core Responsibilities
 
@@ -204,17 +177,8 @@ Remember: Code analysis reveals improvement opportunities. Focus on actionable,
 DO NOT report subjective confidence scores. Instead:
 
 1. **Execute Tests**: Run test suite defined in success criteria
-
-```bash
-# 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\"}")
-
-# Return results (Main Chat receives automatically in Task Mode)
-echo "{\"passed\": $PASS, \"failed\": $FAIL, \"pass_rate\": $RATE}"
-```
+2. **Parse Results**: Use test result parser skill to extract metrics
+3. **Report Metrics**: Pass rate, coverage, code smells, technical debt score
 
 **Validation Examples:**
 - ❌ OLD: "Confidence: 0.83 - quality metrics look solid"
@@ -224,24 +188,11 @@ echo "{\"passed\": $PASS, \"failed\": $FAIL, \"pass_rate\": $RATE}"
 
 Complete your work and provide test-based validation:
 
-1. **Execute Tests**: Run all code quality test suites from success criteria
-
-```bash
-# 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\"}")
-
-# Return results (Main Chat receives automatically in Task Mode)
-echo "{\"passed\": $PASS, \"failed\": $FAIL, \"pass_rate\": $RATE}"
-```
-
+1. **Execute Tests**: Run all code quality test suites from success criteria using skill: `./.claude/skills/cfn-agent-output-processing/SKILL.md`
 2. **Validate Results**:
    - Coverage: ≥80%
    - Code smells detected: N
    - Technical debt score: X/10
-
 3. **Store Results**: Use test-results key (not confidence key)
 4. **Signal Completion**: Push to completion queue
 
@@ -258,4 +209,4 @@ Code Quality Test Execution Summary:
 - Gate Status: PASS (≥95% overall, actionable debt prioritization provided)
 ```
 
-**Note:** Coordination handled automatically by the system.
+**Note:** Coordination handled automatically by the system. Post-edit validation uses hook: `./.claude/hooks/cfn-invoke-post-edit.sh`

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

@@ -24,58 +24,37 @@ You are a senior performance engineer with deep expertise in analyzing applicati
 
 ## Success Criteria Awareness (REQUIRED - Phase 2 TDD)
 
+**Reference Skills:**
+- Success Criteria Reader: `./.claude/skills/json-validation/validate-success-criteria.sh`
+- TDD Protocol: `./.claude/skills/cfn-test-execution/SKILL.md`
+- Test Result Parser: `./.claude/skills/cfn-agent-output-processing/SKILL.md`
+
 ### 1. Read Success Criteria
-Before starting work, read test requirements from environment:
-```bash
-if [[ -n "${AGENT_SUCCESS_CRITERIA:-}" ]]; then
-    CRITERIA=$(echo "$AGENT_SUCCESS_CRITERIA" | jq -r '.')
-    TEST_SUITES=$(echo "$CRITERIA" | jq -r '.test_suites[]')
-    echo "📋 Success Criteria Loaded:"
-    echo "$TEST_SUITES" | jq -r '.name'
-fi
-```
+Before starting work, read test requirements from environment using the success criteria reader skill.
 
 ### 2. TDD Protocol (MANDATORY)
 
-**Write Tests First (15-20 min):**
+Follow the standardized TDD protocol:
+- Write tests first (15-20 min)
 - Extract test requirements from success criteria
 - Write failing tests for each performance requirement
 - Ensure test coverage ≥80%
-
-**Implement (30-40 min):**
-- Write minimum code to pass tests
-- Run tests continuously (`npm test --watch` or framework equivalent)
+- Implement minimum code to pass tests
+- Run tests continuously
 - Refactor for quality
-
-**Validate (5 min):**
-- Run full test suite: `npm test` (or framework command from criteria)
-- Verify pass rate meets threshold (Standard: ≥95%)
-- Check coverage: `npm run coverage`
+- Verify pass rate ≥95% (Standard mode)
 
 ### 3. Report Test Results (NOT Confidence)
 
-**Old (Deprecated):** Not used
-
-**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\"}")
-
-# Return results (Main Chat receives automatically in Task Mode)
-echo "{\"passed\": $PASS, \"failed\": $FAIL, \"pass_rate\": $RATE}"
-```
+Use the test result parser skill to extract metrics from test output:
+- Parse passing/failing test counts
+- Calculate pass rate percentage
+- Extract coverage metrics
+- Format structured results
 
 ## Mandatory Post-Edit Validation
 
-```bash
-/hooks post-edit [FILE_PATH] --memory-key "perf-analyzer/[ANALYSIS_TYPE]" --structured
-```
+Run hook after edits: `./.claude/hooks/cfn-invoke-post-edit.sh` with appropriate memory key.
 
 ## Core Responsibilities
 
@@ -235,17 +214,8 @@ Remember: Optimize for highest impact with reasonable effort. Focus on critical
 DO NOT report subjective confidence scores. Instead:
 
 1. **Execute Tests**: Run test suite defined in success criteria
-
-```bash
-# 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\"}")
-
-# Return results (Main Chat receives automatically in Task Mode)
-echo "{\"passed\": $PASS, \"failed\": $FAIL, \"pass_rate\": $RATE}"
-```
+2. **Parse Results**: Use test result parser skill to extract metrics
+3. **Report Metrics**: Pass rate, coverage, bottlenecks, expected improvement
 
 **Validation Examples:**
 - ❌ OLD: "Confidence: 0.86 - analysis is thorough"
@@ -255,24 +225,11 @@ echo "{\"passed\": $PASS, \"failed\": $FAIL, \"pass_rate\": $RATE}"
 
 Complete your work and provide test-based validation:
 
-1. **Execute Tests**: Run all performance analysis test suites from success criteria
-
-```bash
-# 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\"}")
-
-# Return results (Main Chat receives automatically in Task Mode)
-echo "{\"passed\": $PASS, \"failed\": $FAIL, \"pass_rate\": $RATE}"
-```
-
+1. **Execute Tests**: Run all performance analysis test suites from success criteria using skill: `./.claude/skills/cfn-agent-output-processing/SKILL.md`
 2. **Validate Results**:
    - Coverage: ≥80%
    - Bottlenecks identified: N
    - Expected improvement: X%
-
 3. **Store Results**: Use test-results key (not confidence key)
 4. **Signal Completion**: Push to completion queue
 
@@ -289,4 +246,4 @@ Performance Analysis Test Summary:
 - Gate Status: PASS (≥95% in 1/3 suites, actionable recommendations provided)
 ```
 
-**Note:** Coordination handled automatically by the system.
+**Note:** Coordination handled automatically by the system. Post-edit validation uses hook: `./.claude/hooks/cfn-invoke-post-edit.sh`

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

@@ -21,77 +21,45 @@ validation_hooks:
 
 ## Success Criteria Awareness (REQUIRED - Phase 2 TDD)
 
+**Reference Skills:**
+- Success Criteria Reader: `./.claude/skills/json-validation/validate-success-criteria.sh`
+- TDD Protocol: `./.claude/skills/cfn-test-execution/SKILL.md`
+- Test Result Parser: `./.claude/skills/cfn-agent-output-processing/SKILL.md`
+
 ### 1. Read Success Criteria
-Before starting work, read test requirements from environment:
-```bash
-if [[ -n "${AGENT_SUCCESS_CRITERIA:-}" ]]; then
-    CRITERIA=$(echo "$AGENT_SUCCESS_CRITERIA" | jq -r '.')
-    TEST_SUITES=$(echo "$CRITERIA" | jq -r '.test_suites[]')
-    echo "📋 Success Criteria Loaded:"
-    echo "$TEST_SUITES" | jq -r '.name'
-fi
-```
+Before starting work, read test requirements from environment using the success criteria reader skill.
 
 ### 2. TDD Protocol (MANDATORY)
 
-**Write Tests First (15-20 min):**
+Follow the standardized TDD protocol:
+- Write tests first (15-20 min)
 - Extract test requirements from success criteria
 - Write failing tests for each benchmark requirement
 - Ensure test coverage ≥80%
-
-**Implement (30-40 min):**
-- Write minimum code to pass tests
-- Run tests continuously (`npm test --watch` or framework equivalent)
+- Implement minimum code to pass tests
+- Run tests continuously
 - Refactor for quality
-
-**Validate (5 min):**
-- Run full test suite: `npm test` (or framework command from criteria)
-- Verify pass rate meets threshold (Standard: ≥95%)
-- Check coverage: `npm run coverage`
+- Verify pass rate ≥95% (Standard mode)
 
 ### 3. Report Test Results (NOT Confidence)
 
-**Old (Deprecated):** Not used
-
-**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\"}")
-
-# Return results (Main Chat receives automatically in Task Mode)
-echo "{\"passed\": $PASS, \"failed\": $FAIL, \"pass_rate\": $RATE}"
-```
-
-## 🚨 Mandatory Post-Edit Validation
+Use the test result parser skill to extract metrics from test output:
+- Parse passing/failing test counts
+- Calculate pass rate percentage
+- Extract coverage metrics
+- Format structured results
 
-Refer to [.claude/templates/post-edit-validation.md](../templates/post-edit-validation.md)
+## Mandatory Post-Edit Validation
 
-```bash
-/hooks post-edit [FILE_PATH] --memory-key "performance-benchmarker/[TASK_ID]"
-```
+Run hook after edits: `./.claude/hooks/cfn-invoke-post-edit.sh` with memory key.
 
 ## Test-Driven Validation (Replaces Confidence Reporting)
 
 DO NOT report subjective confidence scores. Instead:
 
 1. **Execute Tests**: Run test suite defined in success criteria
-
-```bash
-# 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\"}")
-
-# Return results (Main Chat receives automatically in Task Mode)
-echo "{\"passed\": $PASS, \"failed\": $FAIL, \"pass_rate\": $RATE}"
-```
+2. **Parse Results**: Use test result parser skill to extract metrics
+3. **Report Metrics**: Pass rate, coverage, performance baseline
 
 **Validation Examples:**
 - ❌ OLD: "Confidence: 0.88 - benchmarks look good"
@@ -101,23 +69,10 @@ echo "{\"passed\": $PASS, \"failed\": $FAIL, \"pass_rate\": $RATE}"
 
 Complete your work and provide test-based validation:
 
-1. **Execute Tests**: Run all benchmark test suites from success criteria
-
-```bash
-# 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\"}")
-
-# Return results (Main Chat receives automatically in Task Mode)
-echo "{\"passed\": $PASS, \"failed\": $FAIL, \"pass_rate\": $RATE}"
-```
-
+1. **Execute Tests**: Run all benchmark test suites from success criteria using skill: `./.claude/skills/cfn-agent-output-processing/SKILL.md`
 2. **Validate Results**:
    - Coverage: ≥80%
    - Performance baseline established: Yes/No
-
 3. **Store Results**: Use test-results key (not confidence key)
 4. **Signal Completion**: Push to completion queue
 
@@ -133,7 +88,7 @@ Benchmark Test Execution Summary:
 - Gate Status: PASS (≥95% in 1/3 suites, latency anomalies noted)
 ```
 
-**Note:** Coordination handled automatically by the system.
+**Note:** Coordination handled automatically by the system. Post-edit validation uses hook: `./.claude/hooks/cfn-invoke-post-edit.sh`
 
 ## Team Dynamics