采访我
- 作者仓库星标 48,015
- 作者仓库 agent-skills
- 领域
- 数据
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @addyosmani · 未声明许可证
- 上下文用量评级
- 中等消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 命令执行
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
在询问任何问题之前,用一句话写下您当前对用户需求的最佳解读,加上诚实的置信度数字 (0–100%):该数字强制诚实。如果您写下一个很大的数字,但实际上无法预测用户对您接下来提出的三个问题的反应,则该数字是错误的。从你可以捍卫的信心水平开始。当置信度低于 70% 时,在同一行中附加一个简短的原因 - 哪些内容仍未解决或缺失。这可以准确地告诉用户采访需要显示什么内容,并防止数字成为模糊的信号。
格式:等待用户做出反应后再提出下一个问题。为什么一次一个,而不是一批:如果您将假设埋在列表中,用户将无法对您的假设做出反应批次鼓励略读和表面答案
最危险的答案是用户所说的“听起来像是”深思熟虑的答案,而不是他们真正想要的答案。注意: 模式匹配最佳实践谈话的答案(“我希望它是可扩展的”,“干净的架构”),没有具体细节 遵循惯例的答案(“大多数应用程序的方式”,“标准方法”) 像“我可能应该......”,“我认为我应该......”,“良好的工程实践说......”这样的短语
当您信心十足时,写回您现在认为用户想要的内容。保持紧凑(5-8 行),尽可能使用他们的语言,并对其进行结构化,以便用户可以逐行确认或更正:包括“超出范围”是不可协商的。一半的不一致是关于“不”正在建造的东西的无声分歧。
门是一个明确的“是”。以下不是“是”:“你认为最好的。” → 用户正在委托,这意味着他们也没有 95% 的信心。重新提出两个具体选项作为选择。 “听起来不错。” → 模棱两可。问:“你有什么要精炼的吗?”沉默并不等于确认。 “当然可以,我们走吧。” → 通常是礼貌的退出,而不是认可。同样的后续。沉默之后是“好吧,我们开始吧”。 → 用户已经放弃采访,没有收敛。停下来问问你是否错过了什么。
# Interview Me
## Overview
What people ask for and what they actually want are different things. They ask for "a dashboard" because that's what one asks for, not because a dashboard solves their problem. They say "make it faster" without a number to hit.
The cheapest moment to find this gap is before any plan, spec, or code exists. Once you've started building, switching costs are real, and the user will rationalize the wrong thing into a "good enough" thing. The misfit gets locked in.
This skill closes the gap before it costs anything. The other Define-phase skills assume you already know roughly what you want: `idea-refine` generates variations from an idea, `spec-driven-development` writes the requirements down, `doubt-driven-development` stress-tests a plan after you've drafted one. Interview-me is the part before all of those, where you ask one question at a time, with your best guess attached, until you can predict what the user is going to say before they say it.
## When to Use
Apply this skill when:
- The ask is missing at least one of: **who** the user is, **why** they want it, what **success** looks like, what the binding **constraint** is
- The request is conventional rather than specific ("build me X", "make it faster") and you can't unpack the convention without guessing
- You're tempted to start with assumptions you haven't surfaced
- The user hasn't said which value they're optimizing for when two reasonable ones are in tension (simplicity vs. flexibility, cost vs. speed)
- The user explicitly invokes: "interview me", "grill me", "before we start, are we sure?", "stress-test my thinking"
**When NOT to use:**
- The ask is unambiguous and self-contained ("rename this variable", "fix this typo")
- The user has explicitly asked for speed over verification
- Pure information requests ("how does X work?", "what does this code do?")
- Mechanical operations (renames, formats, file moves)
- You already have ≥95% confidence; re-read the stop condition below before assuming you don't
## Loading Constraints
This skill needs a live, responsive user. **Do not invoke in non-interactive contexts** like CI pipelines, scheduled runs, `/loop`, or autonomous-loop. If you're in one of those and the ask is underspecified, flag that as a blocker for the user instead of guessing.
## The Process
### Step 1: Hypothesize, with a confidence number
Before asking anything, write down your current best read of what the user wants in **one sentence**, plus an honest confidence number (0–100%):
```
HYPOTHESIS: You want a way to answer "how are we doing?" in standup, and "dashboard" was the convention that came to mind.
CONFIDENCE: ~30% — missing: who it's for, what "metrics" means in context, and what success looks like
```
The number forces honesty. If you wrote down a high number but can't actually predict the user's reactions to the next three questions you'd ask, the number is wrong. Start at the confidence level you can defend.
When confidence is below ~70%, append a brief reason on the same line — what's still unresolved or missing. This tells the user exactly what the interview needs to surface, and prevents the number from being a vague signal.
### Step 2: Ask one question at a time, each with a guess attached
Format:
```
Q: <one focused question>
GUESS: <your hypothesis for the answer, with the reasoning that produced it>
```
Wait for the user to react before asking the next question.
**Why one at a time, not a batch:**
- The user can't react to your hypotheses if you bury them in a list
- Batches encourage skim-reading and surface answers
- The third question often depends on the answer to the first; asking them all at once locks in the wrong framing
- The user's energy for thinking carefully is finite; spend it one question at a time
**Why attach a guess:**
- The user reacts faster to a wrong guess than they generate an answer from scratch
- It commits you to a hypothesis you can be visibly wrong about, which keeps you honest
- It surfaces *your* assumptions, which is what the interview is meant to expose
The risk here is a polite user agreeing with your guess to be agreeable. Mitigate by being visibly willing to be wrong, and occasionally guess in a direction you expect the user to push back on.
### Step 3: Listen for "want vs. should want"
The most dangerous answers are the ones where the user says what a thoughtful answer *sounds like* rather than what they actually want. Watch for:
- Answers that pattern-match best-practice talk ("I want it to be scalable", "clean architecture") without specifics
- Answers that defer to convention ("the way most apps do it", "the standard approach")
- Phrases like "I should probably…", "I think I'm supposed to…", "good engineering practice says…"
- Buzzwords as goals — when "modern", "scalable", "robust" are the answer instead of a specific outcome
When you hear these, the question to ask is:
> *"If you didn't have to justify this to anyone, what would you actually want?"*
That single question often does more work than the previous five.
### Step 4: Restate intent in the user's own words
When your confidence is high, write back what you now think the user wants. Keep it tight (5–8 lines), use their language where possible, and structure it so the user can confirm or correct line by line:
```
Here's what I now think you want:
- Outcome: <one line>
- User: <one line — who benefits>
- Why now: <one line — what changed>
- Success: <one line — how we know it worked>
- Constraint: <one line — the binding limit>
- Out of scope: <one line — what we're explicitly not doing>
Yes / no / refine?
```
Including "Out of scope" is non-negotiable. Half of misalignment is silent disagreement about what is *not* being built.
### Step 5: Confirm — explicit yes, not "whatever you think"
The gate is an explicit "yes." The following are **not** yes:
- "Whatever you think is best." → The user is delegating, which means they don't have 95% confidence either. Re-ask with two concrete options framed as a choice.
- "Sounds good." → Ambiguous. Ask: "Anything you'd refine?" Silence isn't confirmation.
- "Sure, let's go." → Often a polite exit, not an endorsement. Same follow-up.
- Silence followed by "okay let's start." → The user has given up on the interview, not converged. Stop and ask whether you've missed something.
If they correct you, fold the correction in and restate. Loop until you get an explicit yes.
### The 95% Confidence Stop
You're done when you can answer yes to this:
> *Can I predict the user's reaction to the next three questions I would ask?*
If yes, you have shared understanding. Stop interviewing and produce the restate. If no, you're not done; ask the next question.
This is a checkable test, not a vibe. It also has a floor: if you've gone several rounds and still can't predict, that's information about the ask, not a reason to keep grinding. Stop and tell the user: "I've asked X questions and I still can't predict your reactions. Something foundational is missing. Want to step back?"
## Output
The output of this skill is a **confirmed statement of intent**: the restate from Step 4, with an explicit yes from Step 5. That's the deliverable. Specs, plans, and task lists are downstream; they consume the intent this skill produces.
If the user wants the intent to persist (a multi-session project, a handoff to another collaborator), offer to save it to `docs/intent/[topic].md`. Only save if they confirm.
## Example
A short before-and-after.
**Without `interview-me`:**
```
User: build me a dashboard for our metrics
Agent: <starts proposing chart libraries and layouts>
```
The agent has assumed: who it's for, what metrics, what "for our team" means, what success looks like. None of these are stated. Every assumption is a place the user can later say "that's not what I meant."
**With `interview-me`:**
```
User: build me a dashboard for our metrics
Agent:
HYPOTHESIS: You want a way to answer "how are we doing?" in standup, and "dashboard" came to mind because that's the conventional answer.
CONFIDENCE: ~30% — missing: who it's for, what "metrics" are, and what success looks like
Q: When you say "how are we doing?", who's asking — you alone, the engineering team in standup, or up the chain (e.g., your manager, an exec, a board)?
GUESS: engineering team in standup, because "we" usually scopes that way and standups are where this question gets asked. If it's for execs the metrics and the framing change a lot.
User: It's actually for me. I keep losing track of which experiments are running and what their early signal looks like.
Agent:
Updated read: not a team dashboard at all. It's a personal experiment tracker. Confidence: ~60% — still missing: what "early signal" means and what done looks like.
Q: Is the gap that you don't know which experiments exist, or that you can't see their results in one place?
GUESS: the second one. You have a list of experiments somewhere, but their results live in five different tools, and reconciling them by hand is what you're tired of.
User: First one actually. I literally don't have a list. They're spread across different docs.
Agent: <continues>
```
Two questions in, the agent has discovered the actual ask isn't "a dashboard." It's "a list." Different artifact, different scope, different work. The dashboard would have been wrong.
## Interaction with Other Skills
- **`idea-refine`**: downstream. If the confirmed intent is "I want X but I don't know how to scope it," hand off to `idea-refine` to generate variations against the now-explicit intent.
- **`spec-driven-development`**: downstream. If the confirmed intent is concrete ("I want X for Y users with Z success criteria"), hand off to `spec-driven-development` to write it down.
- **`planning-and-task-breakdown`**: two hops downstream of this skill (after the spec).
- **`doubt-driven-development`**: opposite end of the timeline. Interview-me is pre-decision intent extraction; doubt-driven is post-decision artifact review. Both catch divergence, but at different moments.
- **`source-driven-development`**: orthogonal. Interview-me clarifies what the user wants; SDD verifies framework facts. They don't compete.
## Common Rationalizations
| Rationalization | Reality |
|---|---|
| "The ask is clear enough" | If you can't write the user's desired outcome in one sentence right now, the ask isn't clear. Run Step 1 before deciding. |
| "Asking too many questions wastes their time" | Time wasted by 4–6 targeted questions is small. Time wasted by building the wrong thing is enormous, and the user is the one bearing that cost. |
| "I'll figure it out as I build" | Switching costs after code exists are 10x what they are now. Discovery during implementation is rework. |
| "They said 'whatever you think,' so I should just decide" | "Whatever you think" is delegation, not decision. Re-ask with two concrete options as a choice. |
| "I should give them several options to pick from" | Options work when the user knows what they want and is choosing between trade-offs. They don't know what they want yet. Listing options widens the search; asking narrows it. |
| "If I attach my guess, I'm leading them" | Leading is the point. Reacting is faster than generating from scratch. The risk is sycophancy, not leading; mitigate by being visibly willing to be wrong. |
| "We've talked enough, I get it" | Test it: can you predict their reaction to the next three questions? If not, you don't get it yet. |
| "The user said yes, we're done" | If the yes followed a vague restate or an open-ended "sounds good," the yes is hollow. Restate concretely and re-confirm. |
## Red Flags
- Three or more questions in a single message: that's batching, not interviewing
- A question without your hypothesis attached: that's surveying, not committing
- Accepting "whatever you think is best" as a terminal answer
- Producing a spec, plan, or task list before the user has explicitly confirmed your restate
- Questions framed as "what would be best practice?" instead of "what do you actually want?"
- The user gives a sophistication-signaling answer ("scalable", "clean", "modern") and you accept it without probing whether it's what they actually want
- Three or more rounds without your confidence visibly rising: you're asking the wrong questions, step back and reframe
- A confidence number below ~70% with no reason attached: the user can't help close the gap if they don't know what's missing
- Saving the intent doc before the user has confirmed (the doc itself implies a yes the user didn't give)
- Skipping the "Out of scope" line in the restate (silent disagreement about non-goals is half of misalignment)
## Verification
After applying interview-me:
- [ ] An explicit hypothesis with a confidence number was stated in the first turn
- [ ] Every confidence number below ~70% was accompanied by a one-line reason (what's still unresolved or missing)
- [ ] Questions were asked one at a time, each with the agent's guess attached
- [ ] At least one "what would you actually want if you didn't have to justify it?" probe ran when the user gave a sophistication-signaling or convention-signaling answer
- [ ] A concrete restate (Outcome / User / Why now / Success / Constraint / Out of scope) was written back to the user
- [ ] The user confirmed the restate with an explicit yes (not "whatever you think," not "sounds good," not silence)
- [ ] At the stop point, the agent could predict reactions to the next three questions it would ask
- [ ] Any handoff to a downstream skill (`idea-refine`, `spec-driven-development`) was framed in terms of the confirmed intent, not the original underspecified ask
按说明文件中的顺序排列。
概述
何时使用
加载约束
第 1 步:用置信度进行假设
第 2 步:一次提出一个问题,每个问题都附带一个猜测
文件/命令 -> idea-refine · spec-driven-development · doubt-driven-development · /loop · docs/intent/[topic].md · interview-me · planning-and-task-breakdown · source-driven-development
内容校验值 -> 90af081d658a
当前原文的自动摘译,尚未人工审校。
概述
人们要求的东西和他们真正想要的东西是不同的。他们要求“仪表板”,因为这就是人们所要求的,而不是因为仪表板解决了他们的问题。他们说“让它更快”,但没有达到目标。发现这种差距的最便宜的时刻是在任何计划、规范或代码存在之前。一旦开始构建,转换成本就是真实的,用户会将错误的事情合理化为“足够好”的事情。不合时宜的人被锁定。
何时使用
在以下情况下应用此技能: 询问至少缺少以下一项:用户是谁、为什么他们想要它、成功是什么样子、绑定约束是什么 请求是常规的而不是特定的(“构建我 X”、“让它更快”)并且您无法在不猜测的情况下解开约定 您很想从尚未浮现的假设开始 当两个合理的值处于紧张状态时(简单性与灵活性、成本与速度),用户还没有说出他们要优化的值(简单性与灵活性、成本与速度)
加载约束
这项技能需要一个活跃的、反应灵敏的用户。不要在非交互式上下文中调用,例如 CI 管道、计划运行、
/loop或自主循环。如果您属于其中之一,并且询问未指定,请将其标记为用户的阻止者,而不是猜测。