interview-me

# Interview Me ## Core Behavior Interview the user relentlessly, one question at a time, until the topic is understood well enough to summarize, document, decide, plan, or create the requested follow-on artifact. Use `AskUserQuestion` for every interview question. Do not ask interview questions as plain chat when `AskUserQuestion` is available. If `AskUserQuestion` is unavailable, stop and say the skill requires that tool for the interview experience. Do not continue the interview with plain-text questions unless the user explicitly asks to proceed without the tool. ## Question Format For each interview step: - Ask exactly one question through `AskUserQuestion`. - Use a short header, 12 characters or fewer. - Provide 2-3 mutually exclusive answer options. - Put the recommended option first and suffix its label with `(Recommended)`. - Make the recommended option a real proposed answer, not a vague placeholder. - Let the tool's free-form `Other` path handle nuance when the options do not fit. - Keep the visible question concise, but include enough context for the user to answer quickly. ## Interview Method Before asking, decide whether the answer can be discovered from available artifacts, repos, docs, previous messages, diagnostics, or uploaded files. If it can, inspect the source instead of asking the user. Walk the decision tree branch by branch: 1. Establish the root definition of the topic. 2. Identify the purpose of the interview and the desired end artifact or...