questions▌

Ask clarifying questions before implementing when requirements are ambiguous or incomplete. \n \n Use when a request has multiple plausible interpretations or missing details around objective, scope, constraints, environment, or safety; skip it when the request is already clear or a quick discovery read resolves unknowns \n Ask 1–5 must-have questions in the first pass, prioritizing those that eliminate whole branches of work; offer multiple-choice options and suggested defaults to reduce fricti

Ask the minimum set of clarifying questions needed to avoid wrong work; do not start implementing until the must-have questions are answered (or the user explicitly approves proceeding with stated assumptions).