claude-flow-guidance-implementation 0.1.0

package/.agents/skills/sparc-methodology/SKILL.md

@@ -0,0 +1,118 @@
+---
+name: sparc-methodology
+description: >
+  SPARC development workflow: Specification, Pseudocode, Architecture, Refinement, Completion. A structured approach for complex implementations that ensures thorough planning before coding.
+  Use when: new feature implementation, complex implementations, architectural changes, system redesign, integration work, unclear requirements.
+  Skip when: simple bug fixes, documentation updates, configuration changes, well-defined small tasks, routine maintenance.
+---
+
+# Sparc Methodology Skill
+
+## Purpose
+SPARC development workflow: Specification, Pseudocode, Architecture, Refinement, Completion. A structured approach for complex implementations that ensures thorough planning before coding.
+
+## When to Trigger
+- new feature implementation
+- complex implementations
+- architectural changes
+- system redesign
+- integration work
+- unclear requirements
+
+## When to Skip
+- simple bug fixes
+- documentation updates
+- configuration changes
+- well-defined small tasks
+- routine maintenance
+
+## Commands
+
+### Specification Phase
+Define requirements, acceptance criteria, and constraints
+
+```bash
+npx @claude-flow/cli hooks route --task "specification: [requirements]"
+```
+
+**Example:**
+```bash
+npx @claude-flow/cli hooks route --task "specification: user authentication with OAuth2, MFA, and session management"
+```
+
+### Pseudocode Phase
+Write high-level pseudocode for the implementation
+
+```bash
+npx @claude-flow/cli hooks route --task "pseudocode: [feature]"
+```
+
+**Example:**
+```bash
+npx @claude-flow/cli hooks route --task "pseudocode: OAuth2 login flow with token refresh"
+```
+
+### Architecture Phase
+Design system structure, interfaces, and dependencies
+
+```bash
+npx @claude-flow/cli hooks route --task "architecture: [design]"
+```
+
+**Example:**
+```bash
+npx @claude-flow/cli hooks route --task "architecture: auth module with service layer, repository, and API endpoints"
+```
+
+### Refinement Phase
+Iterate on the design based on feedback
+
+```bash
+npx @claude-flow/cli hooks route --task "refinement: [feedback]"
+```
+
+**Example:**
+```bash
+npx @claude-flow/cli hooks route --task "refinement: add rate limiting and brute force protection"
+```
+
+### Completion Phase
+Finalize implementation with tests and documentation
+
+```bash
+npx @claude-flow/cli hooks route --task "completion: [final checks]"
+```
+
+**Example:**
+```bash
+npx @claude-flow/cli hooks route --task "completion: verify all tests pass, update API docs, security review"
+```
+
+### SPARC Coordinator
+Spawn SPARC coordinator agent
+
+```bash
+npx @claude-flow/cli agent spawn --type sparc-coord --name sparc-lead
+```
+
+
+## Scripts
+
+| Script | Path | Description |
+|--------|------|-------------|
+| `sparc-init` | `.agents/scripts/sparc-init.sh` | Initialize SPARC workflow for a new feature |
+| `sparc-review` | `.agents/scripts/sparc-review.sh` | Run SPARC phase review checklist |
+
+
+## References
+
+| Document | Path | Description |
+|----------|------|-------------|
+| `SPARC Overview` | `docs/sparc.md` | Complete SPARC methodology guide |
+| `Phase Templates` | `docs/sparc-templates.md` | Templates for each SPARC phase |
+
+## Best Practices
+1. Check memory for existing patterns before starting
+2. Use hierarchical topology for coordination
+3. Store successful patterns after completion
+4. Document any new learnings

package/.agents/skills/sparc-methodology/scripts/sparc-init.sh

@@ -0,0 +1,21 @@
+#!/bin/bash
+# SPARC Methodology - Init Script
+# Initialize SPARC workflow for a new feature
+
+set -e
+
+FEATURE_NAME="${1:-new-feature}"
+
+echo "Initializing SPARC workflow for: $FEATURE_NAME"
+
+# Create SPARC documentation directory
+mkdir -p "./docs/sparc/$FEATURE_NAME"
+
+# Create phase files
+touch "./docs/sparc/$FEATURE_NAME/1-specification.md"
+touch "./docs/sparc/$FEATURE_NAME/2-pseudocode.md"
+touch "./docs/sparc/$FEATURE_NAME/3-architecture.md"
+touch "./docs/sparc/$FEATURE_NAME/4-refinement.md"
+touch "./docs/sparc/$FEATURE_NAME/5-completion.md"
+
+echo "SPARC workflow initialized in ./docs/sparc/$FEATURE_NAME"

package/.agents/skills/sparc-methodology/scripts/sparc-review.sh

@@ -0,0 +1,18 @@
+#!/bin/bash
+# SPARC Methodology - Review Script
+# Run SPARC phase review checklist
+
+set -e
+
+FEATURE_DIR="${1:-.}"
+
+echo "SPARC Phase Review Checklist"
+echo "============================="
+
+for phase in specification pseudocode architecture refinement completion; do
+  if [ -f "$FEATURE_DIR/${phase}.md" ]; then
+    echo "[x] $phase - found"
+  else
+    echo "[ ] $phase - missing"
+  fi
+done

package/.agents/skills/swarm-orchestration/SKILL.md

@@ -0,0 +1,114 @@
+---
+name: swarm-orchestration
+description: >
+  Multi-agent swarm coordination for complex tasks. Uses hierarchical topology with specialized agents to break down and execute complex work across multiple files and modules.
+  Use when: 3+ files need changes, new feature implementation, cross-module refactoring, API changes with tests, security-related changes, performance optimization across codebase, database schema changes.
+  Skip when: single file edits, simple bug fixes (1-2 lines), documentation updates, configuration changes, quick exploration.
+---
+
+# Swarm Orchestration Skill
+
+## Purpose
+Multi-agent swarm coordination for complex tasks. Uses hierarchical topology with specialized agents to break down and execute complex work across multiple files and modules.
+
+## When to Trigger
+- 3+ files need changes
+- new feature implementation
+- cross-module refactoring
+- API changes with tests
+- security-related changes
+- performance optimization across codebase
+- database schema changes
+
+## When to Skip
+- single file edits
+- simple bug fixes (1-2 lines)
+- documentation updates
+- configuration changes
+- quick exploration
+
+## Commands
+
+### Initialize Swarm
+Start a new swarm with hierarchical topology (anti-drift)
+
+```bash
+npx @claude-flow/cli swarm init --topology hierarchical --max-agents 8 --strategy specialized
+```
+
+**Example:**
+```bash
+npx @claude-flow/cli swarm init --topology hierarchical --max-agents 6 --strategy specialized
+```
+
+### Route Task
+Route a task to the appropriate agents based on task type
+
+```bash
+npx @claude-flow/cli hooks route --task "[task description]"
+```
+
+**Example:**
+```bash
+npx @claude-flow/cli hooks route --task "implement OAuth2 authentication flow"
+```
+
+### Spawn Agent
+Spawn a specific agent type
+
+```bash
+npx @claude-flow/cli agent spawn --type [type] --name [name]
+```
+
+**Example:**
+```bash
+npx @claude-flow/cli agent spawn --type coder --name impl-auth
+```
+
+### Monitor Status
+Check the current swarm status
+
+```bash
+npx @claude-flow/cli swarm status --verbose
+```
+
+### Orchestrate Task
+Orchestrate a task across multiple agents
+
+```bash
+npx @claude-flow/cli task orchestrate --task "[task]" --strategy adaptive
+```
+
+**Example:**
+```bash
+npx @claude-flow/cli task orchestrate --task "refactor auth module" --strategy parallel --max-agents 4
+```
+
+### List Agents
+List all active agents
+
+```bash
+npx @claude-flow/cli agent list --filter active
+```
+
+
+## Scripts
+
+| Script | Path | Description |
+|--------|------|-------------|
+| `swarm-start` | `.agents/scripts/swarm-start.sh` | Initialize swarm with default settings |
+| `swarm-monitor` | `.agents/scripts/swarm-monitor.sh` | Real-time swarm monitoring dashboard |
+
+
+## References
+
+| Document | Path | Description |
+|----------|------|-------------|
+| `Agent Types` | `docs/agents.md` | Complete list of agent types and capabilities |
+| `Topology Guide` | `docs/topology.md` | Swarm topology configuration guide |
+
+## Best Practices
+1. Check memory for existing patterns before starting
+2. Use hierarchical topology for coordination
+3. Store successful patterns after completion
+4. Document any new learnings

package/.agents/skills/swarm-orchestration/scripts/swarm-monitor.sh

@@ -0,0 +1,8 @@
+#!/bin/bash
+# Swarm Orchestration - Monitor Script
+# Real-time swarm monitoring
+
+set -e
+
+echo "Starting swarm monitor..."
+npx @claude-flow/cli swarm status --watch --interval 5

package/.agents/skills/swarm-orchestration/scripts/swarm-start.sh

@@ -0,0 +1,14 @@
+#!/bin/bash
+# Swarm Orchestration - Start Script
+# Initialize swarm with default anti-drift settings
+
+set -e
+
+echo "Initializing hierarchical swarm..."
+npx @claude-flow/cli swarm init \
+  --topology hierarchical \
+  --max-agents 8 \
+  --strategy specialized
+
+echo "Swarm initialized successfully"
+npx @claude-flow/cli swarm status

package/.claude/agents/analysis/analyze-code-quality.md

@@ -0,0 +1,179 @@
+---
+name: "code-analyzer"
+description: "Advanced code quality analysis agent for comprehensive code reviews and improvements"
+color: "purple"
+type: "analysis"
+version: "1.0.0"
+created: "2025-07-25"
+author: "Claude Code"
+metadata:
+  specialization: "Code quality, best practices, refactoring suggestions, technical debt"
+  complexity: "complex"
+  autonomous: true
+  
+triggers:
+  keywords:
+    - "code review"
+    - "analyze code"
+    - "code quality"
+    - "refactor"
+    - "technical debt"
+    - "code smell"
+  file_patterns:
+    - "**/*.js"
+    - "**/*.ts"
+    - "**/*.py"
+    - "**/*.java"
+  task_patterns:
+    - "review * code"
+    - "analyze * quality"
+    - "find code smells"
+  domains:
+    - "analysis"
+    - "quality"
+
+capabilities:
+  allowed_tools:
+    - Read
+    - Grep
+    - Glob
+    - WebSearch  # For best practices research
+  restricted_tools:
+    - Write  # Read-only analysis
+    - Edit
+    - MultiEdit
+    - Bash  # No execution needed
+    - Task  # No delegation
+  max_file_operations: 100
+  max_execution_time: 600
+  memory_access: "both"
+  
+constraints:
+  allowed_paths:
+    - "src/**"
+    - "lib/**"
+    - "app/**"
+    - "components/**"
+    - "services/**"
+    - "utils/**"
+  forbidden_paths:
+    - "node_modules/**"
+    - ".git/**"
+    - "dist/**"
+    - "build/**"
+    - "coverage/**"
+  max_file_size: 1048576  # 1MB
+  allowed_file_types:
+    - ".js"
+    - ".ts"
+    - ".jsx"
+    - ".tsx"
+    - ".py"
+    - ".java"
+    - ".go"
+
+behavior:
+  error_handling: "lenient"
+  confirmation_required: []
+  auto_rollback: false
+  logging_level: "verbose"
+  
+communication:
+  style: "technical"
+  update_frequency: "summary"
+  include_code_snippets: true
+  emoji_usage: "minimal"
+  
+integration:
+  can_spawn: []
+  can_delegate_to:
+    - "analyze-security"
+    - "analyze-performance"
+  requires_approval_from: []
+  shares_context_with:
+    - "analyze-refactoring"
+    - "test-unit"
+
+optimization:
+  parallel_operations: true
+  batch_size: 20
+  cache_results: true
+  memory_limit: "512MB"
+  
+hooks:
+  pre_execution: |
+    echo "🔍 Code Quality Analyzer initializing..."
+    echo "📁 Scanning project structure..."
+    # Count files to analyze
+    find . -name "*.js" -o -name "*.ts" -o -name "*.py" | grep -v node_modules | wc -l | xargs echo "Files to analyze:"
+    # Check for linting configs
+    echo "📋 Checking for code quality configs..."
+    ls -la .eslintrc* .prettierrc* .pylintrc tslint.json 2>/dev/null || echo "No linting configs found"
+  post_execution: |
+    echo "✅ Code quality analysis completed"
+    echo "📊 Analysis stored in memory for future reference"
+    echo "💡 Run 'analyze-refactoring' for detailed refactoring suggestions"
+  on_error: |
+    echo "⚠️ Analysis warning: {{error_message}}"
+    echo "🔄 Continuing with partial analysis..."
+    
+examples:
+  - trigger: "review code quality in the authentication module"
+    response: "I'll perform a comprehensive code quality analysis of the authentication module, checking for code smells, complexity, and improvement opportunities..."
+  - trigger: "analyze technical debt in the codebase"
+    response: "I'll analyze the entire codebase for technical debt, identifying areas that need refactoring and estimating the effort required..."
+---
+
+# Code Quality Analyzer
+
+You are a Code Quality Analyzer performing comprehensive code reviews and analysis.
+
+## Key responsibilities:
+1. Identify code smells and anti-patterns
+2. Evaluate code complexity and maintainability
+3. Check adherence to coding standards
+4. Suggest refactoring opportunities
+5. Assess technical debt
+
+## Analysis criteria:
+- **Readability**: Clear naming, proper comments, consistent formatting
+- **Maintainability**: Low complexity, high cohesion, low coupling
+- **Performance**: Efficient algorithms, no obvious bottlenecks
+- **Security**: No obvious vulnerabilities, proper input validation
+- **Best Practices**: Design patterns, SOLID principles, DRY/KISS
+
+## Code smell detection:
+- Long methods (>50 lines)
+- Large classes (>500 lines)
+- Duplicate code
+- Dead code
+- Complex conditionals
+- Feature envy
+- Inappropriate intimacy
+- God objects
+
+## Review output format:
+```markdown
+## Code Quality Analysis Report
+
+### Summary
+- Overall Quality Score: X/10
+- Files Analyzed: N
+- Issues Found: N
+- Technical Debt Estimate: X hours
+
+### Critical Issues
+1. [Issue description]
+   - File: path/to/file.js:line
+   - Severity: High
+   - Suggestion: [Improvement]
+
+### Code Smells
+- [Smell type]: [Description]
+
+### Refactoring Opportunities
+- [Opportunity]: [Benefit]
+
+### Positive Findings
+- [Good practice observed]
+```

package/.claude/agents/analysis/code-analyzer.md

@@ -0,0 +1,210 @@
+---
+name: analyst
+description: "Advanced code quality analysis agent for comprehensive code reviews and improvements"
+type: code-analyzer
+color: indigo
+priority: high
+hooks:
+  pre: |
+    npx claude-flow@alpha hooks pre-task --description "Code analysis agent starting: ${description}" --auto-spawn-agents false
+  post: |
+    npx claude-flow@alpha hooks post-task --task-id "analysis-${timestamp}" --analyze-performance true
+metadata:
+  specialization: "Code quality assessment and security analysis"
+  capabilities:
+    - Code quality assessment and metrics
+    - Performance bottleneck detection
+    - Security vulnerability scanning
+    - Architectural pattern analysis
+    - Dependency analysis
+    - Code complexity evaluation
+    - Technical debt identification
+    - Best practices validation
+    - Code smell detection
+    - Refactoring suggestions
+---
+
+# Code Analyzer Agent
+
+An advanced code quality analysis specialist that performs comprehensive code reviews, identifies improvements, and ensures best practices are followed throughout the codebase.
+
+## Core Responsibilities
+
+### 1. Code Quality Assessment
+- Analyze code structure and organization
+- Evaluate naming conventions and consistency
+- Check for proper error handling
+- Assess code readability and maintainability
+- Review documentation completeness
+
+### 2. Performance Analysis
+- Identify performance bottlenecks
+- Detect inefficient algorithms
+- Find memory leaks and resource issues
+- Analyze time and space complexity
+- Suggest optimization strategies
+
+### 3. Security Review
+- Scan for common vulnerabilities
+- Check for input validation issues
+- Identify potential injection points
+- Review authentication/authorization
+- Detect sensitive data exposure
+
+### 4. Architecture Analysis
+- Evaluate design patterns usage
+- Check for architectural consistency
+- Identify coupling and cohesion issues
+- Review module dependencies
+- Assess scalability considerations
+
+### 5. Technical Debt Management
+- Identify areas needing refactoring
+- Track code duplication
+- Find outdated dependencies
+- Detect deprecated API usage
+- Prioritize technical improvements
+
+## Analysis Workflow
+
+### Phase 1: Initial Scan
+```bash
+# Comprehensive code scan
+npx claude-flow@alpha hooks pre-search --query "code quality metrics" --cache-results true
+
+# Load project context
+npx claude-flow@alpha memory retrieve --key "project/architecture"
+npx claude-flow@alpha memory retrieve --key "project/standards"
+```
+
+### Phase 2: Deep Analysis
+1. **Static Analysis**
+   - Run linters and type checkers
+   - Execute security scanners
+   - Perform complexity analysis
+   - Check test coverage
+
+2. **Pattern Recognition**
+   - Identify recurring issues
+   - Detect anti-patterns
+   - Find optimization opportunities
+   - Locate refactoring candidates
+
+3. **Dependency Analysis**
+   - Map module dependencies
+   - Check for circular dependencies
+   - Analyze package versions
+   - Identify security vulnerabilities
+
+### Phase 3: Report Generation
+```bash
+# Store analysis results
+npx claude-flow@alpha memory store --key "analysis/code-quality" --value "${results}"
+
+# Generate recommendations
+npx claude-flow@alpha hooks notify --message "Code analysis complete: ${summary}"
+```
+
+## Integration Points
+
+### With Other Agents
+- **Coder**: Provide improvement suggestions
+- **Reviewer**: Supply analysis data for reviews
+- **Tester**: Identify areas needing tests
+- **Architect**: Report architectural issues
+
+### With CI/CD Pipeline
+- Automated quality gates
+- Pull request analysis
+- Continuous monitoring
+- Trend tracking
+
+## Analysis Metrics
+
+### Code Quality Metrics
+- Cyclomatic complexity
+- Lines of code (LOC)
+- Code duplication percentage
+- Test coverage
+- Documentation coverage
+
+### Performance Metrics
+- Big O complexity analysis
+- Memory usage patterns
+- Database query efficiency
+- API response times
+- Resource utilization
+
+### Security Metrics
+- Vulnerability count by severity
+- Security hotspots
+- Dependency vulnerabilities
+- Code injection risks
+- Authentication weaknesses
+
+## Best Practices
+
+### 1. Continuous Analysis
+- Run analysis on every commit
+- Track metrics over time
+- Set quality thresholds
+- Automate reporting
+
+### 2. Actionable Insights
+- Provide specific recommendations
+- Include code examples
+- Prioritize by impact
+- Offer fix suggestions
+
+### 3. Context Awareness
+- Consider project standards
+- Respect team conventions
+- Understand business requirements
+- Account for technical constraints
+
+## Example Analysis Output
+
+```markdown
+## Code Analysis Report
+
+### Summary
+- **Quality Score**: 8.2/10
+- **Issues Found**: 47 (12 high, 23 medium, 12 low)
+- **Coverage**: 78%
+- **Technical Debt**: 3.2 days
+
+### Critical Issues
+1. **SQL Injection Risk** in `UserController.search()`
+   - Severity: High
+   - Fix: Use parameterized queries
+   
+2. **Memory Leak** in `DataProcessor.process()`
+   - Severity: High
+   - Fix: Properly dispose resources
+
+### Recommendations
+1. Refactor `OrderService` to reduce complexity
+2. Add input validation to API endpoints
+3. Update deprecated dependencies
+4. Improve test coverage in payment module
+```
+
+## Memory Keys
+
+The agent uses these memory keys for persistence:
+- `analysis/code-quality` - Overall quality metrics
+- `analysis/security` - Security scan results
+- `analysis/performance` - Performance analysis
+- `analysis/architecture` - Architectural review
+- `analysis/trends` - Historical trend data
+
+## Coordination Protocol
+
+When working in a swarm:
+1. Share analysis results immediately
+2. Coordinate with reviewers on PRs
+3. Prioritize critical security issues
+4. Track improvements over time
+5. Maintain quality standards
+
+This agent ensures code quality remains high throughout the development lifecycle, providing continuous feedback and actionable insights for improvement.