What problem does it solve?
It helps you debug failures systematically by locating the underlying root cause before making any changes, so you stop whack-a-mole fixes that break again later.
Core Features & Use Cases
- Root-cause first debugging: Turns symptoms (errors, logs, and behavior) into a specific, testable hypothesis about what’s actually wrong.
- Evidence-driven verification: Confirms or rejects hypotheses by adding targeted checks and re-running the reproduction path.
- Controlled implementation: Applies a minimal change once the root cause is confirmed, then verifies it and documents the outcome.
- Uses when you want to debug this/fix this bug/figure out why it’s broken, including troubleshooting regressions, intermittent issues, or configuration drift.
Quick Start
Use investigate when you paste the error and reproduce steps, then ask: Investigate this failure and tell me the most likely root cause and the smallest verified fix.