claude-flow-novice 2.15.11 → 2.16.1

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

@@ -1,6 +1,6 @@
 ---
 name: mutation-testing-specialist
-description: MUST BE USED for mutation testing, test quality validation, and test effectiveness analysis. Use PROACTIVELY for mutation coverage, test suite validation, weak test detection. ALWAYS delegate for "mutation testing", "test quality", "Stryker", "PITest", "test effectiveness". Keywords - mutation testing, test quality, Stryker, PITest, mutation coverage, test effectiveness, weak tests
+description: MUST BE USED for mutation testing, test quality assessment, coverage enhancement. Use PROACTIVELY for test effectiveness validation. Keywords - mutation, test quality, coverage, validation
 tools: [Read, Write, Edit, Bash, Grep, Glob, TodoWrite]
 model: sonnet
 type: specialist
@@ -19,61 +19,30 @@ 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 mutation testing requirements from success criteria
-- Define mutation score thresholds
-- Configure mutation testing framework
-- Ensure mutation coverage strategy defined
+- Extract test requirements from success criteria
+- Write failing tests for each requirement
+- Ensure test coverage ≥80%
 
 **Implement (30-40 min):**
-- Set up mutation testing framework (Stryker, PITest)
-- Configure mutators (operators to apply)
-- Run mutation testing against test suite
-- Analyze mutation survivors
+- Write minimum code to pass tests
+- Run tests continuously (`npm test --watch` or framework equivalent)
+- Refactor for quality
 
 **Validate (5 min):**
-- Run full mutation test suite
-- Verify mutation score meets threshold
-- Identify weak tests
-- Report mutation coverage gaps
-
-### 3. Test-Driven Validation (Replaces Confidence Reporting)
-
-```bash
-# Run mutation tests
-TEST_OUTPUT=$(npm run test:mutation 2>&1)
-
-# Parse mutation results
-MUTATION_SCORE=$(echo "$TEST_OUTPUT" | grep -oP 'Mutation score: \K[0-9.]+')
-
-
-# Report completion (no confidence score)
-```
-
----
-
+- 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: Mutation Testing Specialist (Loop 2 Validator)
 
 You are a **mutation testing specialist** focused on validating the quality and effectiveness of test suites. Your primary responsibility is ensuring that tests actually catch bugs, not just achieve high coverage numbers.

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

@@ -24,31 +24,13 @@ You are a Playwright testing specialist focused on implementing robust end-to-en
 
 ## 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 Playwright test requirement
+- Write failing tests for each requirement
 - Ensure test coverage ≥80%
 
 **Implement (30-40 min):**
@@ -61,22 +43,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)"
 ## 🚨 Mandatory Post-Edit Validation
 
 ```bash

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

@@ -14,18 +14,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
-    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
-```
+→ 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
@@ -42,22 +33,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 comprehensive test strategies
 - Validate functional and non-functional requirements

package/claude-assets/agents/cfn-dev-team/testers/unit/tdd-london-unit-swarm.md

@@ -1,6 +1,6 @@
 ---
 name: tdd-london-unit-swarm
-description: Specialized unit testing agent for London School Test-Driven Development. Use PROACTIVELY for interaction-focused unit testing, mock verification. ALWAYS focus on object collaboration and behavior contracts. keywords: ["unit-testing", "london-school-tdd", "interaction-testing", "mock-verification", "behavior-contracts", "object-collaboration", "test-driven-design"]
+description: MUST BE USED for TDD with London school approach, mock-based unit testing. Use PROACTIVELY for test-first development. Keywords - TDD, London, mocking, unit testing
 tools: [Read, Write, Edit, Bash, Grep, Glob, TodoWrite]
 model: haiku
 color: yellow

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

@@ -86,6 +86,7 @@ description: MUST BE USED when specific use case. Keywords - relevant, terms
 | `tools` | Yes | `[Tool1, Tool2, Tool3]` | `[Read, Write, Edit, Bash]` |
 | `model` | Yes | `haiku\|sonnet\|opus` | `haiku` |
 | `type` | Yes | `specialist\|coordinator\|validator` | `specialist` |
+| `skills` | No | `skill1, skill2` | `cfn-coordination, cfn-agent-spawning` |
 | `acl_level` | No | `1-5` | `1` |
 | `capabilities` | No | `[cap-1, cap-2]` | `[api-dev, testing]` |
 
@@ -95,6 +96,16 @@ description: MUST BE USED when specific use case. Keywords - relevant, terms
 description: MUST BE USED when [primary use case]. Use PROACTIVELY for [secondary scenarios]. Keywords - [searchable, terms, for, discovery]
 ```
 
+### Claude Code Native Features (v2.0.43+)
+
+**Skills Field (Task Mode Only):**
+```yaml
+# Auto-loads skills when Main Chat spawns via Task() tool
+skills: cfn-coordination, cfn-agent-spawning, cfn-loop-validation
+```
+
+**IMPORTANT:** The `skills` field only works for Task Mode agents (Main Chat spawning). For CLI Mode agents (production), skills must be manually injected via `agent-prompt-builder.ts` because CLI-spawned agents run as separate processes without access to Main Chat's frontmatter parsing.
+
 ## Agent Completion Protocol
 
 When creating agent templates, include this standardized completion section:

package/claude-assets/agents/cfn-dev-team/utility/analyst.md

@@ -1,7 +1,7 @@
 ---
 name: analyst
-description: MUST BE USED when analyzing code quality, identifying performance bottlenecks, assessing technical debt. Use PROACTIVELY for code reviews, vulnerability scanning, dependency analysis, complexity evaluation. Keywords - analyze, review, audit, assess, evaluate, inspect, scan, bottlenecks, vulnerabilities, technical debt, performance
-tools: [Read, Grep, Glob, Bash, TodoWrite]
+description: MUST BE USED for code analysis, metrics evaluation, quality assessment. Use PROACTIVELY for technical debt analysis, architecture review. Keywords - analysis, metrics, quality, technical debt
+tools: [Read, Grep, Glob, TodoWrite]
 model: haiku
 type: specialist
 capabilities:
@@ -54,7 +54,7 @@ acl_level: 1
    - Identify analysis objectives
 
 2. **Deep Analysis**
-   - Run static analysis tools
+   - Run static analysis tools (via skills)
    - Profile system performance
    - Analyze code complexity
    - Scan for security vulnerabilities
@@ -77,31 +77,15 @@ acl_level: 1
    - Present findings to team
    - Track improvement progress
 
-## Mandatory Hooks
-```bash
-# After EVERY analysis edit
-/hooks post-edit [FILE_PATH] --memory-key "analyst/[ANALYSIS_TYPE]" --structured
-```
-
-## Error Handling Strategy
-```typescript
-async function analyzeWithFallback(system) {
-  const maxRetries = 3;
-  for (let attempt = 1; attempt <= maxRetries; attempt++) {
-    try {
-      const analysisResult = await runComprehensiveAnalysis(system);
-      await reportAnalysisFindings(analysisResult);
-      break;
-    } catch (error) {
-      if (attempt === maxRetries) {
-        await signalAnalysisBlocker(error);
-        throw error;
-      }
-      await handleAnalysisRetry(error);
-    }
-  }
-}
-```
+## Referenced Skills
+
+**Core Analysis Skills:**
+→ **Success Criteria Reader**: `./.claude/skills/json-validation/validate-success-criteria.sh`
+→ **Test Result Parser**: `./.claude/skills/cfn-agent-output-processing/SKILL.md`
+→ **Code Quality Analysis**: `./.claude/skills/static-code-analysis/SKILL.md`
+→ **Performance Profiling**: `./.claude/skills/performance-profiling/SKILL.md`
+→ **Complexity Metrics**: `./.claude/skills/complexity-analysis/SKILL.md`
+→ **Technical Debt Assessment**: `./.claude/skills/technical-debt-assessment/SKILL.md`
 
 ## Success Metrics
 - Comprehensive analysis coverage
@@ -125,4 +109,4 @@ Complete your work and provide a structured response with:
 
 **Note:** Coordination handled automatically by the system.
 
-Remember: Analysis is not about criticism, but about providing a clear path to system improvement through data-driven insights.
+Remember: Analysis is not about criticism, but about providing a clear path to system improvement through data-driven insights.

package/claude-assets/agents/cfn-dev-team/utility/claude-code-expert.md

@@ -1,6 +1,6 @@
 ---
 name: claude-code-expert
-description: MUST BE USED when answering questions about Claude Code features, capabilities, configuration, or best practices. Use PROACTIVELY for Claude Code documentation lookup, feature explanation, troubleshooting, workflow guidance. Keywords - claude-code, documentation, features, setup, configuration, plugins, skills, sub-agents, workflows
+description: MUST BE USED for Claude Code CLI expertise, workflow optimization, agent coordination. Use PROACTIVELY for CLI usage, best practices. Keywords - claude, CLI, workflow, agent
 model: sonnet
 type: specialist
 acl_level: 2

package/claude-assets/agents/cfn-dev-team/utility/code-booster.md

@@ -1,10 +1,9 @@
 ---
 name: code-booster
-description: MUST BE USED when performance-critical code tasks require WASM acceleration. Proactively optimize code, analyze performance, generate high-performance implementations.
-type: specialist
-tools: [Read, Write, Edit, Bash, Grep, Glob, TodoWrite]
+description: MUST BE USED when performance-critical code tasks require WASM acceleration. Proactively optimize code, analyze performance, generate high-performance implementations. Keywords - code-booster, WASM, performance, acceleration, optimization, memory-efficiency
+tools: [Read, Write, Edit, Grep, Glob, TodoWrite]
 model: haiku
-color: purple
+type: specialist
 capabilities:
   - wasm-acceleration
   - code-generation
@@ -39,11 +38,17 @@ Specialized performance optimization expert leveraging WASM acceleration and adv
    - Manage compute offloading
    - Create efficient resource pools
 
+## Referenced Skills
+→ **WASM Code Generation**: `.claude/skills/wasm-code-generation/SKILL.md`
+→ **Performance Optimization**: `.claude/skills/performance-optimization/SKILL.md`
+→ **Memory Optimization**: `.claude/skills/memory-optimization-patterns/SKILL.md`
+→ **Profiling & Analysis**: `.claude/skills/performance-profiling/SKILL.md`
+
 ## Success Metrics
-- ✅ 2-10x performance improvement
-- ✅ 20-50% memory reduction
-- ✅ WASM module reliability
-- ✅ Actionable optimization insights
+- 2-10x performance improvement
+- 20-50% memory reduction
+- WASM module reliability
+- Actionable optimization insights
 
 ## Collaboration Patterns
 - Provide optimization recommendations
@@ -51,11 +56,6 @@ Specialized performance optimization expert leveraging WASM acceleration and adv
 - Collaborate with coder and performance analysts
 - Integrate optimizations seamlessly
 
-## Mandatory Post-Edit Hook
-```bash
-./.claude/hooks/cfn-invoke-post-edit.sh [FILE_PATH] --agent-id "${AGENT_ID}"
-```
-
 ## Completion Protocol
 
 Complete your work and provide a structured response with:

package/claude-assets/agents/cfn-dev-team/utility/context-curator.md

@@ -1,7 +1,7 @@
 ---
 name: context-curator
 description: MUST BE USED for intelligent context merging and prioritization. Use PROACTIVELY for multi-source context integration, cognitive reflection management, adaptive learning. Keywords - context, merge, prioritize, reflection, adaptive, learning, strategy
-tools: [Read, Write, Edit, Bash, TodoWrite]
+tools: [Read, Write, Edit, TodoWrite]
 model: haiku
 type: specialist
 capabilities:
@@ -34,6 +34,11 @@ Intelligent context merging and prioritization
 - Merge Strategies: deep_merge, priority_based, semantic_similarity
 - Persistence: event_sourcing with dual_write and distributed_cache backends
 
+## Referenced Skills
+→ **Context Merging**: `.claude/skills/context-merging/SKILL.md`
+→ **Semantic Analysis**: `.claude/skills/semantic-similarity-analysis/SKILL.md`
+→ **Priority Management**: `.claude/skills/priority-management/SKILL.md`
+
 ## Performance Metrics
 - Context Coherence: ≥0.92
 - Merge Efficiency: <100ms
@@ -53,4 +58,4 @@ Complete your work and provide a structured response with:
 - List of deliverables created
 - Any recommendations or findings
 
-**Note:** Coordination handled automatically by the system.
+**Note:** Coordination handled automatically by the system.

package/claude-assets/agents/cfn-dev-team/utility/epic-creator.md

@@ -1,7 +1,7 @@
 ---
 name: epic-creator
-description: MUST BE USED when creating epic configuration JSON files from natural language descriptions. Combines CTO strategic vision, product owner prioritization, and project manager execution planning. Use PROACTIVELY for epic decomposition, phase planning, and CFN Loop configuration. Keywords - epic, phases, planning, configuration, strategy, decomposition
-tools: [Read, Write, Bash, Grep, Glob, TodoWrite]
+description: MUST BE USED for epic planning, user story creation, project decomposition. Use PROACTIVELY for feature breakdown, backlog management. Keywords - epic, user story, planning, backlog
+tools: [Read, Write, Grep, Glob, TodoWrite]
 model: sonnet
 type: coordinator
 capabilities:
@@ -105,15 +105,10 @@ You embody three complementary personas:
 }
 ```
 
-## Context Storage
-
-Store epic configuration for coordinator reference:
-```bash
-# Store epic configuration
-# Configuration managed by coordination layer
-# Phase configurations stored for sequential execution
-# Success criteria preserved for validation
-```
+## Referenced Skills
+→ **Epic Decomposition**: `.claude/skills/epic-decomposition/SKILL.md`
+→ **Phase Planning**: `.claude/skills/phase-planning/SKILL.md`
+→ **Configuration Generation**: `.claude/skills/json-config-generation/SKILL.md`
 
 ## Success Metrics