What problem does it solve? When production systems fail or degrade, engineers often jump straight into raw logs and guess at causes, wasting time and missing the real root cause. This Skill provides a structured five-phase SRE investigation methodology that enforces evidence-based reasoning before conclusions. ## Core Features & Use Cases - Systematic 5-Phase Workflow: Scope the problem, gather statistics-first evidence, form ranked hypotheses, test them, and conclude with a structured root-cause report. - Tool-Guided Evidence Gathering: Directs use of Datadog and CloudWatch metrics, anomaly detection, change-point analysis, log aggregation, and Kubernetes pod events before raw logs. - Structured Conclusions: Produces root cause statements with supporting evidence, confidence levels, remediation actions, and explicit caveats. - Use Case: A latency spike hits your API after a deployment. The Skill walks you through correlating metrics, finding the change point, checking pod events, and ranking hypotheses before declaring a cause. ## Quick Start Investigate the current latency spike in the payments service and identify the root cause with supporting evidence.
