investigate

A detective-style code investigation diagnoses root causes by following evidence trails through phased analysis—Establish Case, Survey Scene, Examine Evidence, Interview Witnesses, Connect Evidence—to surface bugs and hidden problems across code, performance, architecture, data, and systems.

The best way to troubleshoot code inconsistencies across a large software project is applying multi-perspective reasoning—deduction, intent, and persistence—to trace evidence trails and connect findings to root causes across any software project size.

Start diagnosing hidden software problems by loading available evidence and outlining a structured investigation plan that surveys the scene, examines evidence, and connects findings to actionable conclusions.

Yes, you can perform read-only code analysis without modifying the software architecture by using only provided tools like Read, Grep, Glob, Agent, AskUserQuestion, and Bash to follow evidence trails and diagnose issues.

Use a phase-driven investigation workflow for debugging when you need to follow evidence trails across code, performance, architecture, data, and systems to surface hidden problems and edge cases through multi-perspective reasoning.