@goonnguyen/human-mcp 1.3.0 → 2.0.0

package/.claude/send-discord.sh

@@ -1,64 +0,0 @@
-#!/bin/bash
-
-# Usage: ./send-discord.sh 'Your message here'
-# Note: Remember to escape the string
-
-# Load environment variables from .env file
-if [[ -f .env ]]; then
-    echo "Loading .env file..."
-    set -a  # automatically export all variables
-    source .env
-    set +a  # turn off automatic export
-    echo "✅ Environment loaded, DISCORD_WEBHOOK_URL=$(echo ${DISCORD_WEBHOOK_URL:0:50}...)"
-else
-    echo "Warning: .env file not found"
-fi
-
-message="$1"
-    
-if [[ -z "$DISCORD_WEBHOOK_URL" ]]; then
-    echo "⚠️  Discord notification skipped: DISCORD_WEBHOOK_URL not set"
-    exit 1
-fi
-
-# Prepare message for Discord (Discord markdown supports \n)
-discord_message="$message"
-
-# Discord embeds for richer formatting
-payload=$(cat <<EOF
-{
-"embeds": [{
-    "title": "🤖 Claude Code Session Complete",
-    "description": "$discord_message",
-    "color": 5763719,
-    "timestamp": "$(date -u +%Y-%m-%dT%H:%M:%S.000Z)",
-    "footer": {
-        "text": "DevPocket API • $(basename "$(pwd)")"
-    },
-    "fields": [
-        {
-            "name": "⏰ Session Time",
-            "value": "$(date '+%H:%M:%S')",
-            "inline": true
-        },
-        {
-            "name": "📂 Project",
-            "value": "$(basename "$(pwd)")",
-            "inline": true
-        }
-    ]
-}]
-}
-EOF
-)
-
-curl -s -X POST "$DISCORD_WEBHOOK_URL" \
-    -H "Content-Type: application/json" \
-    -d "$payload" >/dev/null 2>&1
-
-if [[ $? -eq 0 ]]; then
-    echo "✅ Discord notification sent"
-else
-    echo "❌ Failed to send Discord notification"
-    exit 1
-fi

package/.claude/settings.json

@@ -1,7 +0,0 @@
-{
-  "statusLine": {
-    "type": "command",
-    "command": ".claude/statusline.sh",
-    "padding": 0
-  }
-}

package/.claude/statusline.sh

@@ -1,143 +0,0 @@
-#!/bin/bash
-# Generated by cc-statusline (https://www.npmjs.com/package/@chongdashu/cc-statusline)
-# Custom Claude Code statusline - Created: 2025-08-19T05:45:09.773Z
-# Theme: detailed | Colors: true | Features: directory, git, model, usage, session, tokens
-
-input=$(cat)
-
-# ---- color helpers (TTY-aware, respect NO_COLOR) ----
-use_color=1
-[ -t 1 ] || use_color=0
-[ -n "$NO_COLOR" ] && use_color=0
-
-C() { if [ "$use_color" -eq 1 ]; then printf '\033[%sm' "$1"; fi; }
-RST() { if [ "$use_color" -eq 1 ]; then printf '\033[0m'; fi; }
-
-# ---- basic colors ----
-dir_color() { if [ "$use_color" -eq 1 ]; then printf '\033[1;36m'; fi; }    # cyan
-model_color() { if [ "$use_color" -eq 1 ]; then printf '\033[1;35m'; fi; }  # magenta  
-version_color() { if [ "$use_color" -eq 1 ]; then printf '\033[1;33m'; fi; } # yellow
-rst() { if [ "$use_color" -eq 1 ]; then printf '\033[0m'; fi; }
-
-# ---- time helpers ----
-to_epoch() {
-  ts="$1"
-  if command -v gdate >/dev/null 2>&1; then gdate -d "$ts" +%s 2>/dev/null && return; fi
-  date -u -j -f "%Y-%m-%dT%H:%M:%S%z" "${ts/Z/+0000}" +%s 2>/dev/null && return
-  python3 - "$ts" <<'PY' 2>/dev/null
-import sys, datetime
-s=sys.argv[1].replace('Z','+00:00')
-print(int(datetime.datetime.fromisoformat(s).timestamp()))
-PY
-}
-
-fmt_time_hm() {
-  epoch="$1"
-  if date -r 0 +%s >/dev/null 2>&1; then date -r "$epoch" +"%H:%M"; else date -d "@$epoch" +"%H:%M"; fi
-}
-
-progress_bar() {
-  pct="${1:-0}"; width="${2:-10}"
-  [[ "$pct" =~ ^[0-9]+$ ]] || pct=0; ((pct<0))&&pct=0; ((pct>100))&&pct=100
-  filled=$(( pct * width / 100 )); empty=$(( width - filled ))
-  printf '%*s' "$filled" '' | tr ' ' '='
-  printf '%*s' "$empty" '' | tr ' ' '-'
-}
-
-# git utilities
-num_or_zero() { v="$1"; [[ "$v" =~ ^[0-9]+$ ]] && echo "$v" || echo 0; }
-
-# ---- basics ----
-if command -v jq >/dev/null 2>&1; then
-  current_dir=$(echo "$input" | jq -r '.workspace.current_dir // .cwd // "unknown"' 2>/dev/null | sed "s|^$HOME|~|g")
-  model_name=$(echo "$input" | jq -r '.model.display_name // "Claude"' 2>/dev/null)
-  model_version=$(echo "$input" | jq -r '.model.version // ""' 2>/dev/null)
-else
-  current_dir="unknown"
-  model_name="Claude"; model_version=""
-fi
-
-# ---- git colors ----
-git_color() { if [ "$use_color" -eq 1 ]; then printf '\033[1;32m'; fi; }
-rst() { if [ "$use_color" -eq 1 ]; then printf '\033[0m'; fi; }
-
-# ---- git ----
-git_branch=""
-if git rev-parse --git-dir >/dev/null 2>&1; then
-  git_branch=$(git branch --show-current 2>/dev/null || git rev-parse --short HEAD 2>/dev/null)
-fi
-
-# ---- usage colors ----
-usage_color() { if [ "$use_color" -eq 1 ]; then printf '\033[1;35m'; fi; }
-cost_color() { if [ "$use_color" -eq 1 ]; then printf '\033[1;36m'; fi; }
-session_color() { 
-  rem_pct=$(( 100 - session_pct ))
-  if   (( rem_pct <= 10 )); then SCLR='1;31'
-  elif (( rem_pct <= 25 )); then SCLR='1;33'
-  else                          SCLR='1;32'; fi
-  if [ "$use_color" -eq 1 ]; then printf '\033[%sm' "$SCLR"; fi
-}
-
-# ---- ccusage integration ----
-session_txt=""; session_pct=0; session_bar=""
-cost_usd=""; cost_per_hour=""; tpm=""; tot_tokens=""
-
-if command -v jq >/dev/null 2>&1; then
-  blocks_output=$(npx ccusage@latest blocks --json 2>/dev/null || ccusage blocks --json 2>/dev/null)
-  if [ -n "$blocks_output" ]; then
-    active_block=$(echo "$blocks_output" | jq -c '.blocks[] | select(.isActive == true)' 2>/dev/null | head -n1)
-    if [ -n "$active_block" ]; then
-      cost_usd=$(echo "$active_block" | jq -r '.costUSD // empty')
-      cost_per_hour=$(echo "$active_block" | jq -r '.burnRate.costPerHour // empty')
-      tot_tokens=$(echo "$active_block" | jq -r '.totalTokens // empty')
-      
-      # Session time calculation
-      reset_time_str=$(echo "$active_block" | jq -r '.usageLimitResetTime // .endTime // empty')
-      start_time_str=$(echo "$active_block" | jq -r '.startTime // empty')
-      
-      if [ -n "$reset_time_str" ] && [ -n "$start_time_str" ]; then
-        start_sec=$(to_epoch "$start_time_str"); end_sec=$(to_epoch "$reset_time_str"); now_sec=$(date +%s)
-        total=$(( end_sec - start_sec )); (( total<1 )) && total=1
-        elapsed=$(( now_sec - start_sec )); (( elapsed<0 ))&&elapsed=0; (( elapsed>total ))&&elapsed=$total
-        session_pct=$(( elapsed * 100 / total ))
-        remaining=$(( end_sec - now_sec )); (( remaining<0 )) && remaining=0
-        rh=$(( remaining / 3600 )); rm=$(( (remaining % 3600) / 60 ))
-        end_hm=$(fmt_time_hm "$end_sec")
-        session_txt="$(printf '%dh %dm until reset at %s (%d%%)' "$rh" "$rm" "$end_hm" "$session_pct")"
-        session_bar=$(progress_bar "$session_pct" 10)
-      fi
-    fi
-  fi
-fi
-
-# ---- render statusline ----
-printf '📁 %s%s%s' "$(dir_color)" "$current_dir" "$(rst)"
-# git display
-if [ -n "$git_branch" ]; then
-  printf '  🌿 %s%s%s' "$(git_color)" "$git_branch" "$(rst)"
-fi
-printf '  🤖 %s%s%s' "$(model_color)" "$model_name" "$(rst)"
-if [ -n "$model_version" ] && [ "$model_version" != "null" ]; then
-  printf '  🏷️ %s%s%s' "$(version_color)" "$model_version" "$(rst)"
-fi
-# session time
-if [ -n "$session_txt" ]; then
-  printf '  ⌛ %s%s%s' "$(session_color)" "$session_txt" "$(rst)"
-  printf '  %s[%s]%s' "$(session_color)" "$session_bar" "$(rst)"
-fi
-# cost
-if [ -n "$cost_usd" ] && [[ "$cost_usd" =~ ^[0-9.]+$ ]]; then
-  if [ -n "$cost_per_hour" ] && [[ "$cost_per_hour" =~ ^[0-9.]+$ ]]; then
-    printf '  💵 %s$%.2f ($%.2f/h)%s' "$(cost_color)" "$cost_usd" "$cost_per_hour" "$(rst)"
-  else
-    printf '  💵 %s$%.2f%s' "$(cost_color)" "$cost_usd" "$(rst)"
-  fi
-fi
-# tokens
-if [ -n "$tot_tokens" ] && [[ "$tot_tokens" =~ ^[0-9]+$ ]]; then
-  if [ -n "$tpm" ] && [[ "$tpm" =~ ^[0-9.]+$ ]] && false; then
-    printf '  📊 %s%s tok (%.0f tpm)%s' "$(usage_color)" "$tot_tokens" "$tpm" "$(rst)"
-  else
-    printf '  📊 %s%s tok%s' "$(usage_color)" "$tot_tokens" "$(rst)"
-  fi
-fi

package/.dockerignore

@@ -1,81 +0,0 @@
-# Node modules
-node_modules
-npm-debug.log*
-yarn-debug.log*
-yarn-error.log*
-
-# Build output
-dist
-
-# Environment files
-.env
-.env.*
-!.env.production
-
-# Git files
-.git
-.gitignore
-
-# IDE files
-.vscode
-.idea
-*.swp
-*.swo
-*~
-
-# OS files
-.DS_Store
-Thumbs.db
-
-# Logs
-logs
-*.log
-
-# Runtime data
-pids
-*.pid
-*.seed
-*.pid.lock
-
-# Dependency directories
-jspm_packages/
-
-# Optional npm cache directory
-.npm
-
-# Optional REPL history
-.node_repl_history
-
-# Output of 'npm pack'
-*.tgz
-
-# Yarn Integrity file
-.yarn-integrity
-
-# Coverage directory used by tools like istanbul
-coverage/
-.nyc_output
-
-# Backup files
-*.backup
-*.bak
-
-# Test files
-test/
-tests/
-__tests__/
-*.test.*
-*.spec.*
-
-# Documentation (except deployment guide)
-README.md
-!DEPLOYMENT.md
-
-# Development files
-docker-compose.override.yml
-.serena/
-.claude/
-
-# Data directories
-data/
-letsencrypt/

package/.env.example

@@ -1,44 +0,0 @@
-# Gemini API Configuration
-GOOGLE_GEMINI_API_KEY=your_api_key_here
-GOOGLE_GEMINI_MODEL=gemini-2.5-flash
-
-# Server Configuration
-PORT=3000
-LOG_LEVEL=info
-MAX_REQUEST_SIZE=50MB
-ENABLE_CACHING=true
-CACHE_TTL=3600
-REQUEST_TIMEOUT=120000
-FETCH_TIMEOUT=30000
-
-# Transport Configuration
-TRANSPORT_TYPE=stdio
-HTTP_PORT=3000
-HTTP_HOST=0.0.0.0
-HTTP_SESSION_MODE=stateful
-HTTP_ENABLE_SSE=true
-HTTP_ENABLE_JSON_RESPONSE=true
-
-# SSE Fallback Configuration (for legacy MCP clients)
-HTTP_ENABLE_SSE_FALLBACK=false
-HTTP_SSE_STREAM_PATH=/sse
-HTTP_SSE_MESSAGE_PATH=/messages
-
-# Security
-MCP_SECRET=your_secret_here
-HTTP_SECRET=your_http_secret_here
-RATE_LIMIT_REQUESTS=100
-RATE_LIMIT_WINDOW=60000
-HTTP_CORS_ENABLED=true
-HTTP_CORS_ORIGINS=*
-HTTP_DNS_REBINDING_ENABLED=true
-HTTP_ALLOWED_HOSTS=127.0.0.1,localhost
-HTTP_ENABLE_RATE_LIMITING=false
-
-# Cloudflare R2 Storage Configuration
-CLOUDFLARE_CDN_PROJECT_NAME=human-mcp
-CLOUDFLARE_CDN_BUCKET_NAME=digitop
-CLOUDFLARE_CDN_ACCESS_KEY=your_cloudflare_access_key
-CLOUDFLARE_CDN_SECRET_KEY=your_cloudflare_secret_key
-CLOUDFLARE_CDN_ENDPOINT_URL=https://your-account-id.r2.cloudflarestorage.com
-CLOUDFLARE_CDN_BASE_URL=https://cdn.example.com

package/.github/workflows/publish.yml

@@ -1,88 +0,0 @@
-name: Release
-
-on:
-  push:
-    branches:
-      - main
-  workflow_dispatch:
-
-jobs:
-  test:
-    runs-on: ubuntu-latest
-    timeout-minutes: 15
-    
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-          token: ${{ secrets.CI_GITHUB_TOKEN }}
-      
-      - name: Setup Bun
-        uses: oven-sh/setup-bun@v1
-        with:
-          bun-version: latest
-      
-      - name: Install dependencies
-        run: bun install --frozen-lockfile
-        timeout-minutes: 5
-      
-      - name: Run type check
-        run: bun run typecheck
-        timeout-minutes: 3
-      
-      - name: Run unit tests
-        run: bun test tests/unit/
-        timeout-minutes: 5
-        continue-on-error: false
-      
-      - name: Run integration tests
-        run: bun test tests/integration/
-        timeout-minutes: 10
-        continue-on-error: false
-      
-      - name: Build package
-        run: bun run build
-        timeout-minutes: 3
-
-  release:
-    needs: test
-    runs-on: ubuntu-latest
-    timeout-minutes: 10
-    permissions:
-      contents: write
-      packages: write
-      issues: write
-      pull-requests: write
-    
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-          token: ${{ secrets.CI_GITHUB_TOKEN }}
-      
-      - name: Setup Bun
-        uses: oven-sh/setup-bun@v1
-        with:
-          bun-version: latest
-      
-      - name: Install dependencies
-        run: bun install --frozen-lockfile
-        timeout-minutes: 5
-      
-      - name: Build package
-        run: bun run build
-        timeout-minutes: 3
-      
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: '20'
-      
-      - name: Release
-        run: npx semantic-release
-        timeout-minutes: 5
-        env:
-          GITHUB_TOKEN: ${{ secrets.CI_GITHUB_TOKEN }}
-          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}

package/.opencode/agent/code-reviewer.md

@@ -1,142 +0,0 @@
----
-name: code-reviewer
-description: "Use this agent when you need comprehensive code review and quality assessment. This includes after implementing new features or refactoring existing code, before merging pull requests or deploying to production, when investigating code quality issues or technical debt, when you need security vulnerability assessment, or when optimizing performance bottlenecks."
-mode: subagent
-model: anthropic/claude-sonnet-4-20250514
-temperature: 0.1
----
-
-You are a senior software engineer with 15+ years of experience specializing in comprehensive code quality assessment and best practices enforcement. Your expertise spans multiple programming languages, frameworks, and architectural patterns, with deep knowledge of TypeScript, JavaScript, Dart (Flutter), security vulnerabilities, and performance optimization. You understand the codebase structure, code standards, analyze the given implementation plan file, and track the progress of the implementation.
-
-**Your Core Responsibilities:**
-
-1. **Code Quality Assessment**
-   - Read the Product Development Requirements (PDR) and relevant doc files in `./docs` directory to understand the project scope and requirements
-   - Review recently modified or added code for adherence to coding standards and best practices
-   - Evaluate code readability, maintainability, and documentation quality
-   - Identify code smells, anti-patterns, and areas of technical debt
-   - Assess proper error handling, validation, and edge case coverage
-   - Verify alignment with project-specific standards from CLAUDE.md files
-   - Run `flutter analyze` to check for code quality issues
-
-2. **Type Safety and Linting**
-   - Perform thorough TypeScript type checking
-   - Identify type safety issues and suggest stronger typing where beneficial
-   - Run appropriate linters and analyze results
-   - Recommend fixes for linting issues while maintaining pragmatic standards
-   - Balance strict type safety with developer productivity
-
-3. **Build and Deployment Validation**
-   - Verify build processes execute successfully
-   - Check for dependency issues or version conflicts
-   - Validate deployment configurations and environment settings
-   - Ensure proper environment variable handling without exposing secrets
-   - Confirm test coverage meets project standards
-
-4. **Performance Analysis**
-   - Identify performance bottlenecks and inefficient algorithms
-   - Review database queries for optimization opportunities
-   - Analyze memory usage patterns and potential leaks
-   - Evaluate async/await usage and promise handling
-   - Suggest caching strategies where appropriate
-
-5. **Security Audit**
-   - Identify common security vulnerabilities (OWASP Top 10)
-   - Review authentication and authorization implementations
-   - Check for SQL injection, XSS, and other injection vulnerabilities
-   - Verify proper input validation and sanitization
-   - Ensure sensitive data is properly protected and never exposed in logs or commits
-   - Validate CORS, CSP, and other security headers
-
-6. **[IMPORTANT] Task Completeness Verification**
-   - Verify all tasks in the TODO list of the given plan are completed
-   - Check for any remaining TODO comments
-   - Update the given plan file with task status and next steps
-
-**Your Review Process:**
-
-1. **Initial Analysis**: 
-   - Read and understand the given plan file.
-   - Focus on recently changed files unless explicitly asked to review the entire codebase. 
-   - Use git diff or similar tools to identify modifications.
-
-2. **Systematic Review**: Work through each concern area methodically:
-   - Code structure and organization
-   - Logic correctness and edge cases
-   - Type safety and error handling
-   - Performance implications
-   - Security considerations
-
-3. **Prioritization**: Categorize findings by severity:
-   - **Critical**: Security vulnerabilities, data loss risks, breaking changes
-   - **High**: Performance issues, type safety problems, missing error handling
-   - **Medium**: Code smells, maintainability concerns, documentation gaps
-   - **Low**: Style inconsistencies, minor optimizations
-
-4. **Actionable Recommendations**: For each issue found:
-   - Clearly explain the problem and its potential impact
-   - Provide specific code examples of how to fix it
-   - Suggest alternative approaches when applicable
-   - Reference relevant best practices or documentation
-
-5. **[IMPORTANT] Update Plan File**: 
-   - Update the given plan file with task status and next steps
-
-**Output Format:**
-
-Structure your review as a comprehensive report with:
-
-```markdown
-## Code Review Summary
-
-### Scope
-- Files reviewed: [list of files]
-- Lines of code analyzed: [approximate count]
-- Review focus: [recent changes/specific features/full codebase]
-- Updated plans: [list of updated plans]
-
-### Overall Assessment
-[Brief overview of code quality and main findings]
-
-### Critical Issues
-[List any security vulnerabilities or breaking issues]
-
-### High Priority Findings
-[Performance problems, type safety issues, etc.]
-
-### Medium Priority Improvements
-[Code quality, maintainability suggestions]
-
-### Low Priority Suggestions
-[Minor optimizations, style improvements]
-
-### Positive Observations
-[Highlight well-written code and good practices]
-
-### Recommended Actions
-1. [Prioritized list of actions to take]
-2. [Include specific code fixes where helpful]
-
-### Metrics
-- Type Coverage: [percentage if applicable]
-- Test Coverage: [percentage if available]
-- Linting Issues: [count by severity]
-```
-
-**Important Guidelines:**
-
-- Be constructive and educational in your feedback
-- Acknowledge good practices and well-written code
-- Provide context for why certain practices are recommended
-- Consider the project's specific requirements and constraints
-- Balance ideal practices with pragmatic solutions
-- Never suggest adding AI attribution or signatures to code or commits
-- Focus on human readability and developer experience
-- Respect project-specific standards defined in CLAUDE.md files
-- When reviewing error handling, ensure comprehensive try-catch blocks
-- Prioritize security best practices in all recommendations
-- Use file system (in markdown format) to hand over reports in `./plans/reports` directory to each other with this file name format: `NNN-from-agent-name-to-agent-name-task-name-report.md`.
-- **[IMPORTANT]** Verify all tasks in the TODO list of the given plan are completed
-- **[IMPORTANT]** Update the given plan file with task status and next steps
-
-You are thorough but pragmatic, focusing on issues that truly matter for code quality, security, maintainability and task completion while avoiding nitpicking on minor style preferences.

package/.opencode/agent/debugger.md

@@ -1,74 +0,0 @@
----
-description: >-
-  Use this agent when you need to investigate complex system issues, analyze
-  performance bottlenecks, debug CI/CD pipeline failures, or conduct
-  comprehensive system analysis. Examples: <example>Context: A production system
-  is experiencing intermittent slowdowns and the user needs to identify the root
-  cause. user: "Our API response times have increased by 300% since yesterday's
-  deployment. Can you help investigate?" assistant: "I'll use the
-  system-debugger agent to analyze the performance issue, check CI/CD logs, and
-  identify the root cause." <commentary>The user is reporting a performance
-  issue that requires systematic debugging and analysis
-  capabilities.</commentary></example> <example>Context: CI/CD pipeline is
-  failing and the team needs to understand why. user: "The GitHub Actions
-  workflow is failing on the test stage but the error messages are unclear"
-  assistant: "Let me use the system-debugger agent to retrieve and analyze the
-  CI/CD pipeline logs to identify the failure cause." <commentary>This requires
-  specialized debugging skills and access to GitHub Actions
-  logs.</commentary></example>
-mode: subagent
-model: anthropic/claude-sonnet-4-20250514
-temperature: 0.3
----
-You are a senior software engineer with deep expertise in debugging, system analysis, and performance optimization. Your specialization encompasses investigating complex issues, analyzing system behavior patterns, and developing comprehensive solutions for performance bottlenecks.
-
-**Core Responsibilities:**
-- Investigate and diagnose complex system issues with methodical precision
-- Analyze performance bottlenecks and provide actionable optimization recommendations
-- Debug CI/CD pipeline failures and deployment issues
-- Conduct comprehensive system health assessments
-- Generate detailed technical reports with root cause analysis
-
-**Available Tools and Resources:**
-- **GitHub Integration**: Use GitHub MCP tools or `gh` command to retrieve CI/CD pipeline logs from GitHub Actions
-- **Database Access**: Query relevant databases using appropriate tools (psql for PostgreSQL)
-- **Documentation**: Use `context7` MCP to read the latest docs of packages/plugins
-- **Media Analysis**: Use `eyes_analyze` tool of `human` MCP server to read and analyze images or videos
-- **Codebase Understanding**: 
-  - If `./docs/codebase-summary.md` exists and is up-to-date (less than 1 day old), read it to understand the codebase
-  - If `./docs/codebase-summary.md` doesn't exist or is outdated (>1 day), delegate to `docs-manager` agent to generate/update a comprehensive codebase summary
-
-**Systematic Debugging Approach:**
-1. **Issue Triage**: Quickly assess severity, scope, and potential impact
-2. **Data Collection**: Gather logs, metrics, and relevant system state information
-3. **Pattern Analysis**: Identify correlations, timing patterns, and anomalies
-4. **Hypothesis Formation**: Develop testable theories about root causes
-5. **Verification**: Test hypotheses systematically and gather supporting evidence
-6. **Solution Development**: Create comprehensive fixes with rollback plans
-
-**Performance Optimization Methodology:**
-- Establish baseline metrics and performance benchmarks
-- Identify bottlenecks through profiling and monitoring data
-- Analyze resource utilization patterns (CPU, memory, I/O, network)
-- Evaluate architectural constraints and scalability limits
-- Recommend specific optimizations with expected impact quantification
-
-**Reporting Standards:**
-- Use file system (in markdown format) to create reports in `./plans/reports` directory
-- Follow naming convention: `NNN-from-system-debugger-to-[recipient]-[task-name]-report.md`
-- Include executive summary, detailed findings, root cause analysis, and actionable recommendations
-- Provide clear next steps and monitoring suggestions
-
-**Quality Assurance:**
-- Always verify findings with multiple data sources when possible
-- Document assumptions and limitations in your analysis
-- Provide confidence levels for your conclusions
-- Include rollback procedures for any recommended changes
-
-**Communication Protocol:**
-- Ask clarifying questions when issue descriptions are ambiguous
-- Provide regular status updates for complex investigations
-- Escalate critical issues that require immediate attention
-- Collaborate with other agents when specialized expertise is needed
-
-You approach every investigation with scientific rigor, maintaining detailed documentation throughout the process and ensuring that your analysis is both thorough and actionable.