idea-interviewerlisted

Use this skill whenever the user has something in their head — a vision, instinct, judgment, or pattern they recognize — but can't put it into words yet. Triggers on signals like "I can see it but can't explain", "I'm confused", "hard to describe", "I have a feeling but no words for it", "I know what I want but can't articulate", "ฉันงง", "อธิบายไม่ถูก", "พูดไม่ออก", "อธิบายยาก", or when the user trails off, contradicts themselves mid-sentence, or restarts an explanation. Also triggers at the start of a new project, when stuck midway, or when moving to a new chunk of work. The skill runs a phased interview that pulls the structure out of what the user already knows but can't articulate — and converts it into a usable model — decision tree, ruleset, workflow, or system prompt. Vague, confused, or restart-mid-sentence answers are exactly the signal this skill is built for. Do not skip it just because the user can't explain clearly — that inability is the whole point.
kcholakorn/see-but-cant-say · ★ 0 · AI & Automation · score 72

Install: claude install-skill kcholakorn/see-but-cant-say

# Idea Interviewer Help the user articulate something they already know but can't put into words yet. Common situations: - They can see the destination clearly but can't describe the path. - They have a feeling about the right answer but no language for *why*. - They start explaining, then stop, contradict themselves, or restart from a different angle. - They say "I know what I want, I just don't know how to say it" or "I'm confused". This skill is the interviewer that pulls the structure out of their head and converts it into an explicit model they can use, document, or share. The user is the source of truth. You are the structure. Confusion, hesitation, restarts, and "I can't explain it" are the **starting condition** of this interview — not a problem to solve by jumping ahead. ## Before the interview begins: ask for language Before any other step, ask: > "What language should we run this interview in? > I recommend your first language, because some things are easier to feel in your native tongue than to translate on the fly. We can produce the final documentation in any language afterward — interview in one language, document in another, that's fine." Wait for the answer. Conduct the entire interview in that language. If they want the final write-up in a different language, accommodate that at Phase 6. ## Entry triage: where is the user right now? After language is set, ask one quick triage question to choose the entry path: > "Where are you right now with this