interview
Adaptive pre-work clarifier. Picks 2–4 task-specific questions via AskUserQuestion, echoes a brief scope summary, then proceeds. Refuses for trivial tasks. TRIGGER when: /interview invoked explicitly, OR before non-trivial work where scope/intent/constraints are ambiguous AND the user hasn't already specified them.
mifunedev · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add mifunedev/agro --skill interview技能说明
name: interview description: | Adaptive pre-work clarifier. Picks 2–4 task-specific questions via AskUserQuestion, echoes a brief scope summary, then proceeds. Refuses for trivial tasks. TRIGGER when: /interview invoked explicitly, OR before non-trivial work where scope/intent/constraints are ambiguous AND the user hasn't already specified them. argument-hint: "[task description]"
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
/interviewinvoked 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.AskUserQuestionis for picking among options, not approving a finished plan. - About to run
/prdor/spec plan— 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. Proceeding directly.
Do not refuse silently. The skip is a signal, not an absence.
2. Extract what's already known
Read the conversation context. List, internally, what's already specified — goal, files touched, mode, constraints, acceptance. Do not re-ask anything the context already answers. A question whose answer is already in the prompt is a tell that the model didn't read.
3. Pick 2–4 questions
Each question must clear the bar in § Question quality bar below. If you can't write 2 that clear the bar, ask 1 (sequential calls are fine) or skip and announce why. Don't quota-fill to reach 4.
4. Issue one batched AskUserQuestion call
Pass all questions in one tool call. Each options array has 2–4 entries; never 1, never 5+. The user UI auto-adds "Other" — do not add it manually. Use multiSelect: true only when the choices are genuinely not mutually exclusive.
Sequential calls are the rare exception: only when a later question's option set genuinely depends on an earlier answer (e.g., "which file?" depends on "which mode?").
5. Echo a 2–3 sentence scope brief, then proceed
After answers come back, write a 2–3 sentence brief that:
- Names the goal, the chosen path, and any non-default constraints from the answers.
- Surfaces any stated assumption you're making that wasn't in an answer.
- Has no plan-approval gate. Brief, then work.
If the user types STOP during the brief, halt — do not finish the thought, do not start the work.
Question quality bar
Every question must satisfy all of:
- Decision-shaping — the answer changes what gets built, not how it's described. If both options lead to the same code, it's not a question.
- Task-specific options — options reference real files, components, modes, or thresholds from this task. Not "small / medium / large". Not "yes / no / maybe".
- Mutually exclusive — options don't overlap (or set
multiSelect: trueand acknowledge they don't). - Gut-answerable — the user shouldn't need to read code to decide. If they would, the question is too deep — ask a shallower one first or do the reading yourself.
- 2–4 options — never 1 (not a question), never 5+ (decision paralysis). "Other" is automatic.
- Generic-filler ban — refuse to emit: "what are your constraints?", "any preferences?", "any concerns?", "what's your goal?". These are tells the model didn't think hard enough about this task.
Anti-patterns
- Generic filler. Banned (see above). If your question would work verbatim on a different task, it's filler.
- Re-asking the answered. Context already named the file or mode; don't ask again.
- Quota-filling to 4. Two sharp questions beat four mushy ones.
- Plan-approval via
AskUserQuestion. UseExitPlanMode. The two tools are not interchangeable. - Interviewing trivial tasks. Typos, format passes, single-command invocations. Announce the skip and proceed.
- Templated question banks. A "standard 4 questions to ask before any refactor" defeats the adaptive thesis. Pick questions from this task.
- Asking, then ignoring. If the brief doesn't reflect the answers, the interview was theater.
- Brief longer than the answers. The brief is 2–3 sentences. If you need a paragraph, you're writing a plan — use
ExitPlanMode. - Smuggled assumptions. If the brief asserts something the user didn't pick, either surface it as a stated assumption ("Assuming X — say so if not") or ask another question.
- Ignoring STOP. If the user interjects "STOP" while you're writing the brief, halt. Do not finish the thought; do not start the work.
Examples
Example 1 — refactor request
Invocation: /interview refactor the audit skill
BAD (generic filler):
What are your constraints for this refactor? Options: Time-constrained / Quality-first / Other
GOOD (task-specific):
AskUserQuestion:
question: "Which axis of the audit skill is most worth changing?"
header: "Refactor axis"
options:
- label: "Sub-agent prompts"
description: "Tighten PM/Implem
阅读完整来源 ↗