Grounding before coding REQUIRED BACKGROUND: the skill. Overview Before writing a spec, a fix, or a first line: map the real code and data. Quote and run the query behind every number you rely on. The discipline 1. Read the implementations, not the names. A method called that does not validate is the default assumption. Verify what a thing does before building on what it is called. 2. Quote your evidence. Every load-bearing claim in your plan gets a , an exact query result, or a command output. When you cannot back a claim, say so out loud instead of assuming it. 3. Never guess conventions. H…