investigation-mode

Debug persistent build errors by activating a systematic investigation protocol that pauses execution after two consecutive failures, gathers diagnostic evidence, and performs root cause analysis before applying fixes.

Troubleshooting errors systematically requires pausing development to gather evidence and identify the underlying root cause, ensuring you only resume work after creating a verified plan and receiving explicit approval.

Root cause analysis for unclear problem statements works by initiating a deep research phase that collects diagnostic evidence, traces the underlying issue, and presents evidence-based solutions rather than quick patches.

You need a structured investigation protocol for error handling when encountering persistent failures, repeated test failures, or development stagnation that requires evidence-based solutions instead of superficial patches.

You cannot resume coding automatically after root cause analysis; controlled resumption mandates pausing, gathering evidence, and seeking explicit user approval for any significant direction changes before applying fixes.

Your development process halts after multiple consecutive test failures because the error handling protocol automatically pauses execution to prevent aimless coding and ensure root cause analysis is performed.