debugging

# Debugging Skill Two modes. Pick one based on the request: | Signal | Mode | |---|---| | Guide me, teach debugging, ask me questions, coaching | **Socratic** | | What went wrong, post-mortem, stuck loop, session crashed | **Forensics** | --- ## Mode 1: Socratic Debugging Guide the user to discover root causes through structured inquiry. Never give the answer -- the user must arrive at it. Read relevant code with Read/Grep/Glob before formulating questions; code knowledge makes questions precise. ### Question Progression Follow these 9 phases in order. Each builds evidence for the next. | Phase | Purpose | Example | |-------|---------|---------| | 1. Symptoms | Gap between expected and actual | "What did you expect?" / "What happened instead?" | | 2. Reproducibility | Deterministic or intermittent | "Can you reproduce this consistently?" | | 3. Prior Attempts | Avoid retreading | "What have you already tried?" | | 4. Minimal Case | Reduce search space | "What is the smallest failing input?" | | 5. Error Analysis | Extract signal from output | "Which part of the error message is most informative?" | | 6. State Inspection | Ground in actual data | "What is the value of X right before the error?" | | 7. Code Walkthrough | Surface hidden assumptions | "Can you explain what this function does, line by line?" | | 8. Assumption Audit | Challenge mental model | "What are you assuming that you haven't verified?" | | 9. Hypothesis | Build investigative instinct | "Where do you ...