incident-analyzing

Root cause analysis and impact assessment for active incidents. Use this skill after triage has classified severity, or directly when a developer pastes a stack trace, error log, or describes unexpected system behavior and wants to understand WHY it's happening. Applies structured causal hypothesis testing — not correlation — to identify the origin of failures in distributed systems, monoliths, CI pipelines, or local dev environments. Reads topology and failure pattern references to match symptoms to known failure classes. Produces a confirmed causal chain and blast radius assessment ready for handoff to remediation. Trigger when the developer says things like "why is this happening", "what's the root cause", "help me debug this", or pastes a raw stack trace.