claude-flow-novice 2.14.29 → 2.14.31

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

@@ -89,14 +89,14 @@ BRAND=$(echo "$TASK_DESCRIPTION" | grep -oP 'brand:\s*\K.*' || echo "OurStories"
 AUDIENCE=$(echo "$TASK_DESCRIPTION" | grep -oP 'audience:\s*\K.*' || echo "general")
 TARGET_LOCATION=$(echo "$TASK_DESCRIPTION" | grep -oP 'location:\s*\K.*' || echo "")
 
-# Store in Redis for orchestrator
-redis-cli HSET "seo:task:$TASK_ID:context" \
-  target_keyword "$TARGET_KEYWORD" \
-  content_type "$CONTENT_TYPE" \
-  brand "$BRAND" \
-  audience "$AUDIENCE" \
-  target_location "$TARGET_LOCATION" \
-  task_description "$TASK_DESCRIPTION"
+# Store context for orchestrator
+# Context will be passed to orchestration script
+export SEO_CONTEXT_TARGET_KEYWORD="$TARGET_KEYWORD"
+export SEO_CONTEXT_CONTENT_TYPE="$CONTENT_TYPE"
+export SEO_CONTEXT_BRAND="$BRAND"
+export SEO_CONTEXT_AUDIENCE="$AUDIENCE"
+export SEO_CONTEXT_TARGET_LOCATION="$TARGET_LOCATION"
+export SEO_CONTEXT_TASK_DESCRIPTION="$TASK_DESCRIPTION"
 ```
 
 ## DataForSEO API Integration
@@ -179,16 +179,15 @@ exit 0
 
 **Why Exit After Spawning:**
 - Orchestrator runs as background process
-- Uses Redis for coordination
 - Spawns SEO agents via CLI (Z.ai routing)
-- Reports progress to Redis
-- Main Chat monitors via web portal or Redis
+- Reports progress through output monitoring
+- Main Chat monitors via web portal or output logs
 
 ## Validation Thresholds
 
 **Step 7 Validators:**
 - **Individual Gate:** Each validator ≥0.75 confidence
-- **Consensus:** Average of all validators ≥0.95
+- **Average Score:** Average of all validators ≥0.95
 - **Required Validators:**
   - `humanizer-validator` (natural writing)
   - `branding-validator` (OurStories alignment)
@@ -196,19 +195,20 @@ exit 0
 
 **Iteration Logic:**
 ```bash
-# Collect validator scores
-HUMANIZER_SCORE=$(redis-cli HGET "seo:task:$TASK_ID:validation:iteration:$ITERATION" humanizer)
-BRANDING_SCORE=$(redis-cli HGET "seo:task:$TASK_ID:validation:iteration:$ITERATION" branding)
-AUDIENCE_SCORE=$(redis-cli HGET "seo:task:$TASK_ID:validation:iteration:$ITERATION" audience)
+# Collect validator scores from validation results
+# Scores are retrieved from orchestration output or validation results
+HUMANIZER_SCORE=$(cat validation_results.json | jq -r '.humanizer // 0')
+BRANDING_SCORE=$(cat validation_results.json | jq -r '.branding // 0')
+AUDIENCE_SCORE=$(cat validation_results.json | jq -r '.audience // 0')
 
-# Calculate consensus
-CONSENSUS=$(echo "scale=2; ($HUMANIZER_SCORE + $BRANDING_SCORE + $AUDIENCE_SCORE) / 3" | bc)
+# Calculate average
+AVERAGE_SCORE=$(echo "scale=2; ($HUMANIZER_SCORE + $BRANDING_SCORE + $AUDIENCE_SCORE) / 3" | bc)
 
 # Decision
-if (( $(echo "$CONSENSUS >= 0.95" | bc -l) )); then
+if (( $(echo "$AVERAGE_SCORE >= 0.95" | bc -l) )); then
   echo "✅ Validation passed - Proceed to publishing"
 else
-  echo "🔄 Iteration required - Consensus: $CONSENSUS"
+  echo "🔄 Iteration required - Average Score: $AVERAGE_SCORE"
   # Wake Step 5 (writer) with validator feedback
 fi
 ```
@@ -247,7 +247,7 @@ esac
 
 **Coordinator Success:**
 - Task classified correctly
-- Context extracted and stored in Redis
+- Context extracted and passed to orchestrator
 - Orchestrator invoked successfully
 - All required API credentials validated
 - Clean exit after spawning orchestrator
@@ -259,7 +259,7 @@ esac
 - Step 4: Research complete (≥5 sources)
 - Step 5: Draft written (≥1500 words for blog)
 - Step 6: SEO optimized (title tag, meta description, headers, schema)
-- Step 7: Validation consensus ≥0.95
+- Step 7: Validation average ≥0.95
 - Step 8: Published with schema markup
 
 ## Output Format
@@ -283,27 +283,279 @@ Return structured JSON for Main Chat visibility:
     "perplexity": "enabled"
   },
   "estimated_duration": "45-60 minutes",
-  "monitoring": "redis-cli HGETALL seo:task:seo-task-12345:status"
+  "monitoring": "Output logs track progress and agent status"
 }
 ```
 
-## Redis Monitoring Commands
+## Redis Coordination System
+
+The SEO coordinator uses Redis-based coordination for CLI-mode SEO agent orchestration. This enables swarm recovery, progress tracking, and cost optimization.
+
+### SEO-Specific Redis Context Storage
+
+Store SEO campaign parameters and pipeline state:
+
+```bash
+# SEO Campaign Context Storage
+redis-cli HSET "seo_campaign:${TASK_ID}:context" \
+  "campaign_type" "${CONTENT_TYPE}" \
+  "target_keyword" "${TARGET_KEYWORD}" \
+  "brand" "${BRAND}" \
+  "audience" "${AUDIENCE}" \
+  "target_location" "${TARGET_LOCATION}" \
+  "content_type" "${CONTENT_TYPE}" \
+  "pipeline_steps" "${PIPELINE_STEPS}" \
+  "iteration" "1"
+
+# SEO Pipeline Configuration
+redis-cli HSET "seo_campaign:${TASK_ID}:config" \
+  "dataforseo_api" "${DATAFORSEO_API_KEY:-UNSET}" \
+  "openrouter_api" "${OPENROUTER_API_KEY:-UNSET}" \
+  "specialists" "${SEO_SPECIALISTS}" \
+  "validation_threshold" "0.95" \
+  "cost_optimization" "enabled"
+
+# Store step-specific context for each SEO specialist
+for step in ${PIPELINE_STEPS}; do
+  redis-cli HSET "seo_campaign:${TASK_ID}:step:${step}" \
+    "status" "pending" \
+    "agent_type" "${step}" \
+    "iteration" "1"
+done
+```
+
+### SEO Specialist Agent Spawning with Context
+
+```bash
+# Spawn SEO specialists with campaign context
+SEO_SPECIALISTS=("seo-analytics-specialist" "content-seo-strategist" "technical-seo-specialist" "schema-markup-engineer")
+
+for specialist in "${SEO_SPECIALISTS[@]}"; do
+  AGENT_ID="${TASK_ID}-${specialist}-$(date +%s)"
+
+  # Store specialist-specific SEO context
+  redis-cli HSET "seo_agent:${AGENT_ID}" \
+    "agent_type" "${specialist}" \
+    "task_id" "${TASK_ID}" \
+    "campaign_type" "${CONTENT_TYPE}" \
+    "target_keyword" "${TARGET_KEYWORD}" \
+    "brand" "${BRAND}" \
+    "pipeline_step" "${specialist}" \
+    "status" "spawning"
+
+  # Inject SEO context and spawn via CLI (cost-optimized Z.ai routing)
+  SEO_CONTEXT=$(cat <<EOF
+SEO Campaign Execution for ${CONTENT_TYPE}
+
+Campaign Parameters:
+- Target Keyword: ${TARGET_KEYWORD}
+- Brand: ${BRAND}
+- Audience: ${AUDIENCE}
+- Content Type: ${CONTENT_TYPE}
+- Pipeline Step: ${specialist}
+
+Specialist Instructions: $(redis-cli HGET "seo_campaign:${TASK_ID}:specialist_instructions" "${specialist}")
+EOF
+  )
+
+  npx claude-flow-novice agent-spawn "${specialist}" \
+    --task-id "${TASK_ID}" \
+    --agent-id "${AGENT_ID}" \
+    --context "${SEO_CONTEXT}" &
+
+  SEO_AGENT_PIDS+=($!)
+done
+
+# Wait for all SEO specialists to complete
+wait "${SEO_AGENT_PIDS[@]}"
+```
+
+### SEO Pipeline Completion Collection
 
-**For Main Chat / User:**
 ```bash
-# Check overall status
-redis-cli HGETALL "seo:task:$TASK_ID:status"
+# Collect SEO specialist completion signals
+SEO_CONFIDENCES=()
+SEO_DELIVERABLES=()
+
+for specialist in "${SEO_SPECIALISTS[@]}"; do
+  # Block for specialist completion (zero-token blocking)
+  COMPLETION_SIGNAL=$(redis-cli blpop "swarm:${TASK_ID}:${specialist}:done" 300)
+
+  if [ -n "$COMPLETION_SIGNAL" ]; then
+    # Extract specialist confidence
+    CONFIDENCE=$(redis-cli HGET "seo_campaign:${TASK_ID}:confidence:${specialist}")
+    SEO_CONFIDENCES+=("$CONFIDENCE")
+
+    # Track deliverables created by this specialist
+    DELIVERABLES_JSON=$(redis-cli HGET "seo_campaign:${TASK_ID}:deliverables:${specialist}")
+    SEO_DELIVERABLES+=("$DELIVERABLES_JSON")
+
+    echo "✅ ${specialist} completed with confidence: ${CONFIDENCE}"
+  else
+    echo "⚠️ SEO specialist ${specialist} timed out"
+    SEO_CONFIDENCES+=("0.0")
+  fi
+done
+
+# Calculate SEO pipeline confidence
+AVERAGE_SEO_CONFIDENCE=$(printf '%s\n' "${SEO_CONFIDENCES[@]}" | awk '{sum+=$1} END {print sum/NR}')
+echo "SEO Pipeline average confidence: $AVERAGE_SEO_CONFIDENCE"
+```
 
-# Check current step
-redis-cli HGET "seo:task:$TASK_ID:status" current_step
+### SEO Content Strategy Consensus
 
-# Check validation scores
-redis-cli HGETALL "seo:task:$TASK_ID:validation:iteration:1"
+For content strategy decisions (keyword selection, content structure, optimization strategy):
 
-# Monitor orchestrator logs
-redis-cli LRANGE "seo:task:$TASK_ID:logs" 0 -1
+```bash
+# Content Strategy Consensus Collection
+STRATEGY_VALIDATORS=("competitive-seo-analyst" "content-seo-strategist" "technical-seo-specialist")
+STRATEGY_CONSENSUSES=()
+
+for validator in "${STRATEGY_VALIDATORS[@]}"; do
+  # Collect strategy consensus signals
+  CONSENSUS_SIGNAL=$(redis-cli blpop "swarm:${TASK_ID}:${validator}:strategy_done" 180)
+
+  if [ -n "$CONSENSUS_SIGNAL" ]; then
+    STRATEGY_SCORE=$(redis-cli HGET "seo_campaign:${TASK_ID}:strategy_consensus:${validator}")
+    STRATEGY_CONSENSUSES+=("$STRATEGY_SCORE")
+  else
+    STRATEGY_CONSENSUSES+=("0.0")
+  fi
+done
+
+# Calculate strategy consensus for SEO decisions
+STRATEGY_AVERAGE=$(printf '%s\n' "${STRATEGY_CONSENSUSES[@]}" | awk '{sum+=$1} END {print sum/NR}')
 ```
 
+### SEO Validation Gate (Content Quality)
+
+SEO content must pass validation gate before publishing:
+
+```bash
+# SEO Validation Gate Check
+VALIDATION_THRESHOLD=0.95
+
+if (( $(echo "$AVERAGE_SEO_CONFIDENCE >= $VALIDATION_THRESHOLD" | bc -l) )); then
+  echo "✅ SEO Content Quality Gate PASSED"
+
+  # Store gate result and signal schema generation
+  redis-cli HSET "seo_campaign:${TASK_ID}:validation_gate" \
+    "status" "passed" \
+    "confidence" "$AVERAGE_SEO_CONFIDENCE" \
+    "timestamp" "$(date -u +%Y-%m-%dT%H:%M:%SZ)"
+
+  # Signal schema-markup-engineer to create structured data
+  redis-cli lpush "swarm:${TASK_ID}:seo-validation-passed" "1"
+
+  # Trigger schema generation and publishing
+  spawn_schema_generation
+else
+  echo "❌ SEO Content Quality Gate FAILED - requires optimization"
+
+  # Store failure and prepare optimization feedback
+  redis-cli HSET "seo_campaign:${TASK_ID}:validation_gate" \
+    "status" "failed" \
+    "confidence" "$AVERAGE_SEO_CONFIDENCE" \
+    "optimization_needed" "true"
+
+  # Prepare content optimization feedback
+  prepare_seo_optimization_feedback
+fi
+```
+
+### SEO Specialist Completion Protocol (Mode-Specific)
+
+```bash
+# CLI Mode Completion Signal (REQUIRED for CLI-spawned SEO specialists)
+signal_seo_specialist_completion() {
+  local confidence="$1"
+  local deliverables="$2"
+  local specialist_type="$3"
+
+  if [[ -n "${TASK_ID:-}" && -n "${AGENT_ID:-}" ]]; then
+    # Signal specialist completion
+    redis-cli lpush "swarm:${TASK_ID}:${AGENT_ID}:done" "complete"
+
+    # Store SEO-specific confidence and deliverables
+    redis-cli HSET "seo_campaign:${TASK_ID}:confidence:${AGENT_ID}" \
+      "confidence" "$confidence" \
+      "specialist_type" "$specialist_type" \
+      "deliverables_created" "$deliverables" \
+      "reported_at" "$(date -u +%Y-%m-%dT%H:%M:%SZ)"
+
+    # Use coordination script for structured reporting
+    ./.claude/skills/cfn-redis-coordination/invoke-waiting-mode.sh report \
+      --task-id "$TASK_ID" \
+      --agent-id "$AGENT_ID" \
+      --confidence "$confidence" \
+      --iteration 1 \
+      --result '{"deliverables": '"$deliverables"', "specialist_type": "'"$specialist_type"'"}'
+  fi
+}
+
+# Task Mode (if spawned via Task() in Main Chat)
+# Simply return JSON response - no Redis signals needed
+```
+
+### SEO Pipeline Progress Monitoring
+
+```bash
+# Monitor SEO pipeline progress in real-time
+monitor_seo_pipeline_progress() {
+  local task_id="$1"
+
+  while true; do
+    echo "=== SEO Pipeline Status ==="
+
+    # Check each pipeline step
+    for step in keyword-research competitor-analysis content-outline research seo-writing seo-optimization validation schema-generation; do
+      step_status=$(redis-cli HGET "seo_campaign:${task_id}:step:${step}" "status" 2>/dev/null || echo "not_started")
+      echo "  ${step}: ${step_status}"
+    done
+
+    # Overall pipeline confidence
+    overall_confidence=$(redis-cli HGET "seo_campaign:${task_id}:validation_gate" "confidence" 2>/dev/null || echo "0.00")
+    echo "  Overall Confidence: ${overall_confidence}"
+
+    # Cost optimization status
+    cost_savings=$(redis-cli HGET "seo_campaign:${task_id}:config" "cost_optimization")
+    echo "  Cost Optimization: ${cost_savings:-disabled}"
+
+    echo ""
+    sleep 30
+  done
+}
+
+# Enable swarm recovery for SEO campaigns
+recover_seo_campaign() {
+  local task_id="$1"
+
+  # Restore campaign context
+  CAMPAIGN_CONTEXT=$(redis-cli HGETALL "seo_campaign:${task_id}:context" | jq -s 'reduce .[] as $item ({}; . + $item)')
+
+  echo "🔄 Recovering SEO Campaign: $(echo "$CAMPAIGN_CONTEXT" | jq -r '.target_keyword')"
+  echo "   Campaign Type: $(echo "$CAMPAIGN_CONTEXT" | jq -r '.campaign_type')"
+  echo "   Last Iteration: $(echo "$CAMPAIGN_CONTEXT" | jq -r '.iteration')"
+
+  # Resume from last completed step
+  LAST_COMPLETED_STEP=$(redis-cli HGETALL "seo_campaign:${task_id}:step:*" | grep "completed" | tail -1 | cut -d: -f3)
+  if [ -n "$LAST_COMPLETED_STEP" ]; then
+    echo "   Resuming from: ${LAST_COMPLETED_STEP}"
+  fi
+}
+```
+
+## Progress Monitoring
+
+The Redis coordination system tracks all SEO specialist progress and validation results in real-time:
+
+- **Specialist Progress**: Track each SEO pipeline step completion status
+- **Confidence Scores**: Monitor quality gate thresholds for content validation
+- **Cost Optimization**: Z.ai routing enabled for all SEO specialists (95% cost savings)
+- **Swarm Recovery**: SEO campaign state survives disconnections and can be resumed
+
+Status updates and progress monitoring are handled automatically through the Redis coordination layer.
+
 ## CLI Mode Cost Optimization
 
 **Agent Spawning Pattern:**
@@ -329,7 +581,7 @@ npx claude-flow-novice agent-spawn seo-analytics-specialist \
 # Fallback to manual steps
 if [ -z "$DATAFORSEO_EMAIL" ]; then
   echo "Warning: DataForSEO not configured - Manual keyword research required"
-  redis-cli HSET "seo:task:$TASK_ID:warnings" dataforseo "manual_research_required"
+  echo "manual_research_required" > warnings/dataforseo.txt
 fi
 ```
 
@@ -338,27 +590,20 @@ fi
 # Check orchestrator health
 if ! ps -p $ORCHESTRATOR_PID > /dev/null 2>&1; then
   echo "Error: Orchestrator process died unexpectedly"
-  redis-cli HSET "seo:task:$TASK_ID:status" orchestrator_status "failed"
+  echo "failed" > status/orchestrator_status.txt
   exit 1
 fi
 ```
 
-## Integration with CFN Loop
-
-**Not a CFN Loop Coordinator:**
-- SEO pipeline is specialized (8-step sequential, not 3-loop validation)
-- No Loop 3/Loop 2/Product Owner pattern
-- Uses custom validation (3 validators with ≥0.95 consensus)
+## SEO Pipeline Characteristics
 
-**Similarities:**
+**SEO Pipeline Features:**
+- Specialized SEO workflow (8-step sequential process)
+- Custom validation approach (3 validators with ≥0.95 average score)
 - CLI spawning for cost optimization
-- Redis coordination
 - Iteration-based improvement
 - Confidence-based progression
 
-**When to Use CFN Loop vs SEO Pipeline:**
-- CFN Loop: Generic software development, features, bugs
-- SEO Pipeline: SEO content creation specifically
 
 ## Workflow Example
 
@@ -371,7 +616,7 @@ fi
    - Brand: "OurStories"
    - Audience: "families, genealogists" (inferred)
 3. Validate APIs: DataForSEO ✅, OpenRouter ✅
-4. Store context in Redis
+4. Set context environment variables
 5. Invoke orchestrator:
    ```bash
    ./.claude/skills/seo-orchestration/orchestrate-seo.sh \
@@ -391,7 +636,7 @@ fi
 - Step 4: Perplexity research (gather sources)
 - Step 5: Write 1500+ word draft
 - Step 6: SEO optimize (title tag, meta, headers, internal links)
-- Step 7: Validate (humanizer + branding + audience ≥0.95 consensus)
+- Step 7: Validate (humanizer + branding + audience ≥0.95 average)
 - Step 8: Publish with Article schema
 
 **Final Output:** `content/blog/preserve-family-stories.md` with full schema markup
@@ -406,5 +651,5 @@ fi
 ---
 
 **Version:** 1.0.0
-**Last Updated:** 2025-11-01
-**Maintained By:** CFN SEO Team
+**Last Updated:** 2025-11-07
+**Maintained By:** CFN SEO Team