investigate

To find the root cause of a performance regression, this investigation systematically traces evidence trails across code, architecture, and data using a structured workflow. It applies detective-style analysis to uncover hidden defects and design gaps, outputting a detailed case report.

Debugging architectural inconsistencies is best handled by applying three investigative lenses—deduction, intent analysis, and edge-case discovery—to systematically surface hidden problems. It evaluates code and deployments to identify structural design gaps and present actionable findings.

To trace a defect through a data pipeline, start at Phase 0 to establish the case, then follow the evidence trail across systems using read-only access. The workflow systematically uncovers bugs and inconsistencies, concluding with an auto-generated case report.

Yes, you can investigate production issues with read-only access using tools like Read, Grep, and Glob. The investigation requires only read-only guidance to systematically uncover root causes and inform decisions without modifying the deployment environment.

Use a structured investigation workflow for code analysis when tracing complex defects, performance regressions, or design gaps across codebases and systems. It is necessary when you need repeatable, phase-driven detective analysis to surface hidden problems and intent gaps.