When to choose it
Finding the files and behavior relevant to a planned change.
Choose it if: You want to trace an existing feature’s entry points, execution path and related files before planning a change.
Look elsewhere if: You need a runtime trace or execution proof; the agent’s code-reading conclusions still need verification.
What the source describes
- Entry-point and execution-path analysis
- Maps related files and dependencies
- Reports findings for the main feature workflow
Requirements
- Install the containing Feature Dev package
This is a component of Feature Dev. Install the containing package once to get its components.
Install the containing plugin
Run the installation command in your shell after reviewing the source. Local scope enables the package for you in this repository. It does not enable it for every collaborator.
claude plugin install feature-dev@claude-plugins-official --scope localUse it after installation
Ask Claude to use Feature Dev’s code-explorer to trace a named behavior.
Installation and loading troubleshootingLimitations & considerations
- Code reading can overlook dynamic behavior
- Its conclusions still need verification against the relevant files
Source & review record
Our description is based on the public source documentation and manifest available on 2026-10-05. The install syntax was checked against Claude Code’s documentation. No extension code was executed for this review.