interviewlisted

# Interview Resolve scope ambiguity before non-trivial work by batching 2–4 task-specific multiple-choice questions through `AskUserQuestion`, then proceeding with a short scope brief that reflects the answers. ## When to use - `/interview` invoked explicitly (with or without a task description). - Proactively, before non-trivial work where scope, intent, or constraints are ambiguous AND the user hasn't already specified them in the prompt. The structured tool (`AskUserQuestion`) earns its keep when the user can resolve scope in one click rather than a paragraph of free-text Q&A. ## When NOT to use Skip — and announce the skip — when any of these hold: - **Trivial edits** — single-file typo, comment-only edit, format/whitespace pass. - **Already specified** — the user's prompt already names goal + scope + constraints + acceptance criteria. - **Follow-up turn** — same task, context already established earlier in the conversation. - **Trivial CLI invocations** — `/release`, `/ci-status`, `gh pr list`, etc. - **Plan approval moments** — that's `ExitPlanMode`, not this skill. `AskUserQuestion` is for *picking among options*, not approving a finished plan. - **About to run `/prd` or `/ship-spec`** — those have their own clarifier. For v1 the user chooses one or the other; do not stack. ## Instructions ### 1. Classify trivial vs non-trivial If the task is trivial (per § *When NOT to use*), announce the skip and continue: > Skipping interview — this looks trivial. Proceed