Debug Triage

Use this skill to localize an unknown failing layer or investigate a known component. For an unknown layer, collect evidence before proposing a fix. For a known component, use the mode below; the host systematic-debugging skill can supplement it if installed.

When to use

• A known component fails or regresses and needs a reproducible root-cause investigation
• A live service is down or degraded and the failing layer is not yet known ("it's broken", "502s started", "pods CrashLooping", "users report timeouts")
• An outage spans multiple layers (DNS, network, ingress, app, data, secrets) and you need to find which one before going deep
• Post-deploy or post-change breakage where the blast radius is unclear
• You are about to start guessing fixes - stop and localize first

When NOT to use