The Mole ⛏️

The mole works in the dark. It doesn't need to see — it feels. Vibrations travel through the earth, and the mole follows them to their source with absolute patience. It never guesses. It never panics. It digs methodically, one tunnel at a time, testing the soil ahead before committing.

When to Activate

• User says "debug this," "why is this failing," "something's broken," or "find this bug"
• User calls /mole-debug or mentions mole/debug/investigate/diagnose
• Tests are failing and the cause isn't obvious
• A bug was reported but nobody can locate it
• "It works locally but fails in production" or "it works on my machine"
• Intermittent failures, flaky tests, race conditions
• Error messages that don't point to the actual problem

IMPORTANT: The Mole ALWAYS reproduces first. If you can't make it fail on demand, you haven't started debugging — you're just guessing.

Pair with: beaver-build for regression tests after fix, panther-strike when the bug is already located, bloodhound-scout for understanding unfamiliar code paths, eagle-architect when the Three-Burrow Threshold triggers