claude-flow-novice 2.11.0 → 2.13.0

package/claude-assets/commands/cfn/github.md

@@ -1,221 +0,0 @@
----
-description: "GitHub integration for repository management, PR automation, and collaboration"
-argument-hint: "<action> [repository] [options]"
-allowed-tools: ["Bash", "Read", "Write", "Grep", "mcp__claude-flow__github_repo_analyze", "mcp__claude-flow__github_pr_manage", "mcp__claude-flow__github_release_coord", "mcp__claude-flow__github_issue_track", "mcp__claude-flow__github_workflow_auto", "mcp__claude-flow__github_metrics", "mcp__claude-flow__agent_spawn", "mcp__claude-flow__memory_usage"]
----
-
-# GitHub Integration & Automation
-
-Comprehensive GitHub integration for repository management, automated workflows, and team collaboration.
-
-**Action**: $ARGUMENTS
-
-## Available Actions
-
-### Repository Management
-- `analyze <repo>` - Comprehensive repository analysis
-- `metrics <repo>` - Repository health and activity metrics
-- `security-scan <repo>` - Security vulnerability scanning
-- `performance-audit <repo>` - Performance and quality assessment
-
-### Pull Request Management
-- `pr create <title>` - Create PR with AI-generated description
-- `pr review <number>` - Automated code review with suggestions
-- `pr merge <number>` - Smart merge with conflict resolution
-- `pr status` - Show all open PRs with analysis
-
-### Issue Management
-- `issue create <title>` - Create issue with templates
-- `issue triage` - AI-powered issue triage and labeling
-- `issue assign` - Smart assignment based on expertise
-- `issue close <number>` - Close issue with summary
-
-### Release Management
-- `release create <version>` - Create release with changelog
-- `release notes <version>` - Generate release notes
-- `release deploy <version>` - Coordinate deployment
-
-### Workflow Automation
-- `workflow setup` - Configure GitHub Actions workflows
-- `workflow status` - Monitor workflow runs
-- `workflow optimize` - Optimize CI/CD performance
-
-## Key Features
-
-### 🔍 AI-Powered Repository Analysis
-
-#### Code Quality Assessment
-- **Architecture Analysis**: Design patterns, SOLID principles compliance
-- **Code Complexity**: Cyclomatic complexity, maintainability index
-- **Technical Debt**: Identification and prioritization
-- **Documentation Quality**: README, API docs, inline comments
-
-#### Security Analysis
-- **Vulnerability Scanning**: Dependencies, code patterns, configurations
-- **Secret Detection**: API keys, passwords, certificates
-- **Access Control**: Repository permissions and branch protection
-- **Supply Chain**: Dependency risk assessment
-
-#### Performance Metrics
-- **Build Performance**: CI/CD execution times, bottlenecks
-- **Code Performance**: Static analysis, performance patterns
-- **Repository Health**: Commit frequency, contributor activity
-- **Issue Resolution**: Response times, resolution rates
-
-### 🤖 Automated Code Review
-
-#### Intelligent PR Analysis
-- **Change Impact**: Affected components and systems
-- **Risk Assessment**: Breaking changes, security implications
-- **Test Coverage**: Missing tests, coverage impact
-- **Documentation**: Required documentation updates
-
-#### Review Automation
-- **Style Compliance**: Code formatting, naming conventions
-- **Best Practices**: Language-specific recommendations
-- **Performance Impact**: Bundle size, runtime performance
-- **Security Review**: Vulnerability patterns, secure coding
-
-### 📈 Advanced Metrics & Insights
-
-#### Team Productivity
-- **Contributor Analysis**: Activity patterns, expertise areas
-- **Collaboration Metrics**: PR review patterns, response times
-- **Knowledge Sharing**: Documentation contributions, mentoring
-- **Burnout Detection**: Workload analysis, health indicators
-
-#### Project Health
-- **Velocity Tracking**: Feature delivery, sprint performance
-- **Quality Trends**: Bug rates, test coverage over time
-- **Maintenance Load**: Technical debt, refactoring needs
-- **Community Growth**: Star/fork growth, issue engagement
-
-## Usage Examples
-
-### Repository Analysis
-```bash
-# Comprehensive repository analysis
-/github analyze myorg/myrepo
-
-# Output includes:
-# - Code quality score (1-10)
-# - Security vulnerability count
-# - Performance bottlenecks
-# - Improvement recommendations
-# - Contributor activity analysis
-```
-
-### PR Management
-```bash
-# Create PR with AI description
-/github pr create "Add user authentication"
-
-# Automated code review
-/github pr review 123
-
-# Output:
-# - Code quality assessment
-# - Security review
-# - Performance impact
-# - Test coverage analysis
-# - Suggested improvements
-```
-
-### Issue Triage
-```bash
-# AI-powered issue triage
-/github issue triage
-
-# Automatically:
-# - Labels issues by type/priority
-# - Assigns to appropriate team members
-# - Estimates effort/complexity
-# - Suggests related issues
-```
-
-### Release Management
-```bash
-# Create release with changelog
-/github release create v2.1.0
-
-# Automatically:
-# - Generates changelog from commits
-# - Identifies breaking changes
-# - Creates release notes
-# - Tags version and triggers deployment
-```
-
-## Sample Analysis Output
-
-```markdown
-# Repository Analysis: myorg/awesome-project
-
-## 🏆 Overall Health Score: 8.7/10
-
-### 🔍 Code Quality (9.2/10)
-- **Architecture**: Well-structured, follows SOLID principles
-- **Complexity**: Low average complexity (2.3/10)
-- **Documentation**: Comprehensive README, 85% API coverage
-- **Testing**: 94% code coverage, good test quality
-
-### 🛡️ Security (7.8/10)
-- **Vulnerabilities**: 2 medium-risk dependencies
-- **Secrets**: No exposed secrets detected
-- **Permissions**: Appropriate branch protection rules
-- **Recommendations**: Update lodash to v4.17.21
-
-### 🚀 Performance (8.5/10)
-- **Build Time**: 3.2 minutes (good)
-- **Bundle Size**: 245KB (acceptable)
-- **CI Efficiency**: 95% success rate
-- **Bottlenecks**: Database tests could be optimized
-
-### 📈 Team Metrics
-- **Active Contributors**: 12 (last 30 days)
-- **PR Response Time**: 4.2 hours average
-- **Issue Resolution**: 89% within SLA
-- **Knowledge Distribution**: Good (no single points of failure)
-
-## 📝 Recommendations
-1. **Security**: Update 2 vulnerable dependencies
-2. **Performance**: Optimize database test suite
-3. **Process**: Consider automated dependency updates
-4. **Documentation**: Add contribution guidelines
-```
-
-## Workflow Automation
-
-### CI/CD Optimization
-- **Pipeline Analysis**: Identify bottlenecks and optimization opportunities
-- **Parallel Execution**: Suggest parallelization strategies
-- **Caching**: Optimize build caches and artifact storage
-- **Resource Usage**: Monitor and optimize runner usage
-
-### Quality Gates
-- **Automated Testing**: Ensure comprehensive test coverage
-- **Security Scanning**: Integrate security checks into pipelines
-- **Performance Testing**: Monitor performance regressions
-- **Documentation**: Ensure documentation stays up-to-date
-
-## Multi-Repository Management
-
-### Organization Overview
-- **Repository Health Dashboard**: Cross-repo metrics and trends
-- **Dependency Management**: Shared dependency updates
-- **Security Compliance**: Organization-wide security policies
-- **Knowledge Sharing**: Cross-team learning and best practices
-
-### Release Coordination
-- **Multi-Repo Releases**: Coordinate releases across services
-- **Dependency Tracking**: Monitor inter-service dependencies
-- **Rollback Management**: Coordinate rollbacks across systems
-- **Communication**: Automated stakeholder notifications
-
-## Integration with Claude Flow
-
-- **Agent Coordination**: Deploy specialized GitHub agents
-- **Memory Persistence**: Remember repository context across sessions
-- **Learning**: Improve recommendations based on team patterns
-- **Automation**: Custom workflows based on team preferences
-
-Streamline your GitHub workflow with AI-powered automation and insights.

package/claude-assets/commands/cfn/hooks.md

@@ -1,38 +0,0 @@
----
-description: "Automation hooks management"
-argument-hint: "<action> [parameters]"
-allowed-tools: ["Bash", "mcp__claude-flow-novice__memory_usage"]
----
-
-# Automation Hooks Management
-
-Manage automation hooks for pre/post operations and session coordination.
-
-**Action**: $ARGUMENTS
-
-**Available Hook Actions**:
-- `enable` - Enable all automation hooks
-- `disable` - Disable automation hooks
-- `pre-task "<description>"` - Execute pre-task hook
-- `post-task "<task-id>"` - Execute post-task hook
-- `session-start` - Start coordination session
-- `session-end` - End session with summary
-- `notify "<message>"` - Send notification to swarm
-
-**Hook Types**:
-
-## Pre-Operation Hooks
-- **Pre-Command**: Validate commands for safety
-- **Pre-Edit**: Auto-assign agents by file type
-- **Pre-Task**: Prepare resources and context
-
-## Post-Operation Hooks
-- **Post-Command**: Track metrics and results
-- **Post-Edit**: Auto-format code and update memory
-- **Post-Task**: Store completion data
-
-## Session Hooks
-- **Session Start**: Initialize coordination context
-- **Session End**: Generate summaries and persist state
-
-Execute the specified hook action and coordinate with the claude-flow-novice system for automation.

package/claude-assets/commands/cfn/metrics-summary.md

@@ -1,58 +0,0 @@
-# Metrics Summary
-
-Display aggregated metrics statistics with configurable time frame and manage metrics tracking.
-
-## Usage
-
-```bash
-# Display metrics summary
-/metrics-summary [--minutes=60] [--provider=all] [--model=all]
-
-# Manage tracking
-/metrics-summary --enable    # Enable metrics tracking
-/metrics-summary --disable   # Disable metrics tracking
-/metrics-summary --status    # Check tracking status
-```
-
-## Parameters
-
-### Display Metrics
-- `--minutes` - Time frame in minutes (default: 60 = last hour)
-  - Examples: 60 (1 hour), 1440 (24 hours), 10080 (7 days)
-- `--provider` - Filter by provider: `all`, `anthropic`, `z.ai` (default: all)
-- `--model` - Filter by model name (default: all)
-
-### Manage Tracking
-- `--enable` - Enable metrics tracking
-- `--disable` - Disable metrics tracking
-- `--status` - Check current tracking status
-
-## Examples
-
-```bash
-# Last hour stats (all providers)
-/metrics-summary
-
-# Last 24 hours
-/metrics-summary --minutes=1440
-
-# Last hour Z.ai only
-/metrics-summary --minutes=60 --provider=z.ai
-
-# Last 7 days GLM-4.6 only
-/metrics-summary --minutes=10080 --model=glm-4.6
-
-# Enable/disable tracking
-/metrics-summary --enable
-/metrics-summary --disable
-/metrics-summary --status
-```
-
-## Output
-
-- **API Requests**: Total count by provider
-- **Token Usage**: Input/Output/Total by provider and model
-- **Error Rate**: Success vs error percentage
-- **Cost Breakdown**: Estimated costs by provider (if pricing available)
-- **Top Models**: Most used models in time frame
-- **Performance**: Average API duration by provider

package/claude-assets/commands/cfn/neural.md

@@ -1,39 +0,0 @@
----
-description: "Neural network training and management"
-argument-hint: "<action> [parameters]"
-allowed-tools: ["mcp__claude-flow-novice__memory_usage", "mcp__claude-flow-novice__performance_report"]
----
-
-# Neural Network Training & Management
-
-Manage neural networks, training, and cognitive patterns for AI agents.
-
-**Action**: $ARGUMENTS
-
-**Available Neural Actions**:
-- `status` - Check neural network status
-- `train <pattern> <iterations>` - Train neural patterns
-- `patterns` - Analyze cognitive patterns
-- `predict "<input>"` - Make neural predictions
-- `compress <model>` - Compress neural models
-- `explain <prediction>` - Explain neural decisions
-
-**Neural Capabilities**:
-
-## Training Patterns
-- **Coordination**: Agent coordination patterns
-- **Optimization**: Performance optimization patterns
-- **Prediction**: Task completion prediction
-
-## Cognitive Patterns
-- **Convergent**: Focused problem-solving
-- **Divergent**: Creative exploration
-- **Lateral**: Cross-domain thinking
-- **Systems**: Holistic system analysis
-
-## Model Management
-- **WASM SIMD**: Accelerated neural processing
-- **Ensemble**: Multiple model coordination
-- **Transfer**: Cross-domain learning
-
-Execute neural network operations with real-time feedback and performance monitoring.

package/claude-assets/commands/cfn/parse-epic.md

@@ -1,357 +0,0 @@
----
-description: "Parse natural language epic documents to structured JSON configuration"
-argument-hint: "<epic-directory> [--output <file>] [--validate]"
-allowed-tools: ["Read", "Write", "Bash", "Glob", "Grep"]
----
-
-# Parse Epic - Natural Language to Structured JSON
-
-Convert natural language epic markdown documents into structured JSON configuration for CFN Loop execution.
-
-**Input**: Natural language epic directory with markdown files
-**Output**: Structured JSON configuration with phases, sprints, dependencies
-
-## Usage
-
-```bash
-# Basic parsing
-/parse-epic planning/example-epic
-
-# With custom output file
-/parse-epic planning/my-epic --output epic-config.json
-
-# With validation
-/parse-epic planning/auth-epic --validate
-
-# Full options
-/parse-epic planning/example-epic --output custom-epic.json --validate
-```
-
-## Command Arguments
-
-- `<epic-directory>`: **Required** - Path to epic directory containing markdown files
-- `--output <file>`: Optional - Custom output JSON file (default: `<epic-name>-config.json`)
-- `--validate`: Optional - Validate parsed configuration against schema
-
-## Epic Directory Structure
-
-```
-planning/example-epic/
-├── OVERVIEW.md              # Epic description, goals, scope
-├── phase-1-authentication.md    # Phase 1 details
-├── phase-2-authorization.md     # Phase 2 details
-├── phase-3-session-mgmt.md      # Phase 3 details
-└── dependencies.md          # Cross-phase dependencies (optional)
-```
-
-## Markdown Format
-
-### OVERVIEW.md
-```markdown
-# Auth System Epic
-
-**Goal**: Build complete authentication and authorization system
-
-## Scope
-
-### In Scope
-- JWT-based authentication
-- Role-based access control (RBAC)
-- Session management
-- Password security (bcrypt)
-
-### Out of Scope
-- OAuth/social login
-- Multi-factor authentication
-- Biometric authentication
-
-## Risk Profile
-public-facing-medium-risk
-
-## Estimated Timeline
-3 phases, 8 sprints total
-```
-
-### Phase Markdown (phase-1-authentication.md)
-```markdown
-# Phase 1: User Authentication
-
-**Phase ID**: 1
-**Dependencies**: None
-
-## Deliverables
-- Login API endpoint (POST /auth/login)
-- JWT token generation
-- Password validation
-- bcrypt password hashing
-
-## Sprints
-
-### Sprint 1.1: Core Login API
-- POST /auth/login endpoint
-- JWT token generation
-- Basic password validation
-**Estimated Agents**: 3
-
-### Sprint 1.2: Password Security
-- bcrypt password hashing
-- Salt generation
-- Hash verification
-**Estimated Agents**: 2
-
-## Success Criteria
-- All login tests passing
-- Security audit complete
-- API documentation updated
-```
-
-## Output JSON Structure
-
-The parser generates a structured JSON configuration:
-
-```json
-{
-  "epic_name": "auth-system",
-  "epic_goal": "Build complete authentication and authorization system",
-  "scope": {
-    "in_scope": [
-      "JWT-based authentication",
-      "Role-based access control (RBAC)",
-      "Session management",
-      "Password security (bcrypt)"
-    ],
-    "out_of_scope": [
-      "OAuth/social login",
-      "Multi-factor authentication",
-      "Biometric authentication"
-    ],
-    "risk_profile": "public-facing-medium-risk"
-  },
-  "phases": [
-    {
-      "phase_id": "1",
-      "phase_name": "User Authentication",
-      "dependencies": [],
-      "deliverables": [
-        "Login API endpoint (POST /auth/login)",
-        "JWT token generation",
-        "Password validation",
-        "bcrypt password hashing"
-      ],
-      "sprints": [
-        {
-          "sprint_id": "1.1",
-          "sprint_name": "Core Login API",
-          "deliverables": [
-            "POST /auth/login endpoint",
-            "JWT token generation",
-            "Basic password validation"
-          ],
-          "estimated_agents": 3
-        },
-        {
-          "sprint_id": "1.2",
-          "sprint_name": "Password Security",
-          "deliverables": [
-            "bcrypt password hashing",
-            "Salt generation",
-            "Hash verification"
-          ],
-          "estimated_agents": 2
-        }
-      ],
-      "success_criteria": [
-        "All login tests passing",
-        "Security audit complete",
-        "API documentation updated"
-      ]
-    }
-  ],
-  "decision_authority_config": {
-    "auto_approve_threshold": 0.90,
-    "auto_relaunch_max_iteration": 10,
-    "escalation_criteria": [
-      "security vulnerability",
-      "data loss risk"
-    ]
-  }
-}
-```
-
-## Validation
-
-When using `--validate`, the parser checks:
-- ✅ Valid phase IDs and naming
-- ✅ Dependency resolution (no circular dependencies)
-- ✅ Sprint numbering consistency (1.1, 1.2, etc.)
-- ✅ Deliverables are non-empty
-- ✅ Scope boundaries are defined
-- ✅ Risk profile is valid (internal-only-low-risk, public-facing-medium-risk, critical-high-risk)
-- ✅ Success criteria are specified
-
-**Validation Errors:**
-```
-❌ Validation Failed:
-- Phase 2 dependency on Phase 5 (does not exist)
-- Sprint 1.3 missing deliverables
-- Risk profile "high" invalid (use: internal-only-low-risk, public-facing-medium-risk, critical-high-risk)
-```
-
-## Integration with CFN Loop
-
-After parsing, use the JSON configuration with CFN Loop commands:
-
-```bash
-# 1. Parse epic to JSON
-/parse-epic planning/auth-epic --output auth-config.json --validate
-
-# 2. Execute epic using parsed configuration
-/cfn-loop-epic "$(cat auth-config.json)"
-
-# Or manually reference phases
-/cfn-loop-sprints "Phase 1: User Authentication (from auth-config.json)"
-```
-
-## Automatic Scope Storage
-
-The parser automatically stores scope boundaries in memory for Product Owner access:
-
-```javascript
-// Automatically executed during parsing
-mcp__claude-flow-novice__memory_usage({
-  action: "store",
-  namespace: "scope-control",
-  key: "project-boundaries",
-  value: JSON.stringify({
-    primary_goal: epicConfig.epic_goal,
-    in_scope: epicConfig.scope.in_scope,
-    out_of_scope: epicConfig.scope.out_of_scope,
-    risk_profile: epicConfig.scope.risk_profile,
-    decision_authority_config: epicConfig.decision_authority_config
-  })
-})
-```
-
-## Example Workflows
-
-### Workflow 1: Parse and Execute Epic
-```bash
-# Step 1: Create epic markdown files in planning/auth-epic/
-# Step 2: Parse to JSON
-/parse-epic planning/auth-epic --output auth-config.json --validate
-
-# Step 3: Execute epic (automatic phase orchestration)
-/cfn-loop-epic "$(cat auth-config.json)"
-```
-
-### Workflow 2: Parse and Execute Single Phase
-```bash
-# Step 1: Parse epic
-/parse-epic planning/my-epic --validate
-
-# Step 2: Extract specific phase (manual)
-# Read my-epic-config.json, copy Phase 1 details
-
-# Step 3: Execute single phase
-/cfn-loop-sprints "Phase 1 content from parsed JSON"
-```
-
-### Workflow 3: Validate Epic Structure
-```bash
-# Validate epic structure before execution
-/parse-epic planning/complex-epic --validate
-
-# Review validation output
-# Fix any errors in markdown files
-# Re-run validation until clean
-```
-
-## Output Files
-
-**Generated Files:**
-- `<epic-name>-config.json` - Structured epic configuration
-- `<epic-name>-validation-report.json` - Validation results (if --validate)
-
-**Example Output:**
-```bash
-🔍 Epic Parser - Natural Language to Structured JSON
-
-📂 Epic directory: planning/auth-epic
-📄 Overview file: OVERVIEW.md
-
-✅ Parsed successfully:
-   - Epic: auth-system
-   - Phases: 3
-   - Total Sprints: 8
-   - Scope boundaries: ✓
-   - Dependencies: ✓
-
-📄 Output: auth-config.json
-✅ Validation: PASSED
-
-Ready for CFN Loop execution!
-```
-
-## Error Handling
-
-**Common Errors:**
-
-1. **Missing OVERVIEW.md**
-   ```
-   ❌ Epic directory must contain OVERVIEW.md
-   ```
-
-2. **Invalid Phase Dependencies**
-   ```
-   ❌ Phase 3 depends on Phase 5 (not found)
-   ```
-
-3. **Circular Dependencies**
-   ```
-   ❌ Circular dependency detected: Phase 1 → Phase 2 → Phase 1
-   ```
-
-4. **Invalid Sprint Numbering**
-   ```
-   ❌ Sprint 1.5 follows 1.2 (expected 1.3)
-   ```
-
-## Advanced Features
-
-### Custom Risk Profiles
-```markdown
-## Risk Profile
-custom-high-security-critical
-
-## Decision Authority
-- Auto-approve threshold: 0.95
-- Max iteration: 5
-- Escalation: security-team-approval-required
-```
-
-### Cross-Phase Dependencies
-Create `dependencies.md`:
-```markdown
-# Epic Dependencies
-
-- Phase 2 requires Phase 1 (authentication must complete first)
-- Phase 3 requires Phase 1, Phase 2 (session needs auth + authorization)
-- Phase 4 requires Phase 3 (admin panel needs sessions)
-```
-
-### Sprint Estimation
-```markdown
-### Sprint 2.3: Complex Authorization Logic
-**Estimated Agents**: 8
-**Complexity**: High
-**Rationale**: Multi-tenant RBAC with custom permission system
-```
-
-## Tips for Epic Creation
-
-1. **Start with OVERVIEW.md** - Define clear scope boundaries
-2. **One phase per file** - Keep phase definitions modular
-3. **Explicit dependencies** - Document all cross-phase requirements
-4. **Realistic sprint sizing** - 2-5 deliverables per sprint
-5. **Validate early** - Use `--validate` during epic creation
-6. **Clear success criteria** - Define measurable phase completion criteria