dev-debuglisted

# dev-debug ## Overview Systematic debugging. Four phases. No guessing. Bugs tempt you to guess. "Probably this." "Let me just try." "One more thing." Every guess costs time, introduces noise, and drifts you further from the root cause. This skill enforces a discipline: understand first, fix second. ## Announcement When this skill is active, announce: > "I'm using enggenie:dev-debug for systematic root cause investigation." --- ## Hard Rule: No Fixes Without Understanding the Cause First Do NOT propose a fix until you can state: "The bug is caused by X, because I observed Y." No "try this." No "maybe it's." No "let's see if." You state the cause, you show the evidence, then you fix. If you cannot state the cause, you are still in Phase 1. --- ## Phase 1 -- Investigate Gather evidence. Do not interpret yet. Do not fix anything. ### Read Error Messages Completely Read the FULL error output. Not the first line. Not the summary. The whole thing. - Stack trace: every frame. The cause is often 3-4 frames deep, not at the top. - Line numbers: go to the exact line. Read 10 lines above and below. - Error codes: look them up. Error codes exist because the message alone is ambiguous. - Stderr vs stdout: check both. Some failures are silent on stdout. ### Reproduce Consistently Before investigating further, confirm you can reproduce the bug: 1. Write down the exact steps. 2. Run them. Does the bug appear? 3. Run them again. Does it appear every time? 4. If intermittent