claude-flow-novice 2.5.2 → 2.8.1

package/.claude/commands/cfn-loop.md

@@ -85,7 +85,7 @@ Extract parameters from command:
 ### Step 2: Spawn Coordinator Agent (SINGLE AGENT PATTERN)
 
 ```javascript
-Task("cost-savings-cfn-loop-coordinator", `
+Task("cfn-v3-coordinator", `
   CFN LOOP EXECUTION - STRUCTURED PARAMETERS
 
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
@@ -124,9 +124,9 @@ Task("cost-savings-cfn-loop-coordinator", `
   TASK SPECIFICATION
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-  Task Description: ${taskDescription}
-  Phase Name: ${phaseName || 'default'}
-  Task ID: cfn-${phaseName}-$(date +%s)
+  Task Description: $ARGUMENTS
+  Phase Name: (extract from task description or use 'default')
+  Task ID: cfn-phase-$(date +%s)
 
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
   SUCCESS CRITERIA (REQUIRED)
@@ -139,14 +139,14 @@ Task("cost-savings-cfn-loop-coordinator", `
   - [ ] Documentation updated
   - [ ] No regression in existing features
 
-  Quality Gates:
-  - Loop 3 Gate Threshold: ${gateThreshold} (${mode} mode)
-  - Loop 2 Consensus Threshold: ${consensusThreshold} (${mode} mode)
-  - Max Loop 3 Iterations: ${maxLoop3}
-  - Max Loop 2 Iterations: ${maxLoop2}
+  Quality Gates (STANDARD MODE):
+  - Loop 3 Gate Threshold: 0.75
+  - Loop 2 Consensus Threshold: 0.90
+  - Max Loop 3 Iterations: 10
+  - Max Loop 2 Iterations: 10
 
   Definition of Done:
-  - Consensus ≥${consensusThreshold} achieved
+  - Consensus ≥0.90 achieved
   - All acceptance criteria met
   - Product Owner approval received
 
@@ -154,13 +154,18 @@ Task("cost-savings-cfn-loop-coordinator", `
   ORCHESTRATION CONFIGURATION
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-  Mode: ${mode.toUpperCase()}
+  Mode: STANDARD
 
-  Loop 3 Agents (Implementation):
-  - ${loop3Agents.join('\n  - ')}
+  Loop 3 Agents (Implementation) - CUSTOMIZE FOR TASK:
+  - researcher (requirement analysis)
+  - backend-dev (implementation)
+  - devops (deployment/infrastructure)
 
-  Loop 2 Agents (Validation):
-  - ${loop2Agents.join('\n  - ')}
+  Loop 2 Agents (Validation) - CUSTOMIZE FOR TASK:
+  - reviewer (code review)
+  - architect (design validation)
+  - tester (quality assurance)
+  - security-specialist (security audit)
 
   Product Owner: product-owner
 
@@ -169,24 +174,32 @@ Task("cost-savings-cfn-loop-coordinator", `
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
   1. INVOKE ORCHESTRATOR:
-     ./.claude/skills/redis-coordination/orchestrate-cfn-loop.sh \\
-       --task-id "${taskId}" \\
-       --mode ${mode} \\
-       --loop3-agents "${loop3Agents.join(',')}" \\
-       --loop2-agents "${loop2Agents.join(',')}" \\
-       --product-owner "product-owner" \\
-       --max-iterations ${maxLoop2}
+     # Generate task ID and construct bash command with actual values
+     # DO NOT use template literals - construct real bash variables
+
+     TASK_ID="cfn-phase-$(date +%s)"
+     MODE="standard"
+     LOOP3_AGENTS="researcher,backend-dev,devops"
+     LOOP2_AGENTS="reviewer,architect,tester,security-specialist"
+
+     ./.claude/skills/cfn-loop-orchestration/orchestrate.sh \
+       --task-id "$TASK_ID" \
+       --mode "$MODE" \
+       --loop3-agents "$LOOP3_AGENTS" \
+       --loop2-agents "$LOOP2_AGENTS" \
+       --product-owner "product-owner" \
+       --max-iterations 10
 
   2. MONITOR PROGRESS:
      - Use web portal: http://localhost:3000
      - Query metrics: ./.claude/skills/web-portal/invoke-portal-metrics.sh
-     - Track events: ./.claude/skills/web-portal/invoke-portal-events.sh --phase ${phaseName}
+     - Track events: ./.claude/skills/web-portal/invoke-portal-events.sh --phase <phase-name>
 
   3. REPORT RESULTS:
      Return structured result to Main Chat:
      {
-       "taskId": "${taskId}",
-       "phase": "${phaseName}",
+       "taskId": "<actual-task-id>",
+       "phase": "<phase-name>",
        "status": "complete|failed",
        "iterations": {
          "loop3": N,
@@ -211,7 +224,7 @@ Task("cost-savings-cfn-loop-coordinator", `
   - WAKE agents via invoke-waiting-mode.sh wake
   - PUBLISH events to web-portal:events channel
   - RETURN structured result when complete
-`, "cost-savings-cfn-loop-coordinator")
+`, "cfn-v3-coordinator")
 ```
 
 ### Step 3: Coordinator Autonomous Execution
@@ -222,16 +235,16 @@ The coordinator runs the orchestrator script internally, which:
 - Spawns workers via CLI: `npx cfn-spawn agent <agent-type>`
 - Each agent completes work and reports confidence
 - Orchestrator collects scores and checks gate threshold
-- **PASS** (≥${gateThreshold}) → Signal Loop 2 to start
-- **FAIL** (<${gateThreshold}) → Wake Loop 3 for iteration N+1
+- **PASS** (≥0.75) → Signal Loop 2 to start
+- **FAIL** (<0.75) → Wake Loop 3 for iteration N+1
 
 **Loop 2: Validation**
 - **WAITS** for Loop 3 gate pass signal (Redis BLPOP)
 - Spawns validators via CLI
 - Each validator reviews and reports consensus score
 - Orchestrator collects scores and checks consensus threshold
-- **PASS** (≥${consensusThreshold}) → Task complete
-- **FAIL** (<${consensusThreshold}) → Wake all agents for iteration N+1
+- **PASS** (≥0.90) → Task complete
+- **FAIL** (<0.90) → Wake all agents for iteration N+1
 
 **Loop 1: Product Owner**
 - Reviews final consensus and acceptance criteria
@@ -243,10 +256,10 @@ The coordinator runs the orchestrator script internally, which:
 **Real-time monitoring:**
 ```bash
 # View all agents
-./.claude/skills/web-portal/invoke-portal-agents.sh --swarm cfn-${PHASE_NAME}
+./.claude/skills/web-portal/invoke-portal-agents.sh --swarm cfn-<phase-name>
 
 # Track phase events
-./.claude/skills/web-portal/invoke-portal-events.sh --phase ${PHASE_NAME}
+./.claude/skills/web-portal/invoke-portal-events.sh --phase <phase-name>
 
 # Get consensus metrics
 ./.claude/skills/web-portal/invoke-portal-metrics.sh --view consensus

package/.claude/commands/cfn-mode.md

@@ -0,0 +1,20 @@
+---
+name: cfn-mode
+description: Toggle CFN Loop v3 spawning mode (cli vs task) for cost optimization or debugging
+---
+
+Toggle between CLI spawning (cost-optimized, Z.ai routing) and Task spawning (simplified, full visibility).
+
+**Usage:**
+/cfn-mode cli      # Enable CLI spawning (default, 95-98% savings)
+/cfn-mode task     # Enable Task spawning (debugging, full visibility)
+/cfn-mode status   # Show current mode
+
+**Current Mode:**
+Check `.cfn-mode.json` or run `/cfn-mode status`
+
+**Mode Details:**
+- **CLI Mode**: Coordinator → orchestrator → CLI agents (Z.ai routing)
+- **Task Mode**: Coordinator → JSON → Main Chat spawns Task() agents (Anthropic)
+
+Both modes use Redis context storage for swarm recovery.

package/.claude/commands/custom-routing-activate.md

@@ -1,141 +1,55 @@
-# /custom-routing-activate - Enable Cost-Optimized Routing
+---
+description: DEPRECATED - Use /switch-api zai instead
+tags: [deprecated, routing]
+---
 
-Activate tiered provider routing to reduce LLM costs by routing most agents to Z.ai while keeping high-value agents on Anthropic.
+# ⚠️ DEPRECATED Command
 
-## Usage
+**This command is deprecated and no longer needed.**
 
-```bash
-/custom-routing-activate
-```
-
-Simple! No arguments needed. Just run the command to enable cost optimization.
-
-## What It Does
-
-Activates intelligent routing with three priority levels:
-
-### Priority 1: Agent Profile Override
-Agents can specify their preferred provider in their profile:
-```yaml
-provider: zai        # Force Z.ai for this agent
-provider: anthropic  # Force Anthropic for this agent
-```
-
-### Priority 2: Tier Configuration
-**ALL Task Tool agents route to Z.ai** for maximum cost savings:
-- `coder`, `tester`, `reviewer` → Z.ai
-- `architect`, `coordinator`, `system-architect` → Z.ai
-- `devops-engineer`, `security-specialist` → Z.ai
-- All 70+ agent types → Z.ai
-
-Only the main chat uses Anthropic Claude Max:
-- `main-chat` → Anthropic (your direct conversations)
-
-## Cost Savings
-
-**Example calculation:**
-```
-Without routing: 100 agent calls × $0.015 = $1.50
-With routing:    99 calls × $0.003 (Z.ai) + 1 call × $0.015 (main-chat) = $0.31
-
-💰 Savings: 79% cost reduction (all agents on Z.ai)
-```
-
-## Output
-
-When you run `/custom-routing-activate`:
-
-```
-═══════════════════════════════════════════════════════
-   Activating Tiered Provider Routing
-═══════════════════════════════════════════════════════
-
-✅ Tiered Provider Routing ACTIVATED
+## Use Instead
 
-📊 Active Routing:
-  • ALL Task Tool agents (70+ types) → Z.ai
-  • Main chat only → Anthropic Claude Max
-  • Maximum cost optimization enabled
-
-💰 Cost Optimization:
-  • ~79% cost reduction on agent usage
-  • All spawned agents use affordable Z.ai provider
-  • Only main chat uses Anthropic Claude Max
-
-🎯 Agent Profile Overrides:
-  • Add provider: zai to agent profile → force Z.ai
-  • Add provider: anthropic to agent profile → force Anthropic
-
-💾 Configuration saved to:
-   /path/to/project/.claude/settings.json
-
-📖 To disable routing:
-   /custom-routing-deactivate
-═══════════════════════════════════════════════════════
-```
-
-## When to Use
-
-**Enable for:**
-- ✅ Production development (cost savings)
-- ✅ High-volume agent usage
-- ✅ Projects with budget constraints
-- ✅ Default recommendation for most projects
-
-**Disable for:**
-- Testing quality differences between providers
-- Debugging provider-specific issues
-- Ensuring consistent provider behavior
-- Short-term projects where consistency matters more than cost
-
-## Configuration
-
-Settings are saved to `.claude/settings.json`:
-
-```json
-{
-  "tieredRouting": {
-    "enabled": true
-  }
-}
+```bash
+/switch-api zai
 ```
 
-## Related Commands
+## What Changed
 
-- `/custom-routing-deactivate` - Disable tiered routing
-- `/cfn-loop` - Self-correcting development loop (respects routing)
-- `/swarm` - Multi-agent coordination (respects routing)
+**Old system (custom-routing):**
+- Designed for per-agent profile routing
+- Required `tieredRouting` flag in settings.json
+- Never fully implemented
 
-## Best Practices
+**New system (switch-api):**
+- ✅ Simple env var configuration
+- ✅ Works with Main Chat + Task tool
+- ✅ CLI agents use separate routing (.env)
+- ✅ Fully operational
 
-1. **Enable by default** - Activate routing for immediate cost savings
-2. **Monitor quality** - Ensure Z.ai quality meets your standards
-3. **Profile strategic agents** - Mark critical agents with `provider: anthropic`
-4. **Test both modes** - Compare results with routing on and off
+## Migration
 
-## Examples
-
-### First-time activation
+**If you were using `/custom-routing-activate`:**
 ```bash
-$ /custom-routing-activate
-
-✅ Tiered Provider Routing ACTIVATED
-
-💰 Cost Optimization:
-  • ~64% cost reduction on agent usage
+# Just run this instead:
+/switch-api zai
 ```
 
-### Already activated
-```bash
-$ /custom-routing-activate
+**Effect:**
+- Main Chat + Task() agents use Z.ai ($0.50/1M)
+- CLI agents use Z.ai (from .env)
+- Combined 97% cost savings
 
-✅ Tiered routing is already ENABLED
+## Why Deprecated
 
-💡 To disable, run: /custom-routing-deactivate
-```
+The custom-routing system was designed but never fully implemented. The new switch-api provides:
+
+1. **Simpler configuration** - Just env vars
+2. **Actually works** - Complete implementation
+3. **Clear separation** - Main Chat vs CLI routing
+4. **Better documentation** - See `/switch-api` help
 
 ## See Also
 
-- **Deactivation**: `/custom-routing-deactivate`
-- **Status Check**: `/activate-custom-routing` (shows current status)
-- **Agent Profiles**: `.claude/agents/*.md` (add `provider` field)
+- `/switch-api` - Current routing system
+- `/switch-api zai` - Enable Z.ai for Main Chat
+- `/switch-api max` - Use Anthropic for Main Chat

package/.claude/commands/custom-routing-deactivate.md

@@ -1,143 +1,46 @@
-# /custom-routing-deactivate - Disable Tiered Routing
+---
+description: DEPRECATED - Use /switch-api max instead
+tags: [deprecated, routing]
+---
 
-Deactivate tiered provider routing so all agents use the default provider configuration (sonnet model).
+# ⚠️ DEPRECATED Command
 
-## Usage
+**This command is deprecated and no longer needed.**
 
-```bash
-/custom-routing-deactivate
-```
-
-Simple! No arguments needed. Just run the command to disable tiered routing.
-
-## What It Does
-
-Disables profile-based provider routing. After deactivation:
-
-- ✅ All agents use **sonnet model** (from agent profiles)
-- ✅ Single provider for all agents
-- ✅ No provider-based routing
-- ✅ Consistent behavior across all agents
-
-## Use Cases
-
-**Disable for:**
-- Testing quality differences between providers
-- Debugging provider-specific issues
-- Ensuring consistent provider behavior
-- A/B testing routing vs non-routing
-- Projects where consistency matters more than cost
-
-**Enable for:**
-- Production development (cost savings)
-- High-volume agent usage
-- Projects with budget constraints
-
-## Output
-
-When you run `/custom-routing-deactivate`:
-
-```
-═══════════════════════════════════════════════════════
-   Deactivating Tiered Provider Routing
-═══════════════════════════════════════════════════════
-
-✅ Tiered Provider Routing DEACTIVATED
-
-📊 Current Routing:
-  • All agents use sonnet model (from agent profiles)
-  • Single provider for all agents
-  • No provider-based routing
-
-⚠️  Cost Impact:
-  • All agents use default provider (typically Anthropic)
-  • No cost optimization active
-  • Useful for testing or consistency requirements
-
-💾 Configuration saved to:
-   /path/to/project/.claude/settings.json
-
-📖 To enable routing:
-   /custom-routing-activate
-═══════════════════════════════════════════════════════
-```
+## Use Instead
 
-## Configuration
-
-Settings are saved to `.claude/settings.json`:
-
-```json
-{
-  "tieredRouting": {
-    "enabled": false
-  }
-}
-```
-
-## Cost Impact
-
-**Without routing (after deactivation):**
-```
-100 agent calls × $0.015 (Anthropic) = $1.50
-```
-
-**With routing (before deactivation):**
-```
-80 calls × $0.003 (Z.ai) + 20 calls × $0.015 (Anthropic) = $0.54
+```bash
+/switch-api max
 ```
 
-**Impact of deactivation:** +$0.96 per 100 agent calls (178% increase)
-
-## Related Commands
-
-- `/custom-routing-activate` - Enable tiered routing
-- `/activate-custom-routing` - Show routing status
-- `/cfn-loop` - Self-correcting development loop
+## What This Does
 
-## When to Deactivate
+Switches Main Chat + Task tool back to Anthropic (default provider).
 
-### Good Reasons:
-✅ Testing quality differences
-✅ Debugging provider issues
-✅ Short-term consistency needs
-✅ Comparing routing vs non-routing
+**Note:** Requires running `claude login` after switching.
 
-### Bad Reasons:
-❌ "I don't understand routing" - Learn it first, saves money
-❌ "Too complicated" - It's automatic once enabled
-❌ "Not sure if it works" - Test it with small tasks first
+## Migration
 
-## Examples
-
-### Deactivate routing
+**If you were using `/custom-routing-deactivate`:**
 ```bash
-$ /custom-routing-deactivate
-
-✅ Tiered Provider Routing DEACTIVATED
+# Just run this instead:
+/switch-api max
 
-📊 Current Routing:
-  • All agents use sonnet model (from agent profiles)
-  • Single provider for all agents
+# Then re-authenticate:
+claude login
 ```
 
-### Already deactivated
-```bash
-$ /custom-routing-deactivate
-
-✅ Tiered routing is already DISABLED
-
-💡 To enable cost optimization, run: /custom-routing-activate
-```
+## Why Deprecated
 
-## Best Practices
+The custom-routing system was designed but never fully implemented. The new switch-api provides the same functionality with:
 
-1. **Deactivate temporarily** - Only disable for testing, then re-enable
-2. **Document why** - Note the reason for deactivation in project docs
-3. **Set reminder** - Remember to re-enable after testing
-4. **Compare results** - Use deactivation to validate routing quality
+1. **Simpler commands** - `/switch-api zai` or `/switch-api max`
+2. **Actually works** - Complete implementation
+3. **Clear behavior** - Explicit env var management
+4. **Better docs** - See `/switch-api` help
 
 ## See Also
 
-- **Activation**: `/custom-routing-activate`
-- **Status Check**: `/activate-custom-routing`
-- **Cost Analysis**: Check `.claude/settings.json` for current state
+- `/switch-api` - Current routing system
+- `/switch-api max` - Use Anthropic for Main Chat
+- `/switch-api zai` - Use Z.ai for cost savings

package/.claude/commands/switch-api.md

@@ -1,28 +1,53 @@
 ---
-description: Switch between z.ai and Anthropic Claude Max API providers
-tags: [config, api, utility]
+description: Switch Main Chat and Task tool between Z.ai and Anthropic providers
+tags: [config, api, cost-optimization]
 ---
 
-Switch Claude API provider between z.ai (GLM models) and official Anthropic Claude Max.
+Switch Main Chat and Task() tool API provider between Z.ai (cost-optimized) and Anthropic (high-quality).
+
+**Important:** CLI agents always use Z.ai (from `.env`). This command only affects Main Chat and Task() spawned agents.
 
 **Usage:**
-- `/switch-api` - Show current API
-- `/switch-api zai` - Switch to z.ai (GLM-4.6)
-- `/switch-api max` - Switch to Claude Max
-- `/switch-api list` - List saved configurations
-- `/switch-api save <name>` - Save current config
-- `/switch-api restore <name>` - Restore saved config
+- `/switch-api` - Show current status
+- `/switch-api zai` - Main Chat/Task tool use Z.ai ($0.50/1M tokens)
+- `/switch-api max` - Main Chat/Task tool use Anthropic ($15/1M tokens, requires re-login)
 
 **Arguments:**
-- `zai` - Use z.ai API with GLM models
-- `max` or `claude` - Use official Anthropic API
-- `status` - Show current API configuration
-- `list` - List all saved configurations
-- `save <name>` - Save current settings
-- `restore <name>` - Restore previously saved settings
+- `status` - Show current routing configuration (default)
+- `zai` - Route Main Chat + Task tool to Z.ai for cost savings
+- `max` or `claude` - Route Main Chat + Task tool to Anthropic for quality
+
+**What This Does:**
+
+`/switch-api zai`:
+- Adds env vars to `.claude/settings.json`
+- Main Chat + Task() agents use Z.ai
+- Cost: $0.50/1M tokens (97% savings)
+- No login required
 
-Execute API switch using bash script:
+`/switch-api max`:
+- Removes env vars from `.claude/settings.json`
+- Main Chat + Task() agents use Anthropic
+- Cost: $15/1M tokens (or $0 with unlimited plan)
+- **Requires** running `claude login`
 
+**Combined Architecture:**
+```
+Main Chat (Anthropic or Z.ai - your choice)
+  ↓
+Task() → Coordinator (uses Main Chat provider)
+  ↓
+CLI spawn → Workers (always Z.ai from .env)
+```
+
+**Execute:**
 ```bash
 bash scripts/switch-api.sh {{args}}
 ```
+
+**Examples:**
+```bash
+/switch-api          # Show current routing
+/switch-api zai      # Cost-optimize Main Chat
+/switch-api max      # Quality-optimize Main Chat (requires re-login)
+```