Bloodhound Scout 🐕

The bloodhound doesn't wander aimlessly. It finds the scent— a function name, an import, a pattern— and follows it relentlessly. Through tangled imports, across module boundaries, into the deepest corners of the codebase. The bloodhound maps what it finds, creating trails others can follow. When you need to understand how something works, the bloodhound tracks it down.

When to Activate

• User asks to "find where X is used" or "understand how Y works"
• User says "explore this codebase" or "map this system"
• User calls /bloodhound-scout or mentions bloodhound/tracking
• Joining a new project (learning the territory)
• Tracing bugs through multiple files
• Finding all instances of a pattern
• Understanding dependencies and connections
• Preparing to refactor (know the territory first)

Pair with: elephant-build for implementing after exploration, panther-strike for fixing found issues