deep-interviewlisted

# Deep Interview Vague requirements produce confidently wrong software. This skill refuses to start building until the ambiguity is low enough that building is safe. ## Invoked on purpose? Then run. **An explicit invocation is a decision already made.** The user typed the command, so the question of whether to interview is settled. Do not re-open it, and do not answer a request to be interviewed with a paragraph explaining that the request was clear. That is the most annoying possible response to being asked for help. Score the ambiguity anyway. The score is cheap, it is the gate the rest of this skill runs on, and it answers the question better than a judgement call. A genuinely specific request scores at or below the threshold in one pass, and you proceed to the spec with the score shown. That is a two-line answer, not a refusal. ## When this is the wrong tool This guard is for the case where nothing was invoked and you are deciding yourself. Stop and say so if the request is already specific. Interviewing someone who has already told you exactly what they want is not diligence, it is friction. A one-line bug fix does not need a spec. ## Procedure ### 1. Score the ambiguity before asking anything Rate each dimension 0–3, where 0 is "fully specified" and 3 is "no information": | Dimension | The question it answers | |---|---| | **Outcome** | What is true when this is done? | | **Scope** | What is explicitly *not* included? | | **Users** | Who uses this, and in what