understanding-assumption-surface

Surface and verify implicit assumptions in code and design before they cause problems. Use when: (1) asked to surface assumptions or verify claims against code, (2) language patterns reveal claims unsupported by examined evidence—using "this should" or "the system guarantees" without citing specific code, or qualifying statements with "probably" or "I think" while asserting concrete behavior, (3) making claims about code you haven't examined recently, (4) reasoning from general patterns about how software typically works rather than investigating how this particular codebase actually works, (5) planning changes that depend on properties you haven't verified, (6) building on claims from earlier in the conversation without checking them, (7) estimating impact based on assumptions about architecture or dependencies that exist only in your reasoning rather than in verified artifacts