claude-flow-novice 2.18.12 → 2.18.14

package/.claude/skills/cfn-cerebras-coordinator/test-tdd-coordinator.sh

@@ -0,0 +1,250 @@
+#!/bin/bash
+set -euo pipefail
+
+# Test TDD Conversation Coordinator
+# Validates conversation memory and iterative refinement
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+COORDINATOR="$SCRIPT_DIR/tdd-conversation-coordinator.sh"
+
+# Test utilities
+source "$(dirname "$SCRIPT_DIR")/../../../tests/test-utils.sh" 2>/dev/null || {
+    # Fallback test utilities
+    log_step() { echo "[STEP] $*"; }
+    log_info() { echo "[INFO] $*"; }
+    log_error() { echo "[ERROR] $*" >&2; }
+    assert_success() { [[ $? -eq 0 ]] || { log_error "Command failed"; exit 1; }; }
+    assert_file_exists() { [[ -f "$1" ]] || { log_error "File not found: $1"; exit 1; }; }
+    assert_contains() { grep -q "$2" "$1" || { log_error "Pattern '$2' not found in $1"; exit 1; }; }
+}
+
+# Setup
+TEST_DIR="/tmp/test-tdd-coordinator-$$"
+mkdir -p "$TEST_DIR"
+
+cleanup() {
+    rm -rf "$TEST_DIR"
+}
+trap cleanup EXIT
+
+# Test configuration
+export ZAI_API_KEY="${ZAI_API_KEY:-test-key-placeholder}"
+export ZAI_BASE_URL="${ZAI_BASE_URL:-https://api.zai.ai/v1}"
+
+# === TEST 1: Argument Parsing ===
+test_argument_parsing() {
+    log_step "TEST 1: Argument parsing and validation"
+
+    # Test help
+    if "$COORDINATOR" --help 2>&1 | grep -q "Usage:"; then
+        log_info "Help text displays correctly"
+    else
+        log_error "Help text missing"
+        return 1
+    fi
+
+    # Test missing required arguments
+    local output
+    output=$("$COORDINATOR" 2>&1) || true
+    if echo "$output" | grep -q "Missing required"; then
+        log_info "Missing argument detection works"
+    else
+        log_error "Should reject missing arguments"
+        log_error "Got output: $output"
+        return 1
+    fi
+
+    log_info "Argument parsing: PASS"
+}
+
+# === TEST 2: Conversation Initialization ===
+test_conversation_init() {
+    log_step "TEST 2: Conversation file initialization"
+
+    # Create minimal test
+    local test_feature="Test feature"
+    local test_file="$TEST_DIR/test.ts"
+    local agent_id="test-agent-$$"
+
+    # Mock API key (won't actually call)
+    export ZAI_API_KEY="mock-key"
+
+    # We can't run full coordinator without API, but we can test argument parsing
+    local cmd="$COORDINATOR --agent-id $agent_id --feature \"$test_feature\" --file $test_file --test-command \"echo test\" --max-iterations 1 2>&1"
+
+    log_info "Would execute: $cmd"
+    log_info "Full execution requires valid ZAI_API_KEY"
+
+    log_info "Conversation initialization: SKIPPED (requires API)"
+}
+
+# === TEST 3: Test File Path Generation ===
+test_file_path_generation() {
+    log_step "TEST 3: Test file path generation logic"
+
+    # Test various file extensions
+    declare -A test_cases=(
+        ["src/auth.ts"]="src/auth.test.ts"
+        ["src/utils.js"]="src/utils.test.js"
+        ["src/validator.py"]="src/test_validator.py"
+        ["src/handler.go"]="src/handler_test.go"
+    )
+
+    local all_pass=true
+    for impl_file in "${!test_cases[@]}"; do
+        local expected="${test_cases[$impl_file]}"
+
+        # Extract logic from main script (simulate)
+        local test_file
+        case "${impl_file##*.}" in
+            ts|tsx)
+                test_file="${impl_file%.*}.test.ts"
+                ;;
+            js|jsx)
+                test_file="${impl_file%.*}.test.js"
+                ;;
+            py)
+                test_file="test_$(basename "$impl_file")"
+                test_file="$(dirname "$impl_file")/$test_file"
+                ;;
+            go)
+                test_file="${impl_file%.*}_test.go"
+                ;;
+            *)
+                test_file="${impl_file%.*}.test.${impl_file##*.}"
+                ;;
+        esac
+
+        if [[ "$test_file" == "$expected" ]]; then
+            log_info "$impl_file -> $test_file (OK)"
+        else
+            log_error "$impl_file -> $test_file (expected: $expected)"
+            all_pass=false
+        fi
+    done
+
+    if [[ "$all_pass" == "true" ]]; then
+        log_info "Test file path generation: PASS"
+    else
+        log_error "Test file path generation: FAIL"
+        return 1
+    fi
+}
+
+# === TEST 4: Conversation File Structure ===
+test_conversation_structure() {
+    log_step "TEST 4: Conversation JSON structure"
+
+    # Create a mock conversation file
+    local conv_file="$TEST_DIR/conversation.json"
+    local agent_id="test-agent"
+    local feature="Test feature"
+    local file_path="$TEST_DIR/test.ts"
+
+    cat > "$conv_file" <<EOF
+{
+  "messages": [
+    {
+      "role": "system",
+      "content": "You are a TDD expert.",
+      "timestamp": "$(date -Iseconds)"
+    }
+  ],
+  "metadata": {
+    "agent_id": "$agent_id",
+    "feature": "$feature",
+    "file_path": "$file_path",
+    "started_at": "$(date -Iseconds)",
+    "iterations": 0,
+    "phase": "init"
+  }
+}
+EOF
+
+    # Validate structure
+    assert_file_exists "$conv_file"
+
+    # Check required fields
+    if jq -e '.messages | type == "array"' "$conv_file" >/dev/null; then
+        log_info "messages array present"
+    else
+        log_error "messages array missing"
+        return 1
+    fi
+
+    if jq -e '.metadata.agent_id' "$conv_file" >/dev/null; then
+        log_info "metadata.agent_id present"
+    else
+        log_error "metadata.agent_id missing"
+        return 1
+    fi
+
+    if jq -e '.metadata.phase' "$conv_file" >/dev/null; then
+        log_info "metadata.phase present"
+    else
+        log_error "metadata.phase missing"
+        return 1
+    fi
+
+    log_info "Conversation structure: PASS"
+}
+
+# === TEST 5: Integration Test (Mock) ===
+test_integration_mock() {
+    log_step "TEST 5: Integration test with mock API"
+
+    log_info "Full integration test requires:"
+    log_info "  - Valid ZAI_API_KEY"
+    log_info "  - Test project with runnable tests"
+    log_info "  - RuVector index (optional)"
+    log_info ""
+    log_info "Example usage:"
+    log_info "  $COORDINATOR \\"
+    log_info "    --agent-id tdd-001 \\"
+    log_info "    --feature \"Email validator function\" \\"
+    log_info "    --file ./src/validators/email.ts \\"
+    log_info "    --test-command \"npm test email.test.ts\" \\"
+    log_info "    --context \"./src/types.ts\" \\"
+    log_info "    --max-iterations 3 \\"
+    log_info "    --verbose"
+
+    log_info "Integration test: SKIPPED (requires live API)"
+}
+
+# === RUN ALL TESTS ===
+main() {
+    echo "================================================"
+    echo "  TDD Conversation Coordinator - Test Suite"
+    echo "================================================"
+    echo
+
+    local failed=0
+
+    test_argument_parsing || failed=$((failed + 1))
+    echo
+
+    test_conversation_init || failed=$((failed + 1))
+    echo
+
+    test_file_path_generation || failed=$((failed + 1))
+    echo
+
+    test_conversation_structure || failed=$((failed + 1))
+    echo
+
+    test_integration_mock || failed=$((failed + 1))
+    echo
+
+    echo "================================================"
+    if [[ $failed -eq 0 ]]; then
+        echo "  All tests passed!"
+        echo "================================================"
+        exit 0
+    else
+        echo "  $failed test(s) failed"
+        echo "================================================"
+        exit 1
+    fi
+}
+
+main

package/.claude/skills/cfn-compilation-error-fixer/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cfn-compilation-error-fixer
-description: Two-phase compilation error fixer for Rust and TypeScript using Cerebras LLM bulk processing + dedicated agent cleanup
+description: "Two-phase compilation error fixer for Rust and TypeScript using Cerebras LLM bulk processing + dedicated agent cleanup. Use when you have 20+ compilation errors that need fast bulk reduction, or when errors are mostly mechanical (type mismatches, missing imports, syntax issues)."
 version: 2.0.0
 tags: [rust, typescript, compilation, cerebras, error-fixer, cfn]
 status: production

package/.claude/skills/cfn-compilation-error-fixer/lib/fixer/cerebras-gated-fixer-v2.ts

@@ -25,7 +25,7 @@ const CONFIG = {
   maxLayer1Retries: 3,  // Max retries when Layer 1 gates reject
   maxTokens: 4000,
   model: 'zai-glm-4.6',
-  projectPath: '/mnt/c/Users/masha/Documents/ourstories-v2/services/rust-services',
+  projectPath: process.env.RUST_PROJECT_PATH || '/mnt/c/Users/masha/Documents/ourstories-v2/services/rust-services',
   parallelLLMCalls: 10,
   enableLayer3: !process.argv.includes('--no-layer3'),
   enableClippy: !process.argv.includes('--no-clippy'),

package/.claude/skills/cfn-config/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cfn-config
-description: Configuration management and environment sanitization
+description: "Configuration management and environment sanitization. Use when you need to manage configuration files, validate environment variables, sanitize sensitive data, or update system settings across CFN Loop components."
 version: 1.0.0
 tags: [mega-skill, config, environment, sanitization]
 status: production

package/.claude/skills/cfn-dependency-management/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cfn-dependency-management
-description: Task dependency extraction and context ingestion
+description: "Task dependency extraction and context ingestion. Use when you need to parse task criteria, identify dependencies, generate execution order, or inject context for complex multi-step tasks."
 version: 1.1.0
 tags: [mega-skill, dependencies, extraction, ingestion, orchestration]
 status: production

package/.claude/skills/cfn-deployment-lifecycle/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cfn-deployment-lifecycle
-description: Skill deployment and promotion lifecycle management
+description: "Skill deployment and promotion lifecycle management. Use when transitioning skills from APPROVED to DEPLOYED status, or promoting skills from staging to production with SLA enforcement."
 version: 1.0.0
 tags: [mega-skill, deployment, promotion, lifecycle]
 status: production

package/.claude/skills/cfn-edit-safety/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cfn-edit-safety
-description: Pre-edit backup and post-edit validation for safe file modifications
+description: "Pre-edit backup and post-edit validation for safe file modifications. Use when you need to capture file state before edits, validate changes after modifications, revert files to previous state, or ensure edit safety with automatic backup and validation hooks."
 version: 1.0.0
 tags: [mega-skill, backup, hooks, validation, safety]
 status: production

package/.claude/skills/cfn-epic-creator/SKILL.md

@@ -0,0 +1,392 @@
+---
+name: cfn-epic-creator
+description: "Creates comprehensive epic definitions with sequential reviews from 6 key personas. Use when you need to analyze requirements from multiple perspectives and generate structured epic documentation with cost estimates and risk assessments."
+version: 1.0.0
+tags: [epic, creator, personas, analysis, cost-estimation, requirements]
+status: production
+---
+
+# CFN Epic Creator
+
+## Overview
+
+The cfn-epic-creator skill provides orchestration for creating comprehensive epic definitions through sequential reviews from six key personas: Product Owner, Architect, Security Specialist, Performance Specialist, Accessibility Advocate, and DevOps Engineer.
+
+## Usage
+
+### Basic Epic Creation
+
+```bash
+# Create epic with default settings
+./.claude/skills/cfn-epic-creator/invoke.sh "Build a customer-facing analytics dashboard"
+
+# Create epic with specific output file
+./.claude/skills/cfn-epic-creator/invoke.sh "Develop mobile banking app" \
+    --output=banking-epic.json
+
+# Create epic in enterprise mode
+./.claude/skills/cfn-epic-creator/invoke.sh "Implement AI-powered fraud detection" \
+    --mode=enterprise
+```
+
+### Advanced Usage
+
+```bash
+# Enterprise mode with DevOps enforcement
+./invoke.sh "Global supply chain management system" \
+    --mode=enterprise \
+    --enforce-devops \
+    --output=supply-chain-epic.json \
+    --verbose
+
+# MVP mode for rapid prototyping
+./invoke.sh "Simple proof-of-concept for AR furniture placement" \
+    --mode=mvp
+
+# Validate without creating file
+./invoke.sh "Complex multi-region deployment strategy" \
+    --validate-only \
+    --verbose
+```
+
+### Command Line Options
+
+- `<epic-description>`: Detailed description of the epic to be analyzed (required)
+- `-m, --mode <mode>`: Review thoroughness level
+  - `mvp`: Basic reviews, focus on critical items only (~60% fewer recommendations)
+  - `standard`: Full comprehensive reviews (default)
+  - `enterprise`: Deep dive with compliance and governance focus
+- `-e, --enforce-devops`: Make DevOps recommendations blocking instead of suggested
+- `-o, --output <path>`: Output JSON file path (default: auto-generated with timestamp)
+- `-v, --verbose`: Enable verbose logging
+- `--validate-only`: Validate generated epic JSON without creating file
+- `-h, --help`: Show help message
+
+## Supporting Scripts
+
+### validate-epic.sh
+
+Validates generated epic JSON structure and content.
+
+```bash
+# Basic validation
+./validate-epic.sh epic.json
+
+# Verbose validation with details
+./validate-epic.sh epic.json --verbose
+
+# Strict validation (treat warnings as errors)
+./validate-epic.sh epic.json --strict
+```
+
+Options:
+- `-v, --verbose`: Show detailed validation output
+- `-s, --strict`: Enable strict validation (fails on warnings)
+- `-h, --help`: Show help message
+
+### parse-personas.sh
+
+Extracts specific persona insights from generated epic JSON.
+
+```bash
+# Show all persona insights
+./parse-personas.sh epic.json
+
+# Extract specific persona
+./parse-personas.sh epic.json --persona=architect
+
+# Filter by recommendation type
+./parse-personas.sh epic.json --type=blocking
+
+# Export as markdown
+./parse-personas.sh epic.json --format=markdown --output=personas.md
+
+# Show counts only
+./parse-personas.sh epic.json --count
+```
+
+Options:
+- `-p, --persona <name>`: Filter by specific persona
+- `-t, --type <type>`: Filter by recommendation type (blocking/suggested)
+- `-r, --priority <prio>`: Filter by priority (critical/high/medium/low)
+- `-f, --format <fmt>`: Output format (text/json/markdown)
+- `-c, --count`: Show only counts per persona
+- `-s, --summary`: Show summarized insights only
+- `-o, --output <file>`: Write output to file
+
+### estimate-costs.sh
+
+Aggregates cost estimates from all personas in epic JSON.
+
+```bash
+# Show cost summary
+./estimate-costs.sh epic.json
+
+# Detailed breakdown by persona
+./estimate-costs.sh epic.json --format=detailed
+
+# Export as CSV
+./estimate-costs.sh epic.json --format=csv --output=costs.csv
+
+# Filter by blocking recommendations only
+./estimate-costs.sh epic.json --type=blocking
+
+# Sort by highest cost
+./estimate-costs.sh epic.json --sort-by=total
+```
+
+Options:
+- `-p, --persona <name>`: Show costs for specific persona only
+- `-t, --type <type>`: Filter by recommendation type (blocking/suggested)
+- `-r, --priority <prio>`: Filter by priority
+- `-f, --format <fmt>`: Output format (summary/detailed/csv/json)
+- `-c, --currency <curr>`: Currency symbol for display (default: $)
+- `-s, --sort-by <field>`: Sort personas by field (total/blocking/suggested/name)
+- `-o, --output <file>`: Write output to file
+
+## Output Structure
+
+The generated JSON follows this structure:
+
+```json
+{
+  "epic": {
+    "id": "EPIC-XXXXXX",
+    "title": "Extracted from description",
+    "description": "Full epic description",
+    "status": "in-review",
+    "priority": "high",
+    "estimatedDuration": "TBD",
+    "budget": "TBD",
+    "owner": "TBD",
+    "metadata": {
+      "createdAt": "2024-01-01T00:00:00.000Z",
+      "reviewMode": "standard|enterprise|mvp",
+      "devopsEnforced": true|false
+    },
+    "personas": [
+      {
+        "name": "product-owner",
+        "reviewOrder": 1,
+        "status": "completed",
+        "insights": [
+          "Strategic insight 1",
+          "Strategic insight 2"
+        ],
+        "recommendations": [
+          {
+            "id": "PO-001",
+            "title": "Recommendation title",
+            "type": "blocking|suggested",
+            "priority": "critical|high|medium|low",
+            "estimatedCost": "$X,XXX",
+            "description": "Detailed description"
+          }
+        ],
+        "costAnalysis": {
+          "category1": "$X,XXX",
+          "category2": "$X,XXX"
+        }
+      },
+      {
+        "name": "architect",
+        "reviewOrder": 2,
+        "...": "..."
+      },
+      {
+        "name": "security-specialist",
+        "reviewOrder": 3,
+        "...": "..."
+      },
+      {
+        "name": "performance-specialist",
+        "reviewOrder": 4,
+        "...": "..."
+      },
+      {
+        "name": "accessibility-advocate",
+        "reviewOrder": 5,
+        "...": "..."
+      },
+      {
+        "name": "devops-engineer",
+        "reviewOrder": 6,
+        "...": "..."
+      }
+    ],
+    "implementationRoadmap": [],
+    "totalCostBreakdown": {},
+    "riskAssessment": {}
+  }
+}
+```
+
+## Persona Review Order
+
+1. **Product Owner** - Business value, user stories, market fit
+2. **Architect** - System design, technology choices, scalability
+3. **Security Specialist** - Security posture, vulnerabilities, compliance
+4. **Performance Specialist** - Performance metrics, optimization, monitoring
+5. **Accessibility Advocate** - WCAG compliance, inclusive design
+6. **DevOps Engineer** - Deployment, operations, infrastructure
+
+## Integration with CFN Loop
+
+The epic creator integrates seamlessly with CFN Loop workflows:
+
+```bash
+# Using with CFN Loop
+/cfn-loop-task "Analyze epic for user authentication system" \
+  --agent epic-creator-v2 \
+  --context epic-description="Implement OAuth 2.0 with social login providers" \
+  --context mode=enterprise
+
+# Direct integration
+./invoke.sh "Implement real-time data processing pipeline" \
+  --mode=standard \
+  --output=pipeline-epic.json
+
+# Parse and validate in pipeline
+./validate-epic.sh pipeline-epic.json
+./parse-personas.sh pipeline-epic.json --format=markdown --output=pipeline-personas.md
+./estimate-costs.sh pipeline-epic.json --format=csv --output=pipeline-costs.csv
+```
+
+## Testing
+
+Run the comprehensive test suite:
+
+```bash
+# Run all tests
+./test-invoke.sh
+
+# Run specific test
+./test-invoke.sh --test generation
+
+# Keep logs for debugging
+./test-invoke.sh --keep-logs
+```
+
+The test suite validates:
+- Help functionality and error handling
+- Argument parsing and validation
+- Epic generation in all modes
+- JSON structure validation
+- Persona parsing and filtering
+- Cost estimation and formatting
+- Integration scenarios
+- Error handling edge cases
+
+## Dependencies
+
+- `jq`: Required for JSON processing
+  - Ubuntu/Debian: `sudo apt-get install jq`
+  - macOS: `brew install jq`
+- `bc`: Required for cost calculations (in estimate-costs.sh)
+  - Ubuntu/Debian: `sudo apt-get install bc`
+  - macOS: Pre-installed
+
+## Exit Codes
+
+- `0`: Success
+- `1`: General error
+- `2`: Validation error
+- `3`: Missing required arguments
+- `4`: Invalid mode specified
+- `5`: Agent execution failed
+
+## Best Practices
+
+1. **Clear Epic Descriptions**: Provide detailed, specific descriptions including:
+   - Business objectives
+   - Technical requirements
+   - Target users/stakeholders
+   - Success criteria
+   - Constraints and assumptions
+
+2. **Choose Appropriate Mode**:
+   - Use `mvp` for rapid prototyping and early validation
+   - Use `standard` for most production projects
+   - Use `enterprise` for regulated industries or large-scale systems
+
+3. **DevOps Considerations**:
+   - Enable `--enforce-devops` for production systems
+   - Review DevOps recommendations carefully for operational impact
+
+4. **Cost Analysis**:
+   - Use cost estimates for budget planning
+   - Prioritize blocking recommendations
+   - Consider total cost of ownership, not just implementation
+
+5. **Follow-up Actions**:
+   - Validate generated epics before proceeding
+   - Extract persona insights for stakeholder review
+   - Use cost breakdowns for financial planning
+   - Track implementation against recommendations
+
+## Examples
+
+### E-commerce Platform Epic
+
+```bash
+./invoke.sh \
+  "Build a scalable e-commerce platform with product catalog, shopping cart, payment processing, order management, and admin dashboard. Must support 100,000 concurrent users, multiple currencies, and real-time inventory updates." \
+  --mode=enterprise \
+  --enforce-devops \
+  --output=ecommerce-epic.json
+```
+
+### API Integration Epic
+
+```bash
+./invoke.sh \
+  "Integrate third-party payment gateways (Stripe, PayPal, Square) with existing order processing system. Include webhook handling, error retry logic, and comprehensive logging." \
+  --mode=standard \
+  --output=payment-integration-epic.json
+```
+
+### Data Migration Epic
+
+```bash
+./invoke.sh \
+  "Migrate legacy customer database from Oracle to PostgreSQL with zero downtime. Include data validation, rollback procedures, and performance optimization." \
+  --mode=enterprise \
+  --enforce-devops
+```
+
+## Troubleshooting
+
+### Common Issues
+
+1. **Invalid JSON output**
+   - Run validate-epic.sh to check structure
+   - Check agent logs for errors
+   - Ensure epic description is clear and complete
+
+2. **Missing recommendations**
+   - Try enterprise mode for comprehensive analysis
+   - Check if keywords trigger specific persona insights
+   - Review epic description for missing context
+
+3. **Cost estimation shows $0**
+   - Check if estimatedCost fields are populated
+   - Verify currency format is recognized
+   - Run with --verbose to see parsing details
+
+4. **DevOps recommendations not blocking**
+   - Use --enforce-devops flag
+   - Check DevOps persona status in output
+   - Review deployment-related keywords in description
+
+### Debug Mode
+
+Enable verbose logging to debug issues:
+
+```bash
+./invoke.sh "Your epic description" \
+    --verbose \
+    --output=debug-epic.json
+
+# Then validate with details
+./validate-epic.sh debug-epic.json --verbose
+```