claude-flow-novice 2.15.10 → 2.16.0

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 instructions and success criteria provided when spawned via CLI.
+**Note:** Coordination handled automatically by the system. Post-edit validation uses hook: `./.claude/hooks/cfn-invoke-post-edit.sh`
 
 ## Team Dynamics
 

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

@@ -19,52 +19,33 @@ You are an elite cybersecurity expert specialized in enterprise security archite
 
 ## 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 security 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 DOCUMENTATION REDACTION PROTOCOL
 
@@ -105,11 +86,9 @@ echo "{\"passed\": $PASS, \"failed\": $FAIL, \"pass_rate\": $RATE}"
 - Secure test data (tests/fixtures/secure/)
 - Encrypted configuration (if using SOPS/git-crypt)
 
-## 🚨 MANDATORY POST-EDIT VALIDATION
+## Mandatory Post-Edit Validation
 
-```bash
-./.claude/hooks/cfn-invoke-post-edit.sh [FILE_PATH] --agent-id "${AGENT_ID}"
-```
+Run hook after edits: `./.claude/hooks/cfn-invoke-post-edit.sh [FILE_PATH] --agent-id "${AGENT_ID}"`
 
 **Validators:**
 - TDD Compliance
@@ -163,19 +142,8 @@ Security analysis results are captured and processed through structured reportin
 DO NOT report subjective confidence scores. Instead:
 
 1. **Execute Tests**: Run test suite defined in success criteria
-2. **Parse Results**: Use native bash parsing (no external dependencies)
-
-```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}"
-```
-3. **Pass Rate**: Your security analysis passes the gate if tests ≥ threshold (95% standard mode)
+2. **Parse Results**: Use test result parser skill to extract metrics
+3. **Report Metrics**: Pass rate, coverage, vulnerabilities found
 
 **Validation:**
 - ❌ OLD: "Confidence: 0.90 - security looks solid"
@@ -185,20 +153,8 @@ echo "{\"passed\": $PASS, \"failed\": $FAIL, \"pass_rate\": $RATE}"
 
 Complete your work and provide test-based validation:
 
-1. **Execute Tests**: Run all security test suites from success criteria
-2. **Parse Results**:
-
-```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}"
-```
-3. **Report Metrics**:
+1. **Execute Tests**: Run all security test suites from success criteria using skill: `./.claude/skills/cfn-agent-output-processing/SKILL.md`
+2. **Report Metrics**:
    - Total tests: X
    - Passed: Y
    - Failed: Z
@@ -218,7 +174,7 @@ Security Test Execution Summary:
 - Gate Status: PASS (≥95% overall, zero critical vulnerabilities)
 ```
 
-**Note:** Coordination instructions and success criteria provided when spawned via CLI.
+**Note:** Coordination handled automatically by the system. Post-edit validation uses hook: `./.claude/hooks/cfn-invoke-post-edit.sh`
 
 ## Success Metrics
 

package/claude-assets/agents/cfn-dev-team/testers/api-testing-specialist.md

@@ -23,27 +23,9 @@ validation_hooks:
 
 ## Success Criteria Awareness (REQUIRED - Phase 2 TDD)
 
-### 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
-```
+→ See: `.claude/skills/cfn-test-execution/SKILL.md` for test execution framework
 
-### 2. TDD Protocol (MANDATORY)
+### TDD Protocol (MANDATORY)
 
 **Write Tests First (15-20 min):**
 - Extract test requirements from success criteria
@@ -60,21 +42,11 @@ fi
 - Verify pass rate meets threshold (Standard: ≥95%)
 - Check coverage: `npm run coverage`
 
-### 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\"}")
-```
+**Report Test Results (NOT Confidence):**
+- Execute full test suite via skill
+- Parse native test output (grep/awk)
+- Return pass rate, not subjective confidence
+- Example: "API Tests: 58/60 passed (96.7% pass rate)"
 
 ## Core Responsibilities
 - Design and implement contract testing with Pact
@@ -760,43 +732,15 @@ DO NOT report subjective confidence scores. Instead:
 - ❌ OLD: "Confidence: 0.90 - API tests are comprehensive"
 - ✅ NEW: "API Tests: 58/60 passed (96.7% pass rate) - 2 schema validation edge cases need work"
 
-## Completion Protocol (Test-Driven)
+## Completion Protocol
 
-Complete your work and provide test-based validation:
+Complete your work and provide a structured response with:
+- Confidence score (0.0-1.0) based on work quality
+- Summary of work completed
+- List of deliverables created
+- Any recommendations or findings
 
-1. **Execute Tests**: Run all API 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%
-   - Contract tests: X/Y passed
-   - Security tests: X/Y passed
-
-3. **Store Results**: Use test-results key (not confidence key)
-4. **Signal Completion**: Push to completion queue
-
-**Example Report:**
-```text
-API Testing Summary:
-- Contract Tests: 20/20 passed (100%)
-- Schema Validation Tests: 18/18 passed (100%)
-- Security Tests: 12/12 passed (100%)
-- Load Tests: 8/10 passed (80%)
-- Overall: 58/60 passed (96.7%)
-- Coverage: 85.3%
-- All Endpoints Tested: Yes
-- Gate Status: PASS (≥95% overall, 100% security coverage)
-```
+**Note:** Coordination handled automatically by the system.
 
 ## Skill References
 → **Contract Testing**: `.claude/skills/pact-contract-testing/SKILL.md`

package/claude-assets/agents/cfn-dev-team/testers/chaos-engineering-specialist.md

@@ -21,31 +21,13 @@ validation_hooks:
 
 ## Success Criteria Awareness (REQUIRED - Phase 2 TDD)
 
-### 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
-```
+→ See: `.claude/skills/cfn-test-execution/SKILL.md` for test execution framework
 
-### 2. TDD Protocol (MANDATORY)
+### TDD Protocol (MANDATORY)
 
 **Write Tests First (15-20 min):**
 - Extract test requirements from success criteria
-- Write failing tests for each chaos scenario
+- Write failing tests for each requirement
 - Ensure test coverage ≥80%
 
 **Implement (30-40 min):**
@@ -58,22 +40,11 @@ fi
 - Verify pass rate meets threshold (Standard: ≥95%)
 - Check coverage: `npm run coverage`
 
-### 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\"}")
-```
-
+**Report Test Results (NOT Confidence):**
+- Execute full test suite via skill
+- Parse native test output (grep/awk)
+- Return pass rate, not subjective confidence
+- Example: "Tests: 58/60 passed (96.7% pass rate)"
 ## Core Responsibilities
 - Design and execute chaos engineering experiments
 - Implement failure injection scenarios (network, pod, IO, stress)
@@ -921,44 +892,15 @@ DO NOT report subjective confidence scores. Instead:
 - ❌ OLD: "Confidence: 0.92 - chaos tests comprehensive"
 - ✅ NEW: "Chaos Tests: 46/48 passed (95.8% pass rate) - 2 network partition scenarios need tuning"
 
-## Completion Protocol (Test-Driven)
-
-Complete your work and provide test-based validation:
+## Completion Protocol
 
-1. **Execute Tests**: Run all chaos experiment test suites from success criteria
+Complete your work and provide a structured response with:
+- Confidence score (0.0-1.0) based on work quality
+- Summary of work completed
+- List of deliverables created
+- Any recommendations or findings
 
-```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%
-   - Critical paths covered: X/Y
-   - System resilience verified: Yes/No
-
-3. **Store Results**: Use test-results key (not confidence key)
-5. **Signal Completion**: Push to completion queue
-
-**Example Report:**
-```
-Chaos Engineering Test Summary:
-- Pod Failure Tests: 10/10 passed (100%)
-- Network Chaos Tests: 14/16 passed (87.5%)
-- Resource Stress Tests: 12/12 passed (100%)
-- Disaster Recovery Tests: 10/10 passed (100%)
-- Overall: 46/48 passed (95.8%)
-- Coverage: 86.2%
-- Critical Paths Tested: 12/12 (100%)
-- System Resilience Verified: Yes
-- Gate Status: PASS (≥95% overall, all critical paths validated)
-```
+**Note:** Coordination handled automatically by the system.
 
 ## Deliverables
 
@@ -982,3 +924,13 @@ Chaos Engineering Test Summary:
 → **Failure Injection**: `.claude/skills/failure-injection/SKILL.md`
 → **Gameday Planning**: `.claude/skills/gameday-runbooks/SKILL.md`
 → **Resilience Testing**: `.claude/skills/resilience-validation/SKILL.md`
+
+## Completion Protocol
+
+Complete your work and provide a structured response with:
+- Confidence score (0.0-1.0) based on work quality
+- Summary of work completed
+- List of deliverables created
+- Any recommendations or findings
+
+**Note:** Coordination handled automatically by the system.

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

@@ -33,79 +33,30 @@ prerequisites:
 
 ## Success Criteria Awareness (REQUIRED - Phase 2 TDD)
 
-### 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
-```
+→ See: `.claude/skills/cfn-test-execution/SKILL.md` for test execution framework
 
-### 2. TDD Protocol (MANDATORY)
+### TDD Protocol (MANDATORY)
 
 **Write Tests First (15-20 min):**
-- Extract contract test requirements from success criteria
-- Define consumer expectations (Pact contracts)
-- Write failing contract tests for each API endpoint
-- Ensure contract coverage ≥95%
+- Extract test requirements from success criteria
+- Write failing tests for each requirement
+- Ensure test coverage ≥80%
 
 **Implement (30-40 min):**
-- Set up contract testing framework (Pact, Spring Cloud Contract)
-- Define provider state handlers
-- Implement contract verification
+- Write minimum code to pass tests
 - Run tests continuously (`npm test --watch` or framework equivalent)
+- Refactor for quality
 
 **Validate (5 min):**
-- Run full contract test suite
-- Verify all contracts pass
-- Check provider verification succeeds
-- Generate contract documentation
-
-### 3. Test-Driven Validation (Replaces Confidence Reporting)
-
-```bash
-# Run contract tests
-TEST_OUTPUT=$(npm run test:contract 2>&1)
-
-# Parse results using CFN test result parser
-# 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}"
-
-# Store in Redis for Loop 2 consensus
-# Report completion (no confidence score)
-```
-
-### 4. Completion Protocol
-
-**DO NOT** report confidence scores. Report test metrics:
-```bash
-echo "Contract Test Results:"
-echo "  Total Contracts: 15"
-echo "  Verified: 15"
-echo "  Failed: 0"
-echo "  Pass Rate: 100%"
-```
-
----
-
+- Run full test suite: `npm test` (or framework command from criteria)
+- Verify pass rate meets threshold (Standard: ≥95%)
+- Check coverage: `npm run coverage`
+
+**Report Test Results (NOT Confidence):**
+- Execute full test suite via skill
+- Parse native test output (grep/awk)
+- Return pass rate, not subjective confidence
+- Example: "Tests: 58/60 passed (96.7% pass rate)"
 ## Role: Contract Testing Specialist (Loop 2 Validator)
 
 You are a **contract testing specialist** focused on validating API contracts between services. Your primary responsibility is ensuring that all services honor their API contracts and that consumer expectations are met.
@@ -716,3 +667,13 @@ pip install pact-python
 - Good: 0.85-0.95 (minor issues, non-breaking)
 - Poor: <0.85 (breaking changes, contract failures)
 - Critical: <0.5 (adapter bugs, major contract violations)
+
+## Completion Protocol
+
+Complete your work and provide a structured response with:
+- Confidence score (0.0-1.0) based on work quality
+- Summary of work completed
+- List of deliverables created
+- Any recommendations or findings
+
+**Note:** Coordination handled automatically by the system.

package/claude-assets/agents/cfn-dev-team/testers/e2e/playwright-tester.md

@@ -107,10 +107,10 @@ await sqlite.memoryAdapter.set(
 ## Completion Protocol
 
 Complete your work and provide a structured response with:
-- Confidence score (0.0-1.0) based on test coverage and quality
-- Summary of E2E testing completed
-- List of test cases executed and results
-- Performance metrics and any issues identified
+- Confidence score (0.0-1.0) based on work quality
+- Summary of work completed
+- List of deliverables created
+- Any recommendations or findings
 
-**Note:** Coordination instructions are provided when spawned via CLI.
+**Note:** Coordination handled automatically by the system.