debug-root-causelisted

# Root Cause Analysis I'll help you identify the root cause of issues through systematic dependency tracing and call stack analysis. **Based on obra/superpowers methodology:** - Trace error origins through call stacks - Dependency graph analysis - Configuration issue detection - Environment variable problems - State corruption identification **Quick Start:** Systematic root cause analysis through dependency tracing, call stack analysis, and hypothesis-driven debugging. Optimized for fast feedback with progressive depth. **Arguments:** `$ARGUMENTS` - error message, stack trace, or issue description ## Extended Thinking for Root Cause Analysis <think> Root cause analysis requires systematic investigation: - Error symptoms vs actual cause - Dependencies and their interaction - Configuration cascades - Environment-specific behavior - Timing and state issues Complex scenarios: - Multi-layer stack traces - Transitive dependency failures - Environment variable propagation - Database connection cascades - API timeout chains - Memory corruption patterns - Race conditions in concurrent code </think> ## Phase 1: Error Information Gathering I'll collect comprehensive error context: ```bash #!/bin/bash # Root Cause Analysis - Error Context Gathering echo "=== Root Cause Analysis ===" echo "" echo "Gathering error information..." # Create analysis directory mkdir -p .claude/debugging/root-cause ANALYSIS_DIR=".claude/debugging/root-cause" TIMESTAMP=$(date +%Y%m%d-%H%M%S) REPORT=