Ask Questions If Underspecified
Ask the minimum set of clarifying questions needed to avoid wrong work; do not start implementing until must-have questions are answered or the user explicitly approves proceeding with stated assumptions.
🚀 Before diving into work, pause and ask clarifying questions if the request is unclear. Identify what's missing—the goal, acceptance criteria, scope, constraints, or environment—then ask 1–5 focused questions to fill the gaps. This prevents wasted effort and wrong implementations.
💡 Use this when requirements have multiple interpretations, edge cases aren't defined, or key details (versions, performance, rollback plans) are unstated. It's especially valuable for code changes, migrations, and feature work where assumptions can derail progress.
✨ By asking upfront, you save time, reduce rework, and deliver exactly what's needed. Offer defaults, multiple-choice options, and a fast-path response to keep friction low.
Requirements
No additional requirements.