Debug Mode

Use the evidence loop when the root cause is not proven. Avoid plausible fixes that only pass once.

Activation boundary

Reach for this skill — including autonomously, without waiting for the user to name it — when the user explicitly says diagnose/debug, or when a normal reproduction or inspection has not revealed the cause, especially for flaky, environment-specific, or production-only bugs.

Do not enter debug-mode for a compiler/type/lint/test error whose cause is directly in the output, a review finding that already specifies both cause and fix, an already-proven root cause, or when debug-mode is already active. Never re-invoke debug-mode from inside an active debug-mode run — continue the existing evidence loop.