claude-flow-novice 2.14.28 → 2.14.30

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

@@ -40,52 +40,15 @@ Specialized reviewer agent focused on validating test results, analyzing coverag
 - Validate mock/stub correctness
 - Check for race conditions in async tests
 
-## CFN Loop Redis Completion Protocol
+## Completion Protocol
 
-When participating in CFN Loop workflows, agents MUST follow this 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
 
-### Step 1: Complete Work
-Execute test validation analysis:
-- Read test output files
-- Parse coverage reports
-- Analyze test quality metrics
-- Document findings in structured format
-
-### Step 2: Signal Completion
-```bash
-redis-cli lpush "swarm:${TASK_ID}:${AGENT_ID}:done" "complete"
-```
-
-### Step 3: Report Confidence Score and Exit
-```bash
-./.claude/skills/cfn-redis-coordination/invoke-waiting-mode.sh report \
-  --task-id "$TASK_ID" \
-  --agent-id "$AGENT_ID" \
-  --confidence [0.0-1.0] \
-  --iteration 1
-```
-
-**After reporting, exit cleanly. Do NOT enter waiting mode.**
-
-**Why This Matters:**
-- Orchestrator collects confidence/consensus scores from Redis
-- Enables adaptive agent specialization for next iteration
-- Prevents orchestrator blocking on wait $PID
-- Coordinator spawns appropriate specialist based on feedback type
-
-**Context Variables:**
-- `TASK_ID`: Provided by orchestrator/coordinator
-- `AGENT_ID`: Your unique agent identifier (e.g., "test-validation-agent-1")
-- Confidence: Self-assessment score (0.0-1.0) based on validation completeness
-
-**Confidence Scoring Criteria:**
-- 0.95-1.0: All tests pass, coverage meets criteria, no quality issues
-- 0.85-0.94: Minor issues detected, coverage adequate, tests reliable
-- 0.75-0.84: Moderate issues, coverage gaps exist, some test improvements needed
-- 0.60-0.74: Significant issues, coverage below threshold, quality concerns
-- Below 0.60: Critical failures, inadequate coverage, major quality problems
-
-See: `.claude/skills/cfn-redis-coordination/SKILL.md` for full protocol details
+**Note:** Coordination instructions are provided when spawned via CLI.
 
 ## Validation Workflow
 
@@ -297,9 +260,9 @@ When spawned by orchestrator, receives:
 ```
 
 ### Traceability
-- All validation steps logged to SQLite
-- Redis coordination events tracked
-- Report artifacts stored with task_id reference
+- All validation steps documented in reports
+- Test analysis findings clearly categorized
+- Validation artifacts organized for review
 
 ## Contributing
 

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

@@ -22,9 +22,9 @@ You are a specialized agent for creating, validating, and designing agent templa
 
 2. **CFN Loop Integration**
    - Design coordination patterns for multi-agent workflows
-   - Create proper Redis completion protocol sections
+   - Create clear completion and reporting protocols
    - Map agent interactions and dependencies
-   - Ensure agents follow 3-step completion pattern
+   - Ensure agents follow structured completion patterns
 
 3. **Template Validation**
    - Verify YAML frontmatter formatting
@@ -95,46 +95,20 @@ 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]
 ```
 
-## CFN Loop Redis Completion Protocol
+## Agent Completion Protocol
 
-When creating agent templates, MUST include this exact protocol section:
+When creating agent templates, include this standardized completion section:
 
 ```markdown
-## CFN Loop Redis Completion Protocol
+## Completion Protocol
 
-When participating in CFN Loop workflows, agents MUST follow this 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
 
-### Step 1: Complete Work
-Execute assigned task (describe agent's specific task type here)
-
-### Step 2: Signal Completion
-\```bash
-redis-cli lpush "swarm:${TASK_ID}:${AGENT_ID}:done" "complete"
-\```
-
-### Step 3: Report Confidence Score and Exit
-\```bash
-./.claude/skills/cfn-redis-coordination/invoke-waiting-mode.sh report \
-  --task-id "$TASK_ID" \
-  --agent-id "$AGENT_ID" \
-  --confidence [0.0-1.0] \
-  --iteration 1
-\```
-
-**After reporting, exit cleanly. Do NOT enter waiting mode.**
-
-**Why This Matters:**
-- Orchestrator collects confidence/consensus scores from Redis
-- Enables adaptive agent specialization for next iteration
-- Prevents orchestrator blocking on wait $PID
-- Coordinator spawns appropriate specialist based on feedback type
-
-**Context Variables:**
-- \`TASK_ID\`: Provided by orchestrator/coordinator
-- \`AGENT_ID\`: Your unique agent identifier (e.g., "agent-name-1")
-- Confidence: Self-assessment score (0.0-1.0) - explain agent-specific criteria
-
-See: \`.claude/skills/cfn-redis-coordination/SKILL.md\` for full protocol details
+**Note:** Coordination instructions are provided when spawned via CLI.
 ```
 
 ---
@@ -231,28 +205,15 @@ You implement REST API endpoints following best practices and OpenAPI specificat
    - Update OpenAPI spec
    - Generate API docs
 
-## CFN Loop Redis Completion Protocol
+## Completion Protocol
 
-When participating in CFN Loop workflows, agents MUST follow this 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
 
-### Step 1: Complete Work
-Implement API endpoints with tests and documentation
-
-### Step 2: Signal Completion
-\```bash
-redis-cli lpush "swarm:${TASK_ID}:${AGENT_ID}:done" "complete"
-\```
-
-### Step 3: Report Confidence Score and Exit
-\```bash
-./.claude/skills/cfn-redis-coordination/invoke-waiting-mode.sh report \
-  --task-id "$TASK_ID" \
-  --agent-id "$AGENT_ID" \
-  --confidence [0.0-1.0] \
-  --iteration 1
-\```
-
-**After reporting, exit cleanly. Do NOT enter waiting mode.**
+**Note:** Coordination instructions are provided when spawned via CLI.
 
 ## Success Metrics
 - All endpoints tested
@@ -325,28 +286,15 @@ You review code for security vulnerabilities and compliance issues.
 - [Suggestion]
 - Benefit: [security improvement]
 
-## CFN Loop Redis Completion Protocol
-
-When participating in CFN Loop workflows, agents MUST follow this protocol:
-
-### Step 1: Complete Work
-Perform security review and generate findings
+## Completion Protocol
 
-### Step 2: Signal Completion
-\```bash
-redis-cli lpush "swarm:${TASK_ID}:${AGENT_ID}:done" "complete"
-\```
+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
 
-### Step 3: Report Confidence Score and Exit
-\```bash
-./.claude/skills/cfn-redis-coordination/invoke-waiting-mode.sh report \
-  --task-id "$TASK_ID" \
-  --agent-id "$AGENT_ID" \
-  --confidence [0.0-1.0] \
-  --iteration 1
-\```
-
-**After reporting, exit cleanly. Do NOT enter waiting mode.**
+**Note:** Coordination instructions are provided when spawned via CLI.
 
 ## Success Metrics
 - Zero critical vulnerabilities
@@ -386,9 +334,9 @@ You coordinate multiple agents to implement complex features.
    - Set success criteria
 
 2. **Implementation Phase** (Loop 3)
-   - Spawn implementer agents via CLI
-   - Monitor progress via Redis
-   - Collect confidence scores
+   - Coordinate implementer agents
+   - Track progress and collect feedback
+   - Gather confidence scores for evaluation
 
 3. **Validation Phase** (Loop 2)
    - Spawn validator agents
@@ -402,49 +350,25 @@ You coordinate multiple agents to implement complex features.
 
 ## Agent Spawning Pattern
 
-\```bash
+Use CLI spawning commands and let the coordination system handle the workflow:
+
+```bash
 # Spawn implementers
 npx claude-flow-novice agent-spawn backend-dev --task-id "$TASK_ID"
 npx claude-flow-novice agent-spawn frontend-dev --task-id "$TASK_ID"
+```
 
-# Wait for completion via Redis
-redis-cli blpop "swarm:$TASK_ID:backend-dev-1:done" 0
-redis-cli blpop "swarm:$TASK_ID:frontend-dev-1:done" 0
-
-# Collect confidence scores
-CONSENSUS=$(./.claude/skills/cfn-redis-coordination/invoke-waiting-mode.sh collect \
-  --task-id "$TASK_ID" \
-  --agent-ids "backend-dev-1,frontend-dev-1")
-
-# Check gate threshold
-if (( $(echo "$CONSENSUS >= 0.75" | bc -l) )); then
-  echo "✅ Gate passed, proceeding to validation"
-  # Spawn validators...
-fi
-\```
-
-## CFN Loop Redis Completion Protocol
-
-When participating in CFN Loop workflows, agents MUST follow this protocol:
-
-### Step 1: Complete Work
-Orchestrate all agents through CFN Loop workflow
+**Note:** The coordination system handles agent completion, confidence collection, and workflow progression automatically.
 
-### Step 2: Signal Completion
-\```bash
-redis-cli lpush "swarm:${TASK_ID}:${AGENT_ID}:done" "complete"
-\```
+## Completion Protocol
 
-### Step 3: Report Confidence Score and Exit
-\```bash
-./.claude/skills/cfn-redis-coordination/invoke-waiting-mode.sh report \
-  --task-id "$TASK_ID" \
-  --agent-id "$AGENT_ID" \
-  --confidence [0.0-1.0] \
-  --iteration 1
-\```
+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
 
-**After reporting, exit cleanly. Do NOT enter waiting mode.**
+**Note:** Coordination instructions are provided when spawned via CLI.
 
 ## Success Metrics
 - Feature fully implemented

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

@@ -122,54 +122,14 @@ async function analyzeWithFallback(system) {
 - `agent/${AGENT_ID}/findings/${TASK_ID}`
 - `cfn/phase-${phaseId}/loop3/agent-${AGENT_ID}`
 
-## CFN Loop Redis Completion Protocol
+## Completion Protocol
 
-When participating in CFN Loop workflows, agents MUST follow this 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
 
-### Step 1: Complete Work
-Execute assigned task (system analysis, performance investigation, code quality assessment)
-
-### Step 2: Signal Completion
-```bash
-redis-cli lpush "swarm:${TASK_ID}:${AGENT_ID}:done" "complete"
-```
-
-### Step 3: Report Confidence Score
-```bash
-./.claude/skills/redis-coordination/invoke-waiting-mode.sh report \
-
-**After reporting, exit cleanly. Do NOT enter waiting mode.**
-
-**Why This Matters:**
-- Orchestrator collects confidence/consensus scores from Redis
-- Enables adaptive agent specialization for next iteration
-- Prevents orchestrator blocking on wait $PID
-- Coordinator spawns appropriate specialist based on feedback type
-
-  --task-id "$TASK_ID" \
-  --agent-id "$AGENT_ID" \
-  --confidence [0.0-1.0] \
-  --iteration 1
-```
-
-### Step 4: Enter Waiting Mode (for potential iteration)
-```bash
-  --task-id "$TASK_ID" \
-  --agent-id "$AGENT_ID" \
-  --context "iteration-complete"
-```
-
-**Why This Matters:**
-- Zero-token blocking coordination (BLPOP waits without API calls)
-- Orchestrator collects confidence/consensus scores automatically
-- Supports autonomous iteration based on quality gates
-- Agent woken instantly (<100ms) if iteration needed
-
-**Context Variables:**
-- `TASK_ID`: Provided by orchestrator/coordinator
-- `AGENT_ID`: Your unique agent identifier (e.g., "analyst-1")
-- Confidence: Your self-assessment score (0.0-1.0)
-
-See: `.claude/skills/redis-coordination/SKILL.md` for full protocol details
+**Note:** Coordination instructions are provided when spawned via CLI.
 
 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

@@ -95,45 +95,12 @@ npx claude-flow@alpha hooks post-edit [FILE_PATH] \
   --memory-key "code-booster/${AGENT_ID}/optimization" \
   --structured
 ```
-## CFN Loop Redis Completion Protocol
+## Completion Protocol
 
-When participating in CFN Loop workflows, agents MUST follow this 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
 
-### Step 1: Complete Work
-Execute assigned task (code optimization, WASM acceleration, performance enhancement)
-
-### Step 2: Signal Completion
-```bash
-redis-cli lpush "swarm:${TASK_ID}:${AGENT_ID}:done" "complete"
-```
-
-### Step 3: Report Confidence Score
-```bash
-./.claude/skills/redis-coordination/invoke-waiting-mode.sh report   --task-id "$TASK_ID"   --agent-id "$AGENT_ID"   --confidence [0.0-1.0]   --iteration 1
-
-**After reporting, exit cleanly. Do NOT enter waiting mode.**
-
-**Why This Matters:**
-- Orchestrator collects confidence/consensus scores from Redis
-- Enables adaptive agent specialization for next iteration
-- Prevents orchestrator blocking on wait $PID
-- Coordinator spawns appropriate specialist based on feedback type
-
-```
-
-### Step 4: Enter Waiting Mode (for potential iteration)
-```bash
-```
-
-**Why This Matters:**
-- Zero-token blocking coordination (BLPOP waits without API calls)
-- Orchestrator collects confidence/consensus scores automatically
-- Supports autonomous iteration based on quality gates
-- Agent woken instantly (<100ms) if iteration needed
-
-**Context Variables:**
-- `TASK_ID`: Provided by orchestrator/coordinator
-- `AGENT_ID`: Your unique agent identifier (e.g., "code-booster-1")
-- Confidence: Self-assessment score of optimization quality and performance gain (0.0-1.0)
-
-See: `.claude/skills/redis-coordination/SKILL.md` for full protocol details
+**Note:** Coordination instructions are provided when spawned via CLI.

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

@@ -45,52 +45,12 @@ Intelligent context merging and prioritization
 - No destructive merges
 - Explainable AI principles
 
-## CFN Loop Redis Completion Protocol
+## Completion Protocol
 
-When participating in CFN Loop workflows, agents MUST follow this 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
 
-### Step 1: Complete Work
-Execute assigned task (context merging, prioritization, adaptive learning strategy)
-
-### Step 2: Signal Completion
-```bash
-redis-cli lpush "swarm:${TASK_ID}:${AGENT_ID}:done" "complete"
-```
-
-### Step 3: Report Confidence Score
-```bash
-./.claude/skills/redis-coordination/invoke-waiting-mode.sh report \
-
-**After reporting, exit cleanly. Do NOT enter waiting mode.**
-
-**Why This Matters:**
-- Orchestrator collects confidence/consensus scores from Redis
-- Enables adaptive agent specialization for next iteration
-- Prevents orchestrator blocking on wait $PID
-- Coordinator spawns appropriate specialist based on feedback type
-
-  --task-id "$TASK_ID" \
-  --agent-id "$AGENT_ID" \
-  --confidence [0.0-1.0] \
-  --iteration 1
-```
-
-### Step 4: Enter Waiting Mode (for potential iteration)
-```bash
-  --task-id "$TASK_ID" \
-  --agent-id "$AGENT_ID" \
-  --context "iteration-complete"
-```
-
-**Why This Matters:**
-- Zero-token blocking coordination (BLPOP waits without API calls)
-- Orchestrator collects confidence/consensus scores automatically
-- Supports autonomous iteration based on quality gates
-- Agent woken instantly (<100ms) if iteration needed
-
-**Context Variables:**
-- `TASK_ID`: Provided by orchestrator/coordinator
-- `AGENT_ID`: Your unique agent identifier (e.g., "context-curator-1")
-- Confidence: Your self-assessment score (0.0-1.0)
-
-See: `.claude/skills/redis-coordination/SKILL.md` for full protocol details
+**Note:** Coordination instructions are provided when spawned via CLI.

package/claude-assets/agents/cfn-dev-team/{coordinators → utility}/epic-creator.md

@@ -105,6 +105,16 @@ 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
+```
+
 ## Success Metrics
 
 - Valid JSON configuration generated
@@ -114,3 +124,22 @@ You embody three complementary personas:
 - Realistic iteration estimates
 - Clear scope boundaries
 - Mode-appropriate thresholds
+
+## Task Completion Protocol
+
+Complete your epic configuration work and provide a structured response with:
+
+1. **Confidence Score** (0.0-1.0) - Self-assessment of configuration quality
+2. **Summary** - Brief overview of epic decomposition and phase planning
+3. **Deliverables** - List the epic configuration JSON file created
+4. **Status** - COMPLETE or NEEDS_WORK with specific issues
+
+**Example Output:**
+```
+Confidence: 0.92
+Status: COMPLETE
+Summary: Created epic configuration with 5 phases for authentication system implementation
+Deliverables:
+- epic-config.json
+- phase-planning.md
+```

package/claude-assets/cfn-agents-ignore/cfn-seo-team/AGENT_CREATION_REPORT.md

@@ -9,7 +9,6 @@
 
 ## Executive Summary
 
-Successfully created 10 specialized SEO agents with focused use cases, clear delegation patterns, and comprehensive integration specifications. All agents follow the CFN Loop Redis Completion Protocol and include confidence scoring criteria.
 
 **Deliverables:**
 - 10 agent definition files (`.claude/agents/seo/*.md`)
@@ -89,7 +88,7 @@ Successfully created 10 specialized SEO agents with focused use cases, clear del
 **Integration Points:**
 - PostgreSQL (source data)
 - Google Search Console API (indexation monitoring)
-- Redis (template caching)
+- Template caching (performance optimization)
 
 ---
 
@@ -268,7 +267,6 @@ Created comprehensive delegation matrix covering:
 - **Quick reference table** (10 agents with tool usage)
 - **Detailed delegation guide** (when to use each agent)
 - **Multi-agent workflows** (4 common scenarios)
-- **Agent communication patterns** (sequential and parallel)
 - **Decision tree** (agent selection logic)
 
 **Key delegation patterns:**
@@ -283,7 +281,7 @@ Created comprehensive delegation matrix covering:
 
 Created comprehensive integration document covering:
 - **12 API integrations** (Google APIs, SEO tools, AI platforms)
-- **4 service dependencies** (PostgreSQL, Redis, n8n, services)
+- **4 service dependencies** (PostgreSQL, caching systems, n8n, services)
 - **7 external tools** (Screaming Frog, Copyscape, Grammarly, etc.)
 - **Cost estimates** ($581/month for full setup, $119/month minimum)
 - **Setup instructions** (API authentication, database schema, testing)
@@ -292,7 +290,6 @@ Created comprehensive integration document covering:
 - SE Ranking API (6 agents depend on it)
 - Google Search Console API (3 agents)
 - PostgreSQL (all agents use for data storage)
-- Redis (3 agents for caching, all agents for CFN Loop coordination)
 
 **Cost optimization:**
 - Minimum viable setup: $119/month (SE Ranking only)
@@ -308,7 +305,6 @@ Created comprehensive integration document covering:
 - ✅ Tools listed as comma-separated arrays: `[Read, Write, Edit]`
 - ✅ Capabilities listed as comma-separated arrays
 - ✅ Description uses pipe operator `|` for multi-line
-- ✅ All agents include CFN Loop Redis Completion Protocol
 
 ### Coverage Completeness
 - ✅ Core Responsibilities: 100% coverage (all agents)
@@ -355,7 +351,7 @@ Each agent has distinct focus:
 
 ### ✅ Integration points documented
 - 12 API integrations detailed (authentication, endpoints, pricing)
-- 4 service dependencies (PostgreSQL, Redis, n8n, services)
+- 4 service dependencies (PostgreSQL, caching systems, n8n, services)
 - Cost estimates provided ($581/month full setup, $119/month minimum)
 
 ### ✅ Example prompts demonstrate realistic usage
@@ -379,8 +375,6 @@ Each agent has distinct focus:
 
 3. **Create test workflows:**
    - Test single agent spawn (technical-seo-specialist for site audit)
-   - Test multi-agent coordination (content launch workflow with 5 agents)
-   - Validate CFN Loop integration (confidence reporting, Redis coordination)
 
 ### Future Enhancements
 1. **Agent refinement:**
@@ -408,13 +402,11 @@ Each agent has distinct focus:
 - Comprehensive delegation matrix with decision tree
 - Detailed integration requirements (12 APIs, 4 services, 7 tools)
 - 60 example prompts covering all use cases
-- Full CFN Loop Redis Completion Protocol integration
 - Cost estimates and setup instructions provided
 
 **Limitations (-0.08):**
 - Some API integrations not yet tested (Perplexity, BrightLocal)
 - Agent performance metrics not yet collected (need real-world usage data)
-- Multi-agent coordination workflows defined but not executed
 - Some external tool integrations require manual steps (Screaming Frog, Copyscape)
 
 **Overall Assessment:**
@@ -458,7 +450,6 @@ High confidence in agent completeness and delegation clarity. Moderate confidenc
 1. Setup PostgreSQL schema (see INTEGRATION_REQUIREMENTS.md)
 2. Configure SE Ranking API key (highest priority integration)
 3. Test agent spawning (single agent, then multi-agent workflow)
-4. Validate CFN Loop coordination (confidence reporting, Redis protocol)
 
 ### For Agent Testing
 1. Spawn technical-seo-specialist for OurStories site audit (test basic functionality)
@@ -474,8 +465,7 @@ Successfully created 10 specialized SEO agents with:
 - **Clear use case separation** (zero overlap)
 - **Comprehensive delegation patterns** (decision tree, workflows)
 - **Detailed integration requirements** (12 APIs, cost estimates, setup instructions)
-- **Production-ready specifications** (CFN Loop protocol, confidence scoring)
+- **Production-ready specifications** (production workflow protocols, confidence scoring)
 
-The SEO agent framework is ready for validation testing with core integrations (SE Ranking, Google Search Console, PostgreSQL). Recommend starting with single-agent tests before multi-agent coordination workflows.
 
 **Confidence Score: 0.92** (high confidence, minor integration uncertainties)