assumptions-checklisted

# Key Assumptions Check Surface what's being taken for granted. Test it. Break what's fragile before it breaks you. ## Core Principle Every plan, design, and decision rests on assumptions -- most of them invisible. This skill makes them visible, rates their strength, and identifies which ones need evidence or testing before you proceed. ## When to Use Use when an assumptions inventory is the requested deliverable, or a specific unverified assumption warrants this technique. Do not run a separate inventory for every non-trivial decision. Examples within that scope: - Before committing to an architecture or technology bet - When a plan feels "obviously right" (that's when assumptions hide best) - When reviewing code that makes implicit guarantees - When someone says "that won't be a problem" without evidence - When inherited designs carry forward without re-examination ## The Process ### Step 1: Extract Assumptions Read the plan/code/design and list every assumption -- stated or implied. Look for assumptions in these categories: | Category | What to look for | |----------|-----------------| | **Technical** | "This library handles X", "The database can handle Y load", "This API is reliable" | | **User** | "Users will do X", "Users understand Y", "Users won't do Z" | | **Business** | "We have time for X", "The market wants Y", "Competitors won't Z" | | **Team** | "We have expertise in X", "We can hire for Y", "This won't need maintenance" | | **Environment** | "Infrast