What problem does it solve?
It helps you identify why something happened and convert that understanding into a clear set of requirements and an execution plan when you are stuck without a known root cause.
Core Features & Use Cases
- Causal Trace Pipeline: Builds and confirms competing hypotheses by running three trace lanes in parallel, converging on evidence, and saving results to a deep-dive trace spec file.
- Deep Interview with Trace Injection: Translates trace findings into a structured requirements conversation by injecting the most likely explanation, replacing codebase context with synthesized results, and turning per-lane unknowns into the first questions.
- Execution Bridge: Hands off refined outcomes to consensus refinement and an execution autopilot flow (or equivalent options) so you can proceed from investigation to action.
Use Case: You get a bug report like “authentication intermittently fails in production” but logs are ambiguous; you run deep-dive to determine the most likely failure cause and then produce the requirements needed to implement a reliable fix and verification steps.
Quick Start
Say: deep dive, investigate why the authentication errors are happening and interview me with the critical unknowns you find.
