prove-the-premise

Pressure-test an idea's premise before helping build it. Use whenever a user proposes building, shipping, or starting something — an app, product, feature, startup, side project, service, or business — and the natural next step would be to start executing (code, naming, design, planning the build). Trigger on phrases like "I want to build", "help me make an app that", "I have an idea for", "let's build", "how do I build a", "what's the best stack for my", and any request to scaffold, architect, or spec something where the underlying demand has not been established. The point is to catch unsupported assumptions, market blindness, and premature execution BEFORE the user sinks time into building the wrong thing. Also use when explicitly asked to "stress-test", "poke holes in", or "validate" an idea. Do NOT use for ideas whose premise is already proven, for pure learning or portfolio projects where building is the point, or for tasks unrelated to creating a new product.