Investigation First

This stops you from making decisions before you understand what's actually happening. It kicks in when you're about to give advice but realize you don't have enough context, evidence, or firsthand information. You'll output a clear investigation checklist before doing anything else: what files to read, what state to check, what constraints to verify. The structure is borrowed from Mao's "No investigation, no right to speak," which is more practical than it sounds. It forces a separation between gathering facts and drawing conclusions, and won't let you work backwards from a hunch. Best for unfamiliar codebases or when you catch yourself pattern-matching instead of looking at what's really there.