Hypothesize Before Fix

Instructions

Never write fix code before explicitly stating and validating a root cause hypothesis. This prevents wasted effort on incorrect assumptions and encourages deeper understanding.

Step 1: Gather Symptoms

Before forming any hypothesis, collect all available evidence:

• Error messages: Exact text, error codes, stack traces
• Observed behavior: What actually happens
• Expected behavior: What should happen
• Reproduction steps: How to trigger the bug
• Context: When it started, what changed, who is affected

Document symptoms clearly: