agentic-qe 3.7.16 → 3.7.18

package/.claude/agents/v3/v3-queen-coordinator.md

@@ -1,98 +0,0 @@
----
-name: v3-queen-coordinator
-version: "3.0.0-alpha"
-updated: "2026-01-04"
-description: V3 Queen Coordinator for 15-agent concurrent swarm orchestration, GitHub issue management, and cross-agent coordination. Implements ADR-001 through ADR-010 with hierarchical mesh topology for 14-week v3 delivery.
-color: purple
-metadata:
-  v3_role: "orchestrator"
-  agent_id: 1
-  priority: "critical"
-  concurrency_limit: 1
-  phase: "all"
-hooks:
-  pre_execution: |
-    echo "👑 V3 Queen Coordinator starting 15-agent swarm orchestration..."
-
-    # Check intelligence status
-    npx agentic-flow@alpha hooks intelligence stats --json > /tmp/v3-intel.json 2>/dev/null || echo '{"initialized":false}' > /tmp/v3-intel.json
-    echo "🧠 RuVector: $(cat /tmp/v3-intel.json | jq -r '.initialized // false')"
-
-    # GitHub integration check
-    if command -v gh &> /dev/null; then
-      echo "🐙 GitHub CLI available"
-      gh auth status &>/dev/null && echo "✅ Authenticated" || echo "⚠️ Auth needed"
-    fi
-
-    # Initialize v3 coordination
-    echo "🎯 Mission: ADR-001 to ADR-010 implementation"
-    echo "📊 Targets: 2.49x-7.47x performance, 150x search, 50-75% memory reduction"
-
-  post_execution: |
-    echo "👑 V3 Queen coordination complete"
-
-    # Store coordination patterns
-    npx agentic-flow@alpha memory store-pattern \
-      --session-id "v3-queen-$(date +%s)" \
-      --task "V3 Orchestration: $TASK" \
-      --agent "v3-queen-coordinator" \
-      --status "completed" 2>/dev/null || true
----
-
-# V3 Queen Coordinator
-
-**🎯 15-Agent Swarm Orchestrator for Claude-Flow v3 Complete Reimagining**
-
-## Core Mission
-
-Lead the hierarchical mesh coordination of 15 specialized agents to implement all 10 ADRs (Architecture Decision Records) within 14-week timeline, achieving 2.49x-7.47x performance improvements.
-
-## Agent Topology
-
-```
-                    👑 QUEEN COORDINATOR
-                         (Agent #1)
-                             │
-        ┌────────────────────┼────────────────────┐
-        │                   │                    │
-   🛡️ SECURITY         🧠 CORE              🔗 INTEGRATION
-   (Agents #2-4)       (Agents #5-9)        (Agents #10-12)
-        │                   │                    │
-        └────────────────────┼────────────────────┘
-                             │
-        ┌────────────────────┼────────────────────┐
-        │                   │                    │
-   🧪 QUALITY          ⚡ PERFORMANCE        🚀 DEPLOYMENT
-   (Agent #13)         (Agent #14)          (Agent #15)
-```
-
-## Implementation Phases
-
-### Phase 1: Foundation (Week 1-2)
-- **Agents #2-4**: Security architecture, CVE remediation, security testing
-- **Agents #5-6**: Core architecture DDD design, type modernization
-
-### Phase 2: Core Systems (Week 3-6)
-- **Agent #7**: Memory unification (AgentDB 150x improvement)
-- **Agent #8**: Swarm coordination (merge 4 systems)
-- **Agent #9**: MCP server optimization
-- **Agent #13**: TDD London School implementation
-
-### Phase 3: Integration (Week 7-10)
-- **Agent #10**: agentic-flow@alpha deep integration
-- **Agent #11**: CLI modernization + hooks
-- **Agent #12**: Neural/SONA integration
-- **Agent #14**: Performance benchmarking
-
-### Phase 4: Release (Week 11-14)
-- **Agent #15**: Deployment + v3.0.0 release
-- **All agents**: Final optimization and polish
-
-## Success Metrics
-
-- **Parallel Efficiency**: >85% agent utilization
-- **Performance**: 2.49x-7.47x Flash Attention speedup
-- **Search**: 150x-12,500x AgentDB improvement
-- **Memory**: 50-75% reduction
-- **Code**: <5,000 lines (vs 15,000+)
-- **Timeline**: 14-week delivery

package/.claude/agents/v3/v3-security-architect.md

@@ -1,174 +0,0 @@
----
-name: v3-security-architect
-version: "3.0.0-alpha"
-updated: "2026-01-04"
-description: V3 Security Architect responsible for complete security overhaul, threat modeling, and CVE remediation planning. Addresses critical vulnerabilities CVE-1, CVE-2, CVE-3 and implements secure-by-default patterns.
-color: red
-metadata:
-  v3_role: "architect"
-  agent_id: 2
-  priority: "critical"
-  domain: "security"
-  phase: "foundation"
-hooks:
-  pre_execution: |
-    echo "🛡️ V3 Security Architect initializing security overhaul..."
-
-    # Security audit preparation
-    echo "🔍 Security priorities:"
-    echo "  CVE-1: Vulnerable dependencies (@anthropic-ai/claude-code)"
-    echo "  CVE-2: Weak password hashing (SHA-256 → bcrypt)"
-    echo "  CVE-3: Hardcoded credentials → random generation"
-    echo "  HIGH-1: Command injection (shell:true → execFile)"
-    echo "  HIGH-2: Path traversal vulnerabilities"
-
-    # Check existing security tools
-    command -v npm &>/dev/null && echo "📦 npm audit available"
-
-    echo "🎯 Target: 90/100 security score, secure-by-default patterns"
-
-  post_execution: |
-    echo "🛡️ Security architecture review complete"
-
-    # Store security patterns
-    npx agentic-flow@alpha memory store-pattern \
-      --session-id "v3-security-$(date +%s)" \
-      --task "Security Architecture: $TASK" \
-      --agent "v3-security-architect" \
-      --priority "critical" 2>/dev/null || true
----
-
-# V3 Security Architect
-
-**🛡️ Complete Security Overhaul & Threat Modeling Specialist**
-
-## Critical Security Mission
-
-Design and implement comprehensive security architecture for v3, addressing all identified vulnerabilities and establishing secure-by-default patterns for the entire codebase.
-
-## Priority Security Fixes
-
-### **CVE-1: Vulnerable Dependencies**
-- **Issue**: Outdated @anthropic-ai/claude-code version
-- **Action**: Update to @anthropic-ai/claude-code@^2.0.31
-- **Files**: package.json
-- **Timeline**: Phase 1 Week 1
-
-### **CVE-2: Weak Password Hashing**
-- **Issue**: SHA-256 with hardcoded salt
-- **Action**: Implement bcrypt with 12 rounds
-- **Files**: api/auth-service.ts:580-588
-- **Timeline**: Phase 1 Week 1
-
-### **CVE-3: Hardcoded Default Credentials**
-- **Issue**: Default credentials in auth service
-- **Action**: Generate random credentials on installation
-- **Files**: api/auth-service.ts:602-643
-- **Timeline**: Phase 1 Week 1
-
-### **HIGH-1: Command Injection**
-- **Issue**: shell:true in spawn() calls
-- **Action**: Use execFile without shell
-- **Files**: Multiple spawn() locations
-- **Timeline**: Phase 1 Week 2
-
-### **HIGH-2: Path Traversal**
-- **Issue**: Unvalidated file paths
-- **Action**: Implement path.resolve() + prefix validation
-- **Files**: All file operation modules
-- **Timeline**: Phase 1 Week 2
-
-## Security Architecture Design
-
-### **Threat Model Domains**
-```
-┌─────────────────────────────────────────┐
-│              API BOUNDARY               │
-├─────────────────────────────────────────┤
-│  Input Validation & Authentication      │
-├─────────────────────────────────────────┤
-│           CORE SECURITY LAYER          │
-├─────────────────────────────────────────┤
-│  Agent Communication & Authorization    │
-├─────────────────────────────────────────┤
-│        STORAGE & PERSISTENCE           │
-└─────────────────────────────────────────┘
-```
-
-### **Security Boundaries**
-- **API Layer**: Input validation, rate limiting, CORS
-- **Authentication**: Token-based auth, session management
-- **Authorization**: Role-based access control (RBAC)
-- **Agent Communication**: Encrypted inter-agent messaging
-- **Data Protection**: Encryption at rest, secure key management
-
-## Secure Patterns Catalog
-
-### **Input Validation**
-```typescript
-// Zod-based validation
-const TaskInputSchema = z.object({
-  taskId: z.string().uuid(),
-  content: z.string().max(10000),
-  agentType: z.enum(['security', 'core', 'integration'])
-});
-```
-
-### **Path Sanitization**
-```typescript
-// Secure path handling
-function securePath(userPath: string, allowedPrefix: string): string {
-  const resolved = path.resolve(allowedPrefix, userPath);
-  if (!resolved.startsWith(path.resolve(allowedPrefix))) {
-    throw new SecurityError('Path traversal detected');
-  }
-  return resolved;
-}
-```
-
-### **Command Execution**
-```typescript
-// Safe command execution
-import { execFile } from 'child_process';
-
-// ❌ Dangerous: shell injection possible
-// exec(`git ${userInput}`, { shell: true });
-
-// ✅ Safe: no shell interpretation
-execFile('git', [userInput], { shell: false });
-```
-
-## Deliverables
-
-### **Phase 1 (Week 1-2)**
-- [ ] **SECURITY-ARCHITECTURE.md** - Complete threat model
-- [ ] **CVE-REMEDIATION-PLAN.md** - Detailed fix timeline
-- [ ] **SECURE-PATTERNS.md** - Reusable security patterns
-- [ ] **THREAT-MODEL.md** - Attack surface analysis
-
-### **Validation Criteria**
-- [ ] All CVEs addressed with tested fixes
-- [ ] npm audit shows 0 high/critical vulnerabilities
-- [ ] Security patterns documented and implemented
-- [ ] Threat model covers all v3 domains
-- [ ] Security testing framework established
-
-## Coordination with Security Team
-
-### **Security Implementer (Agent #3)**
-- Provide detailed implementation specifications
-- Review all security-critical code changes
-- Validate CVE remediation implementations
-
-### **Security Tester (Agent #4)**
-- Supply test specifications for security patterns
-- Define penetration testing requirements
-- Establish security regression test suite
-
-## Success Metrics
-
-- **Security Score**: 90/100 (npm audit + custom scans)
-- **CVE Resolution**: 100% of identified CVEs fixed
-- **Test Coverage**: >95% for security-critical code
-- **Documentation**: Complete security architecture docs
-- **Timeline**: All deliverables within Phase 1

package/.claude/commands/README.md

@@ -1,106 +0,0 @@
-# AQE Slash Commands
-
-This directory contains 8 slash command definitions for the Agentic Quality Engineering (AQE) Fleet.
-
-## Available Commands
-
-| Command | File | Purpose |
-|---------|------|---------|
-| `/aqe-generate` | `aqe-generate.md` | Generate comprehensive test suites using AI |
-| `/aqe-execute` | `aqe-execute.md` | Execute tests with parallel orchestration |
-| `/aqe-analyze` | `aqe-analyze.md` | Analyze coverage and identify gaps |
-| `/aqe-optimize` | `aqe-optimize.md` | Optimize test suites using sublinear algorithms |
-| `/aqe-report` | `aqe-report.md` | Generate quality engineering reports |
-| `/aqe-fleet-status` | `aqe-fleet-status.md` | Display fleet health and agent status |
-| `/aqe-chaos` | `aqe-chaos.md` | Run chaos testing scenarios |
-| `/aqe-benchmark` | `aqe-benchmark.md` | Run performance benchmarks |
-
-## Command Structure
-
-Each command file follows this structure:
-
-```markdown
----
-name: command-name
-description: Brief description
----
-
-# Command Name
-
-## Usage
-## Options
-## Examples
-## Integration with Claude Code
-## Agent Coordination
-## Memory Operations
-## Expected Outputs
-## Error Handling
-## Performance Characteristics
-## See Also
-```
-
-## Quick Start
-
-### Using Commands in Claude Code
-
-```javascript
-// Spawn agent using Claude Code's Task tool
-Task("Generate tests", "Create test suite for auth module", "qe-test-generator")
-
-// Execute command directly
-/aqe-generate src/services/auth-service.ts --coverage 95
-```
-
-### Command Chaining
-
-```bash
-# Complete QE workflow
-/aqe-generate src/services/user-service.ts
-/aqe-execute tests/unit/user-service.test.ts
-/aqe-analyze coverage --threshold 95
-/aqe-report summary
-```
-
-## Integration Features
-
-### Claude Flow Hooks
-All commands integrate with Claude Flow for coordination:
-- Pre-task hooks for initialization
-- Post-task hooks for results storage
-- Memory operations for state sharing
-- Neural pattern training from outcomes
-
-### Agent Coordination
-Commands spawn specialized QE agents:
-- **qe-test-generator**: Test generation
-- **qe-test-executor**: Test execution
-- **qe-coverage-analyzer**: Coverage analysis
-- **qe-quality-gate**: Quality validation
-- **qe-performance-tester**: Performance testing
-- **qe-security-scanner**: Security scanning
-
-### Memory Keys
-Commands use structured memory keys:
-- `aqe/test-generation/*` - Test generation results
-- `aqe/execution/*` - Test execution data
-- `aqe/coverage/*` - Coverage metrics
-- `aqe/optimization/*` - Optimization results
-- `aqe/coordination/*` - Fleet coordination
-
-## Documentation
-
-- **Specification**: `/docs/QE-SLASH-COMMANDS-SPECIFICATION.md`
-- **Implementation Guide**: `/docs/QE-COMMANDS-IMPLEMENTATION-GUIDE.md`
-- **Quick Reference**: `/docs/QE-COMMANDS-QUICK-REFERENCE.md`
-
-## Status
-
-✅ All 8 commands implemented and documented
-✅ Claude Code integration patterns defined
-✅ Agent coordination protocols specified
-✅ Memory operations documented
-✅ Example workflows provided
-
-**Version:** 2.0.0
-**Date:** 2025-09-30
-**Maintainer:** AQE Fleet Team

package/.claude/commands/agents/README.md

@@ -1,10 +0,0 @@
-# Agents Commands
-
-Commands for agents operations in Claude Flow.
-
-## Available Commands
-
-- [agent-types](./agent-types.md)
-- [agent-capabilities](./agent-capabilities.md)
-- [agent-coordination](./agent-coordination.md)
-- [agent-spawning](./agent-spawning.md)

package/.claude/commands/agents/agent-capabilities.md

@@ -1,21 +0,0 @@
-# agent-capabilities
-
-Matrix of agent capabilities and their specializations.
-
-## Capability Matrix
-
-| Agent Type | Primary Skills | Best For |
-|------------|---------------|----------|
-| coder | Implementation, debugging | Feature development |
-| researcher | Analysis, synthesis | Requirements gathering |
-| tester | Testing, validation | Quality assurance |
-| architect | Design, planning | System architecture |
-
-## Querying Capabilities
-```bash
-# List all capabilities
-npx claude-flow agents capabilities
-
-# For specific agent
-npx claude-flow agents capabilities --type coder
-```

package/.claude/commands/agents/agent-coordination.md

@@ -1,28 +0,0 @@
-# agent-coordination
-
-Coordination patterns for multi-agent collaboration.
-
-## Coordination Patterns
-
-### Hierarchical
-Queen-led with worker specialization
-```bash
-npx claude-flow swarm init --topology hierarchical
-```
-
-### Mesh
-Peer-to-peer collaboration
-```bash
-npx claude-flow swarm init --topology mesh
-```
-
-### Adaptive
-Dynamic topology based on workload
-```bash
-npx claude-flow swarm init --topology adaptive
-```
-
-## Best Practices
-- Use hierarchical for complex projects
-- Use mesh for research tasks
-- Use adaptive for unknown workloads

package/.claude/commands/agents/agent-spawning.md

@@ -1,28 +0,0 @@
-# agent-spawning
-
-Guide to spawning agents with Claude Code's Task tool.
-
-## Using Claude Code's Task Tool
-
-**CRITICAL**: Always use Claude Code's Task tool for actual agent execution:
-
-```javascript
-// Spawn ALL agents in ONE message
-Task("Researcher", "Analyze requirements...", "researcher")
-Task("Coder", "Implement features...", "coder")
-Task("Tester", "Create tests...", "tester")
-```
-
-## MCP Coordination Setup (Optional)
-
-MCP tools are ONLY for coordination:
-```javascript
-mcp__claude-flow__swarm_init { topology: "mesh" }
-mcp__claude-flow__agent_spawn { type: "researcher" }
-```
-
-## Best Practices
-1. Always spawn agents concurrently
-2. Use Task tool for execution
-3. MCP only for coordination
-4. Batch all operations

package/.claude/commands/agents/agent-types.md

@@ -1,26 +0,0 @@
-# agent-types
-
-Complete guide to all 54 available agent types in Claude Flow.
-
-## Core Development Agents
-- `coder` - Implementation specialist
-- `reviewer` - Code quality assurance
-- `tester` - Test creation and validation
-- `planner` - Strategic planning
-- `researcher` - Information gathering
-
-## Swarm Coordination Agents
-- `hierarchical-coordinator` - Queen-led coordination
-- `mesh-coordinator` - Peer-to-peer networks
-- `adaptive-coordinator` - Dynamic topology
-
-## Specialized Agents
-- `backend-dev` - API development
-- `mobile-dev` - React Native development
-- `ml-developer` - Machine learning
-- `system-architect` - High-level design
-
-For full list and details:
-```bash
-npx claude-flow agents list
-```

package/.claude/commands/coordination/README.md

@@ -1,9 +0,0 @@
-# Coordination Commands
-
-Commands for coordination operations in Claude Flow.
-
-## Available Commands
-
-- [swarm-init](./swarm-init.md)
-- [agent-spawn](./agent-spawn.md)
-- [task-orchestrate](./task-orchestrate.md)

package/.claude/commands/coordination/agent-spawn.md

@@ -1,25 +0,0 @@
-# agent-spawn
-
-Spawn a new agent in the current swarm.
-
-## Usage
-```bash
-npx claude-flow agent spawn [options]
-```
-
-## Options
-- `--type <type>` - Agent type (coder, researcher, analyst, tester, coordinator)
-- `--name <name>` - Custom agent name
-- `--skills <list>` - Specific skills (comma-separated)
-
-## Examples
-```bash
-# Spawn coder agent
-npx claude-flow agent spawn --type coder
-
-# With custom name
-npx claude-flow agent spawn --type researcher --name "API Expert"
-
-# With specific skills
-npx claude-flow agent spawn --type coder --skills "python,fastapi,testing"
-```

package/.claude/commands/coordination/init.md

@@ -1,44 +0,0 @@
-# Initialize Coordination Framework
-
-## 🎯 Key Principle
-**This tool coordinates Claude Code's actions. It does NOT write code or create content.**
-
-## MCP Tool Usage in Claude Code
-
-**Tool:** `mcp__claude-flow__swarm_init`
-
-## Parameters
-```json
-{"topology": "mesh", "maxAgents": 5, "strategy": "balanced"}
-```
-
-## Description
-Set up a coordination topology to guide Claude Code's approach to complex tasks
-
-## Details
-This tool creates a coordination framework that helps Claude Code:
-- Break down complex problems systematically
-- Approach tasks from multiple perspectives
-- Maintain consistency across large projects
-- Work more efficiently through structured coordination
-
-Remember: This does NOT create actual coding agents. It creates a coordination pattern for Claude Code to follow.
-
-## Example Usage
-
-**In Claude Code:**
-1. Use the tool: `mcp__claude-flow__swarm_init`
-2. With parameters: `{"topology": "mesh", "maxAgents": 5, "strategy": "balanced"}`
-3. Claude Code then executes the coordinated plan using its native tools
-
-## Important Reminders
-- ✅ This tool provides coordination and structure
-- ✅ Claude Code performs all actual implementation
-- ❌ The tool does NOT write code
-- ❌ The tool does NOT access files directly
-- ❌ The tool does NOT execute commands
-
-## See Also
-- Main documentation: /claude.md
-- Other commands in this category
-- Workflow examples in /workflows/

package/.claude/commands/coordination/orchestrate.md

@@ -1,43 +0,0 @@
-# Coordinate Task Execution
-
-## 🎯 Key Principle
-**This tool coordinates Claude Code's actions. It does NOT write code or create content.**
-
-## MCP Tool Usage in Claude Code
-
-**Tool:** `mcp__claude-flow__task_orchestrate`
-
-## Parameters
-```json
-{"task": "Implement authentication system", "strategy": "parallel", "priority": "high"}
-```
-
-## Description
-Break down and coordinate complex tasks for systematic execution by Claude Code
-
-## Details
-Orchestration strategies:
-- **parallel**: Claude Code works on independent components simultaneously
-- **sequential**: Step-by-step execution for dependent tasks
-- **adaptive**: Dynamically adjusts based on task complexity
-
-The orchestrator creates a plan that Claude Code follows using its native tools.
-
-## Example Usage
-
-**In Claude Code:**
-1. Use the tool: `mcp__claude-flow__task_orchestrate`
-2. With parameters: `{"task": "Implement authentication system", "strategy": "parallel", "priority": "high"}`
-3. Claude Code then executes the coordinated plan using its native tools
-
-## Important Reminders
-- ✅ This tool provides coordination and structure
-- ✅ Claude Code performs all actual implementation
-- ❌ The tool does NOT write code
-- ❌ The tool does NOT access files directly
-- ❌ The tool does NOT execute commands
-
-## See Also
-- Main documentation: /claude.md
-- Other commands in this category
-- Workflow examples in /workflows/

package/.claude/commands/coordination/spawn.md

@@ -1,45 +0,0 @@
-# Create Cognitive Patterns
-
-## 🎯 Key Principle
-**This tool coordinates Claude Code's actions. It does NOT write code or create content.**
-
-## MCP Tool Usage in Claude Code
-
-**Tool:** `mcp__claude-flow__agent_spawn`
-
-## Parameters
-```json
-{"type": "researcher", "name": "Literature Analysis", "capabilities": ["deep-analysis"]}
-```
-
-## Description
-Define cognitive patterns that represent different approaches Claude Code can take
-
-## Details
-Agent types represent thinking patterns, not actual coders:
-- **researcher**: Systematic exploration approach
-- **coder**: Implementation-focused thinking
-- **analyst**: Data-driven decision making
-- **architect**: Big-picture system design
-- **reviewer**: Quality and consistency checking
-
-These patterns guide how Claude Code approaches different aspects of your task.
-
-## Example Usage
-
-**In Claude Code:**
-1. Use the tool: `mcp__claude-flow__agent_spawn`
-2. With parameters: `{"type": "researcher", "name": "Literature Analysis", "capabilities": ["deep-analysis"]}`
-3. Claude Code then executes the coordinated plan using its native tools
-
-## Important Reminders
-- ✅ This tool provides coordination and structure
-- ✅ Claude Code performs all actual implementation
-- ❌ The tool does NOT write code
-- ❌ The tool does NOT access files directly
-- ❌ The tool does NOT execute commands
-
-## See Also
-- Main documentation: /claude.md
-- Other commands in this category
-- Workflow examples in /workflows/