investigate

Run a read-only investigation that parses your query, lists the target directory structure, reads entrypoints like package.json and README, then greps for usages and follows import chains. The result is a structured fact report with file paths, patterns, and dependencies.

Search for the functions or components in question, follow their call sites and import chains, and record both what the area depends on and what depends on it. The investigation report lists these dependencies explicitly with concrete file paths.

No. This investigation protocol is strictly read-only: it must not create plans, write code, or refactor anything. It only reads files, searches for patterns, and reports facts.

A useful report includes files found with full paths, architectural patterns in play, dependencies in both directions, and constraints discovered such as locked APIs, shared types, and existing conventions that would limit future implementation.

Investigate whenever you need established facts before deciding, such as understanding how something works or identifying what files are involved. Once facts are gathered, you can hand the findings to a planning step to build a phased implementation plan.