When you hit a problem and don't know if it's a config issue, a code path bug, or just bad assumptions in how you're measuring it, this runs three parallel investigations then feeds what it finds directly into a requirements interview. The trace digs into causality, the interview crystallizes what to build, and the handoff between them is automatic so you don't lose context. It's honestly overkill if you already know the root cause, but when something's broken and you're not sure where to start, having the interview questions pre-seeded with evidence from the trace saves you from re-exploring the same ground twice. Writes a spec to `.omc/specs/` and hands off to the planner.
npx skills add https://github.com/yeachan-heo/oh-my-claudecode --skill deep-dive