Skill · Setup and diagnostics
/investigate$investigate@planr-investigate
Diagnose a bug, regression, error, or unexplained behavior and optionally implement a bounded fix. Use for root-cause investigation, not planned feature delivery.
Run it
/investigatein Claude Code. If /investigate runs another command, use /planr:investigate.
$investigatein Codex. With the OpenPlanr plugin for Codex, use $planr:investigate.
@planr-investigatein Cursor. Cursor applies the planr-investigate rule when you mention it in chat.
When to use it
Use it to
- Investigate a bug, regression, error, or unexplained behavior
- Reproduce a defect, establish its root cause, or apply a bounded fix
- Investigate why this fails
Not for
- Plan a new feature
- Run a broad product review
Prompts and commands
Diagnose a failure without changing code
Get the root cause and the evidence for it, with no edits until you decide on a fix.
Find the root cause before you fix it
Reproduce the defect, establish why it happens, then apply a bounded fix.
Track down a flaky test
Find out why a test fails some of the time before anyone changes the test.