claude-flow-novice 2.6.0 → 2.9.0

package/.claude/agents/{testing → cfn-dev-team/testers}/e2e/playwright-agent.md

@@ -4,6 +4,7 @@ description: |
   Automated end-to-end testing agent for web portal testing using Playwright.
   MUST BE USED for comprehensive web interface validation.
   ALWAYS include cross-browser, performance, and integration testing.
+  keywords: ["end-to-end-testing", "web-portal-validation", "cross-browser-testing", "playwright-automation", "performance-benchmarking", "integration-testing", "web-quality-assurance"]
 tools: [Read, Write, Edit, Bash, Glob, Grep]
 model: haiku
 color: blue
@@ -135,30 +136,10 @@ 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 \
+./.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
 ```
 
-### Step 4: Enter Waiting Mode (for potential iteration)
-```bash
-./.claude/skills/redis-coordination/invoke-waiting-mode.sh enter \
-  --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., "playwright-agent-1", "reviewer-2")
-- Confidence: Your self-assessment score (0.0-1.0)
-
-See: `.claude/skills/redis-coordination/SKILL.md` for full protocol details

package/.claude/agents/{testing → cfn-dev-team/testers}/interaction-tester.md

@@ -9,6 +9,7 @@ tools: [Read, Write, Edit, Bash, Glob, Grep, TodoWrite]
 model: haiku
 color: cyan
 type: specialist
+keywords: [interaction testing, integration tests, e2e, UI testing, accessibility, user flows, WCAG compliance, component testing]
 validation_hooks:
   - agent-template-validator
   - cfn-loop-memory-validator
@@ -139,30 +140,10 @@ 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 \
+./.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
 ```
 
-### Step 4: Enter Waiting Mode (for potential iteration)
-```bash
-./.claude/skills/redis-coordination/invoke-waiting-mode.sh enter \
-  --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., "interaction-tester-1", "reviewer-2")
-- Confidence: Your self-assessment score (0.0-1.0)
-
-See: `.claude/skills/redis-coordination/SKILL.md` for full protocol details

package/.claude/agents/{testing → cfn-dev-team/testers}/playwright-tester.md

@@ -3,7 +3,7 @@ name: playwright-tester
 description: |
   MUST BE USED for end-to-end browser testing with Playwright.
   Automate UI workflows, validate user interactions across browsers.
-  Keywords - playwright, E2E testing, browser automation, cross-browser testing
+  keywords: ["playwright-testing", "end-to-end-automation", "browser-validation", "ui-workflow-testing", "cross-browser-compatibility", "test-infrastructure", "quality-assurance"]
 tools: [Read, Write, Edit, Bash, Grep, Glob, TodoWrite]
 model: haiku
 color: cyan

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

@@ -0,0 +1,139 @@
+# Comprehensive Tester Agent Profile
+
+## Core Responsibilities
+- Design and execute comprehensive test strategies
+- Validate functional and non-functional requirements
+- Identify and document edge cases
+- Ensure software quality and reliability
+- Create automated test suites
+
+## Validation Requirements
+
+### Browser & Application Testing
+**If MCP browser tools available**:
+- Perform end-to-end (E2E) testing
+- Navigate through all application routes
+- Simulate complex user interaction scenarios
+- Take snapshots of key application states
+- Validate responsive design across devices
+- Check console for runtime errors
+- Analyze network request behavior
+- Performance profiling
+- Cross-browser compatibility testing
+
+**Playwright/Automation Testing**:
+- Create comprehensive test scripts
+- Simulate user journeys
+- Test error handling paths
+- Verify state management
+- Capture runtime metrics
+
+**Fallback Testing Strategy**:
+1. When MCP tools unavailable:
+   - Request detailed implementation description
+   - Ask for manual test scenario documentation
+   - Create manual test scripts using Bash/curl
+2. Do NOT certify implementation without thorough testing
+3. Explicitly document testing limitations
+
+### Comprehensive Test Coverage
+
+**Test Dimensions**:
+1. **Functional Testing**
+   - Core feature validation
+   - Input validation
+   - Error handling
+   - Business logic verification
+
+2. **Performance Testing**
+   - Response time measurements
+   - Resource utilization
+   - Load testing
+   - Stress testing
+
+3. **Security Testing**
+   - Vulnerability scanning
+   - Authentication/Authorization tests
+   - Data validation
+   - Input sanitization checks
+
+4. **Compatibility Testing**
+   - Browser compatibility
+   - Device responsiveness
+   - OS-level testing
+
+5. **Usability Testing**
+   - User interaction flows
+   - Accessibility checks
+   - UI/UX consistency
+
+### MCP Browser Tools Reference
+- mcp__playwright__e2e_testing
+- mcp__playwright__browser_snapshot
+- mcp__chrome-devtools__performance_profile
+- mcp__chrome-devtools__cross_browser_check
+- mcp__playwright__user_journey_simulation
+
+## Testing Methodology
+```markdown
+### Test Plan Template
+1. Identify Test Scenarios
+2. Design Test Cases
+3. Prepare Test Data
+4. Execute Tests
+5. Log Results
+6. Report Findings
+```
+
+## Confidence Assessment Protocol
+- Comprehensive testing is multi-dimensional
+- MUST validate functional and non-functional aspects
+- Use browser automation and testing tools when available
+- Explicitly document testing methodology
+- Provide clear, quantifiable test results
+
+## Reporting Requirements
+```markdown
+## Test Execution Report
+- **Total Test Cases**: N
+- **Passed**: X
+- **Failed**: Y
+- **Confidence Score**: 0.0-1.0
+- **Critical Issues**: [List blocking problems]
+- **Warnings**: [Potential improvement areas]
+- **Test Environment**: [Browsers, Devices]
+- **Tools Used**: [MCP/Manual testing tools]
+```
+
+## Constraints
+- NEVER report >0.80 confidence without comprehensive testing
+- Always provide detailed test results
+- Clearly document testing limitations
+- Highlight both passed and failed test scenarios
+
+## Success Criteria
+- 100% critical path coverage
+- Minimum 85% overall test coverage
+- Zero critical test failures
+- Comprehensive test documentation
+- Confidence score ≥ 0.85
+
+## Escalation Protocol
+1. If significant test failures detected
+2. If critical scenarios cannot be tested
+3. If confidence cannot reach 0.85
+   - Escalate to development team
+   - Request additional test environment setup
+   - Provide detailed improvement recommendations
+
+## Collaboration Modes
+- **With Developers**: Provide specific testing feedback
+- **With Product Owner**: Validate requirements coverage
+- **With Security Team**: Comprehensive security testing
+- **Solo**: End-to-end testing and reporting
+
+## Test Environment Configuration
+- Maintain consistent, reproducible test environments
+- Use containerization for test isolation
+- Implement automated test setup and teardown
+

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

@@ -0,0 +1,49 @@
+---
+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"]
+tools: [Read, Write, Edit, Bash, Grep, Glob, TodoWrite]
+model: haiku
+color: yellow
+type: specialist
+acl_level: 3
+
+validation_hooks:
+  - agent-template-validator
+  - cfn-loop-memory-validator
+  - test-coverage-validator
+
+lifecycle:
+  pre_task: |
+    sqlite-cli exec "INSERT INTO agents (id, type, status, spawned_at)
+                     VALUES ('${AGENT_ID}', 'unit-tdd-london-swarm', 'active', CURRENT_TIMESTAMP)"
+  post_task: |
+    sqlite-cli exec "UPDATE agents
+                     SET status = 'completed', completed_at = CURRENT_TIMESTAMP
+                     WHERE id = '${AGENT_ID}'"
+---
+**Key Insight**: The London School emphasizes object collaboration over internal state. Focus on interactions, define clear contracts, and verify behavior through precise mock expectations.
+
+## CFN Loop Redis Completion Protocol
+
+When participating in CFN Loop workflows, agents MUST follow this protocol:
+
+### Step 1: Complete Work
+Execute assigned task (unit test implementation, test suite development, interaction verification)
+
+### Step 2: Signal Completion
+```bash
+redis-cli lpush "swarm:${TASK_ID}:${AGENT_ID}:done" "complete"
+```
+
+### Step 3: Report Confidence Score
+```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
+```

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

@@ -0,0 +1,33 @@
+---
+name: validation-production-validator
+description: |
+  MUST BE USED for final validation of production deployments.
+  Ensure system reliability, user safety, and organizational compliance.
+keywords: ["production-validation", "deployment-readiness", "system-reliability", "compliance-verification", "final-gate-check", "release-assurance", "safety-validation"]
+tools: [Read, Bash, Grep, Glob, TodoWrite]
+model: claude-sonnet-4
+---
+
+Remember: Production validation ensures system reliability, user safety, and organizational compliance.
+
+## CFN Loop Redis Completion Protocol
+
+When participating in CFN Loop workflows, agents MUST follow this protocol:
+
+### Step 1: Complete Work
+Execute assigned task (validation, readiness assessment, deployment checks)
+
+### Step 2: Signal Completion
+```bash
+redis-cli lpush "swarm:${TASK_ID}:${AGENT_ID}:done" "complete"
+```
+
+### Step 3: Report Confidence Score
+```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
+```
+

package/.claude/commands/{CFN_COORDINATOR_PARAMETERS.md → cfn/CFN_COORDINATOR_PARAMETERS.md}

@@ -19,7 +19,7 @@ This document defines the structured parameter specification for CFN Loop coordi
 ```
 /cfn-loop "task"
   ↓
-Main Chat spawns ONE agent: cost-savings-cfn-loop-coordinator
+Main Chat spawns ONE agent: cfn-v3-coordinator
   ↓
 Coordinator runs orchestrate-cfn-loop.sh internally
   ↓
@@ -202,7 +202,7 @@ Product Owner: product-owner
 **Loop 3 (Implementation):**
 - `researcher` - Requirement analysis, research
 - `backend-dev` - Backend implementation
-- `frontend-dev` - Frontend implementation (if needed)
+- `react-frontend-engineer` - Frontend implementation (if needed)
 - `devops` - Infrastructure, deployment
 
 **Loop 2 (Validation):**
@@ -222,7 +222,7 @@ Product Owner: product-owner
 
 ```bash
 1. INVOKE ORCHESTRATOR:
-   ./.claude/skills/redis-coordination/orchestrate-cfn-loop.sh \
+   ./.claude/skills/cfn-cfn-cfn-orchestration/orchestrate.sh \
      --task-id "${taskId}" \
      --mode ${mode} \
      --loop3-agents "${loop3Agents.join(',')}" \
@@ -232,8 +232,8 @@ Product Owner: product-owner
 
 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}
+   - Query metrics: ./.claude/skills/cfn-cfn-web-portal/invoke-portal-metrics.sh
+   - Track events: ./.claude/skills/cfn-cfn-web-portal/invoke-portal-events.sh --phase ${phaseName}
 
 3. REPORT RESULTS:
    Return structured result to Main Chat:
@@ -406,19 +406,19 @@ Epic-Level Acceptance Criteria:
 
 ```bash
 # Start web portal (if not running)
-./.claude/skills/web-portal/invoke-portal-start.sh
+./.claude/skills/cfn-cfn-web-portal/invoke-portal-start.sh
 
 # View all active agents
-./.claude/skills/web-portal/invoke-portal-agents.sh --status active
+./.claude/skills/cfn-cfn-web-portal/invoke-portal-agents.sh --status active
 
 # Track phase events
-./.claude/skills/web-portal/invoke-portal-events.sh --phase ${PHASE_NAME}
+./.claude/skills/cfn-cfn-web-portal/invoke-portal-events.sh --phase ${PHASE_NAME}
 
 # Get consensus metrics
-./.claude/skills/web-portal/invoke-portal-metrics.sh --view consensus
+./.claude/skills/cfn-cfn-web-portal/invoke-portal-metrics.sh --view consensus
 
 # Dashboard summary
-./.claude/skills/web-portal/invoke-portal-dashboard.sh
+./.claude/skills/cfn-cfn-web-portal/invoke-portal-dashboard.sh
 ```
 
 **Web UI:** http://localhost:3000
@@ -435,7 +435,7 @@ Epic-Level Acceptance Criteria:
 ### Example 1: MVP Mode Single Task
 
 ```javascript
-Task("cost-savings-cfn-loop-coordinator", `
+Task("cfn-v3-coordinator", `
   CFN LOOP EXECUTION - STRUCTURED PARAMETERS
 
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
@@ -488,7 +488,7 @@ Task("cost-savings-cfn-loop-coordinator", `
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
   1. INVOKE ORCHESTRATOR:
-     ./.claude/skills/redis-coordination/orchestrate-cfn-loop.sh \\
+     ./.claude/skills/cfn-cfn-cfn-orchestration/orchestrate.sh \\
        --task-id "cfn-mvp-registration-1729350000" \\
        --mode mvp \\
        --loop3-agents "backend-dev" \\
@@ -498,7 +498,7 @@ Task("cost-savings-cfn-loop-coordinator", `
 
   2. MONITOR PROGRESS:
      - Web portal: http://localhost:3000
-     - CLI: ./.claude/skills/web-portal/invoke-portal-agents.sh
+     - CLI: ./.claude/skills/cfn-cfn-web-portal/invoke-portal-agents.sh
 
   3. REPORT RESULTS:
      {
@@ -517,13 +517,13 @@ Task("cost-savings-cfn-loop-coordinator", `
   - LET orchestrator handle CLI spawning
   - USE Redis BLPOP for dependencies
   - RETURN structured result
-`, "cost-savings-cfn-loop-coordinator")
+`, "cfn-v3-coordinator")
 ```
 
 ### Example 2: Enterprise Mode Multi-Phase Epic
 
 ```javascript
-Task("cost-savings-cfn-loop-coordinator", `
+Task("cfn-v3-coordinator", `
   CFN LOOP EPIC EXECUTION - MULTI-PHASE
 
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
@@ -585,10 +585,10 @@ Task("cost-savings-cfn-loop-coordinator", `
   1. CHECK DEPENDENCIES
   2. STORE SCOPE BOUNDARIES (memory)
   3. INVOKE ORCHESTRATOR:
-     ./.claude/skills/redis-coordination/orchestrate-cfn-loop.sh \\
+     ./.claude/skills/cfn-cfn-cfn-orchestration/orchestrate.sh \\
        --task-id "phase-X-$(date +%s)" \\
        --mode enterprise \\
-       --loop3-agents "backend-dev,frontend-dev,devops,security-specialist,researcher" \\
+       --loop3-agents "backend-dev,react-frontend-engineer,devops,security-specialist,researcher" \\
        --loop2-agents "reviewer,architect,tester,security-specialist,performance-analyst" \\
        --product-owner "product-owner" \\
        --max-iterations 15
@@ -600,7 +600,7 @@ Task("cost-savings-cfn-loop-coordinator", `
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
   Web Portal: http://localhost:3000
-  Per-Phase Monitoring: ./.claude/skills/web-portal/invoke-portal-events.sh --phase phase-X
+  Per-Phase Monitoring: ./.claude/skills/cfn-cfn-web-portal/invoke-portal-events.sh --phase phase-X
 
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
   FINAL EPIC REPORT
@@ -616,7 +616,7 @@ Task("cost-savings-cfn-loop-coordinator", `
   - AUTO-TRANSITION between phases
   - DEFER out-of-scope items
   - RETURN epic summary
-`, "cost-savings-cfn-loop-coordinator")
+`, "cfn-v3-coordinator")
 ```
 
 ---
@@ -647,9 +647,9 @@ Task("cost-savings-cfn-loop-coordinator", `
 
 ## Related Documentation
 
-- **Redis Coordination Skill:** `.claude/skills/redis-coordination/SKILL.md`
-- **Web Portal Skill:** `.claude/skills/web-portal/SKILL.md`
-- **CFN Loop Validation Skill:** `.claude/skills/cfn-loop-validation/SKILL.md`
+- **Redis Coordination Skill:** `.claude/skills/cfn-cfn-redis-coordination/SKILL.md`
+- **Web Portal Skill:** `.claude/skills/cfn-cfn-web-portal/SKILL.md`
+- **CFN Loop Validation Skill:** `.claude/skills/cfn-cfn-cfn-loop-validation/SKILL.md`
 - **Slash Commands:** `.claude/commands/cfn-loop*.md`
 
 ---

package/.claude/commands/{cfn-loop-epic.md → cfn/cfn-loop-epic.md}

@@ -97,7 +97,7 @@ The coordinator uses CLI spawning per phase and provides full visibility via web
 ### Epic Pattern (SINGLE COORDINATOR FOR ALL PHASES)
 
 ```javascript
-Task("cost-savings-cfn-loop-coordinator", `
+Task("cfn-v3-coordinator", `
   CFN LOOP EPIC EXECUTION - MULTI-PHASE
 
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
@@ -216,7 +216,7 @@ Task("cost-savings-cfn-loop-coordinator", `
      LOOP3_AGENTS="analyst,architect"
      LOOP2_AGENTS="reviewer,architect"
 
-     ./.claude/skills/redis-coordination/orchestrate-cfn-loop.sh \
+     ./.claude/skills/cfn-cfn-cfn-orchestration/orchestrate.sh \
        --task-id "$TASK_ID" \
        --mode "$MODE" \
        --loop3-agents "$LOOP3_AGENTS" \
@@ -247,9 +247,9 @@ Task("cost-savings-cfn-loop-coordinator", `
   Web Portal: http://localhost:3000
 
   Per-Phase Monitoring:
-  - Agents: ./.claude/skills/web-portal/invoke-portal-agents.sh --swarm phase-${PHASE_ID}
-  - Events: ./.claude/skills/web-portal/invoke-portal-events.sh --phase phase-${PHASE_ID}
-  - Metrics: ./.claude/skills/web-portal/invoke-portal-metrics.sh
+  - Agents: ./.claude/skills/cfn-cfn-web-portal/invoke-portal-agents.sh --swarm phase-${PHASE_ID}
+  - Events: ./.claude/skills/cfn-cfn-web-portal/invoke-portal-events.sh --phase phase-${PHASE_ID}
+  - Metrics: ./.claude/skills/cfn-cfn-web-portal/invoke-portal-metrics.sh
 
   Epic Progress:
   - Query memory for phase results
@@ -293,7 +293,7 @@ Task("cost-savings-cfn-loop-coordinator", `
   - DEFER out-of-scope items to backlog
   - PUBLISH events per phase
   - RETURN epic summary when complete
-`, "cost-savings-cfn-loop-coordinator")
+`, "cfn-v3-coordinator")
 ```
 
 ### Coordinator Autonomous Multi-Phase Execution

package/.claude/commands/{cfn-loop-single.md → cfn/cfn-loop-single.md}

@@ -33,7 +33,7 @@ The coordinator uses CLI spawning (95-98% cost savings) and provides full visibi
 ### Step 1: Spawn Coordinator Agent (SINGLE AGENT PATTERN)
 
 ```javascript
-Task("cost-savings-cfn-loop-coordinator", `
+Task("cfn-v3-coordinator", `
   CFN LOOP SINGLE TASK EXECUTION
 
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
@@ -120,7 +120,7 @@ Task("cost-savings-cfn-loop-coordinator", `
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
   1. INVOKE ORCHESTRATOR:
-     ./.claude/skills/redis-coordination/orchestrate-cfn-loop.sh \\
+     ./.claude/skills/cfn-cfn-orchestration/orchestrate.sh \\
        --task-id "cfn-single-$(date +%s)" \\
        --mode standard \\
        --loop3-agents "researcher,backend-dev,devops" \\
@@ -130,8 +130,8 @@ Task("cost-savings-cfn-loop-coordinator", `
 
   2. MONITOR PROGRESS:
      - Web portal: http://localhost:3000
-     - CLI metrics: ./.claude/skills/web-portal/invoke-portal-agents.sh
-     - Event stream: ./.claude/skills/web-portal/invoke-portal-events.sh
+     - CLI metrics: ./.claude/skills/cfn-web-portal/invoke-portal-agents.sh
+     - Event stream: ./.claude/skills/cfn-web-portal/invoke-portal-events.sh
 
   3. REPORT STRUCTURED RESULT:
      {
@@ -155,7 +155,7 @@ Task("cost-savings-cfn-loop-coordinator", `
   - USE Redis BLPOP for dependencies
   - PUBLISH events to web-portal channel
   - RETURN structured result to Main Chat
-`, "cost-savings-cfn-loop-coordinator")
+`, "cfn-v3-coordinator")
 ```
 
 ### Step 2: Coordinator Autonomous Execution
@@ -182,16 +182,16 @@ The coordinator runs orchestrator script internally:
 **Monitor execution:**
 ```bash
 # Start web portal (if not running)
-./.claude/skills/web-portal/invoke-portal-start.sh
+./.claude/skills/cfn-web-portal/invoke-portal-start.sh
 
 # View agents
-./.claude/skills/web-portal/invoke-portal-agents.sh --status active
+./.claude/skills/cfn-web-portal/invoke-portal-agents.sh --status active
 
 # Track events
-./.claude/skills/web-portal/invoke-portal-events.sh --limit 50
+./.claude/skills/cfn-web-portal/invoke-portal-events.sh --limit 50
 
 # Get metrics
-./.claude/skills/web-portal/invoke-portal-metrics.sh
+./.claude/skills/cfn-web-portal/invoke-portal-metrics.sh
 ```
 
 **Web UI:** http://localhost:3000 (real-time updates)

package/.claude/commands/{cfn-loop-sprints.md → cfn/cfn-loop-sprints.md}

@@ -111,7 +111,7 @@ Task("CFN Loop Coordinator", `
 
   MANDATORY: Use orchestrator script for dependency enforcement.
 
-  ./.claude/skills/redis-coordination/orchestrate-cfn-loop.sh \
+  ./.claude/skills/cfn-cfn-orchestration/orchestrate.sh \
     --task-id "sprint-${sprintId}-$(date +%s)" \
     --mode standard \
     --loop3-agents "backend-dev,tester,security-specialist" \

package/.claude/commands/{cfn-loop.md → cfn/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
 
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
@@ -182,7 +182,7 @@ Task("cost-savings-cfn-loop-coordinator", `
      LOOP3_AGENTS="researcher,backend-dev,devops"
      LOOP2_AGENTS="reviewer,architect,tester,security-specialist"
 
-     ./.claude/skills/redis-coordination/orchestrate-cfn-loop.sh \
+     ./.claude/skills/cfn-cfn-orchestration/orchestrate.sh \
        --task-id "$TASK_ID" \
        --mode "$MODE" \
        --loop3-agents "$LOOP3_AGENTS" \
@@ -192,8 +192,8 @@ Task("cost-savings-cfn-loop-coordinator", `
 
   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 <phase-name>
+     - Query metrics: ./.claude/skills/cfn-web-portal/invoke-portal-metrics.sh
+     - Track events: ./.claude/skills/cfn-web-portal/invoke-portal-events.sh --phase <phase-name>
 
   3. REPORT RESULTS:
      Return structured result to Main Chat:
@@ -224,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
@@ -256,16 +256,16 @@ 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/cfn-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/cfn-web-portal/invoke-portal-events.sh --phase <phase-name>
 
 # Get consensus metrics
-./.claude/skills/web-portal/invoke-portal-metrics.sh --view consensus
+./.claude/skills/cfn-web-portal/invoke-portal-metrics.sh --view consensus
 
 # Dashboard summary
-./.claude/skills/web-portal/invoke-portal-dashboard.sh
+./.claude/skills/cfn-web-portal/invoke-portal-dashboard.sh
 ```
 
 **Web UI:**

package/.claude/commands/cfn/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/{cfn-optimize-agents.md → cfn/cfn-optimize-agents.md}

@@ -68,7 +68,7 @@ Specific agents with more parallel workers:
 ## What It Does
 
 1. **Launches** a coordinator agent via Task tool to manage the optimization process
-2. **Discovers** all agent profiles in .claude/agents/ directory structure
+2. **Discovers** all agent profiles in .claude/agents/cfn-dev-team/ directory structure
 3. **Distributes** profiles evenly among parallel optimizers (zero overlap)
 4. **Coordinates** parallel work via Redis pub/sub messaging
 5. **Spawns** multiple cli-agent-optimizer agents via CLI with specific assignments