Clarify

This skill is guidance, not a script. Clarify enough to make the next engineering decision. An already clear request needs no interview.

When not to use

• Open-ended exploration the user wants to think through. Use grilling.
• A factual gap the code or documentation already answers; investigate it yourself.
• A low-impact, reversible detail: state a reasonable assumption instead.

Inputs and authorization

• Required: the request, plus the code and conversation already available. Reuse settled answers.
• Authorization: a request to discuss stops at discussion. Do not add an approval ritual, and do not implement beyond the existing authorization.

Method

Read the conversation and inspect relevant implementation first. Facts available in the code are yours to investigate; product intent and consequential tradeoffs belong with the user.