engineering-dev-clarify-requirements

What problem does it solve? Ambiguous or underspecified requests often lead developers and AI agents to build the wrong thing, wasting effort on work that must be redone. This Skill inserts an intake gate that detects ambiguity and asks the minimum set of sharp questions before any implementation begins. ## Core Features & Use Cases - Ambiguity Detection: Evaluates requests against six dimensions (objective, definition of done, scope, constraints, environment, safety) to decide whether clarification is needed. - Minimal Question Sets: Produces 1-5 short, numbered, multiple-choice questions with recommended defaults and a fast-path defaults reply option. - Implementation Hold: Blocks commands, edits, and dependent plans until must-have answers arrive or the user confirms stated assumptions. - Use Case: A user asks to "add caching to the API." Instead of guessing, the agent asks which endpoints are in scope, what TTL is acceptable, and whether existing infrastructure must be reused, then restates the confirmed interpretation before coding. ## Quick Start Ask the agent to clarify the requirements and scope of this task before writing any code.