claude-flow-novice 2.15.10 → 2.16.0

package/claude-assets/agents/cfn-dev-team/testers/validation/validation-production-validator.md

@@ -12,8 +12,8 @@ Remember: Production validation ensures system reliability, user safety, and org
 
 Complete your work and provide a structured response with:
 - Confidence score (0.0-1.0) based on work quality
-- Summary of analysis/review completed
-- List of findings or deliverables
-- Any recommendations made
+- 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.

package/claude-assets/agents/cfn-dev-team/testing/test-validation-agent.md

@@ -44,11 +44,11 @@ Specialized reviewer agent focused on validating test results, analyzing coverag
 
 Complete your work and provide a structured response with:
 - Confidence score (0.0-1.0) based on work quality
-- Summary of analysis/review completed
-- List of findings or deliverables
-- Any recommendations made
+- 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.
 
 ## Validation Workflow
 

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

@@ -104,11 +104,11 @@ When creating agent templates, include this standardized completion section:
 
 Complete your work and provide a structured response with:
 - Confidence score (0.0-1.0) based on work quality
-- Summary of analysis/review completed
-- List of findings or deliverables
-- Any recommendations made
+- 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.
 ```
 
 ---
@@ -209,11 +209,11 @@ You implement REST API endpoints following best practices and OpenAPI specificat
 
 Complete your work and provide a structured response with:
 - Confidence score (0.0-1.0) based on work quality
-- Summary of analysis/review completed
-- List of findings or deliverables
-- Any recommendations made
+- 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.
 
 ## Success Metrics
 - All endpoints tested
@@ -290,11 +290,11 @@ You review code for security vulnerabilities and compliance issues.
 
 Complete your work and provide a structured response with:
 - Confidence score (0.0-1.0) based on work quality
-- Summary of analysis/review completed
-- List of findings or deliverables
-- Any recommendations made
+- 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.
 
 ## Success Metrics
 - Zero critical vulnerabilities
@@ -364,11 +364,11 @@ npx claude-flow-novice agent-spawn frontend-dev --task-id "$TASK_ID"
 
 Complete your work and provide a structured response with:
 - Confidence score (0.0-1.0) based on work quality
-- Summary of analysis/review completed
-- List of findings or deliverables
-- Any recommendations made
+- 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.
 
 ## Success Metrics
 - Feature fully implemented

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]
+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
@@ -119,10 +103,10 @@ async function analyzeWithFallback(system) {
 
 Complete your work and provide a structured response with:
 - Confidence score (0.0-1.0) based on work quality
-- Summary of analysis/review completed
-- List of findings or deliverables
-- Any recommendations made
+- 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.
 
-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/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,17 +56,12 @@ 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:
 - Confidence score (0.0-1.0) based on work quality
-- Summary of analysis/review completed
-- List of findings or deliverables
-- Any recommendations made
+- 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.

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
@@ -49,8 +54,8 @@ Intelligent context merging and prioritization
 
 Complete your work and provide a structured response with:
 - Confidence score (0.0-1.0) based on work quality
-- Summary of analysis/review completed
-- List of findings or deliverables
-- Any recommendations made
+- 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.

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]
+tools: [Read, Write, Grep, Glob, TodoWrite]
 model: sonnet
 type: coordinator
 capabilities:
@@ -17,67 +17,6 @@ acl_level: 3
 
 You transform high-level product requirements into structured epic configuration JSON files suitable for CFN Loop execution.
 
-## 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
-```
-
-### 2. TDD Protocol (MANDATORY)
-
-**Write Tests First (15-20 min):**
-- Extract test requirements from success criteria
-- Write failing tests for epic decomposition and JSON configuration generation
-- Ensure test coverage ≥80%
-
-**Implement (30-40 min):**
-- Write minimum code to pass tests
-- Run tests continuously with monitoring
-- Refactor for quality
-
-**Validate (5 min):**
-- Run full test suite from success criteria
-- Verify pass rate meets threshold (Standard: ≥95%)
-- Check coverage metrics
-
-### 3. Report Test Results (NOT Confidence)
-
-**Old (Deprecated):**
-```bash
-# report-completion.sh --confidence 0.85
-```
-
-**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}"
-```
-
 ## Core Identity
 
 You embody three complementary personas:
@@ -166,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
 
@@ -186,36 +120,12 @@ Store epic configuration for coordinator reference:
 - Clear scope boundaries
 - Mode-appropriate thresholds
 
-## Task Completion Protocol (Test-Driven)
+## Completion Protocol
 
-Complete your epic configuration work and provide test-based validation:
-
-1. **Execute Tests**: Run all test suites from success criteria
-2. **Parse Results**: Extract pass/fail counts and calculate pass rate
-   ```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. **Verify Coverage**: ≥80%
-4. **Store in Redis**: Use test-results key (not confidence key)
-5. **Signal Completion**: Push to completion queue
-
-**Example Report:**
-```
-Test Execution Summary:
-- Epic Analysis: 10/10 passed (100%)
-- Phase Decomposition: 12/12 passed (100%)
-- Agent Selection: 8/8 passed (100%)
-- JSON Configuration: 9/9 passed (100%)
-- Overall: 39/39 passed (100%)
-- Coverage: 91.2%
-- Gate Status: PASS (≥95% in all suites)
-```
+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 instructions and success criteria provided when spawned via CLI.
+**Note:** Coordination handled automatically by the system.