Back to Details

interview

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Interview

访谈

Overview

概述

This skill provides a structured interview framework to systematically gather information before starting work. It helps reduce ambiguity, ensure comprehensive understanding, and produce actionable outputs. The interview adapts to different contexts: requirements definition, debugging, architecture decisions, security review, and more.
该技能提供了一套结构化访谈框架，可在启动工作前系统地收集信息，有助于减少歧义、确保理解全面，并产出可落地的输出结果。该访谈框架可适配不同场景：需求定义、调试、架构决策、安全评审等。

When to Use

适用场景

  • Starting a new feature implementation
  • Investigating bugs or issues
  • Reviewing architecture or security
  • Creating documentation or reports
  • Any task requiring clarification of scope, constraints, or expectations
  • 启动新功能开发
  • 排查bug或问题
  • 评审架构或安全方案
  • 编写文档或报告
  • 任何需要明确范围、约束或预期的任务

Workflow

工作流

Phase 1: Preparation (Silent)

阶段1：准备（静默阶段）

Before asking questions, gather background context silently.
Parallel Fan-Out Pattern: The following three preparation tasks have no dependencies on each other and SHOULD be executed in parallel. This reduces Phase 1 completion time by approximately 66%.
Reference: Google ADK Multi-Agent Patterns
Codebase Exploration: (parallel task 1/3)
  • Project structure - Identify key directories, config files, entry points
  • Recent changes - Check git history if applicable
  • Related code - Search for relevant patterns or implementations
Documentation Review: (parallel task 2/3)
  • Read any referenced files or URLs provided by user
  • Check for existing specifications, ADRs, or design documents
  • Review related issues or PRs if applicable
Web Research (if applicable): (parallel task 3/3)
  • Best practices for the domain
  • Similar implementations or patterns
  • Security considerations
For detailed exploration commands per environment (Claude Code, Codex, API), see 
references/exploration-patterns.md
.
提问前，先静默收集背景上下文信息。
并行扇出模式（Parallel Fan-Out Pattern）：以下三项准备任务互不依赖，应当并行执行，可将阶段1的完成时间缩短约66%。
参考：Google ADK Multi-Agent Patterns
代码库探索：（并行任务1/3）
  • 项目结构：识别核心目录、配置文件、入口点
  • 近期变更：如有相关权限，查看git提交历史
  • 相关代码：搜索相关的代码模式或实现
文档评审：（并行任务2/3）
  • 阅读用户提供的所有参考文件或URL
  • 查找是否有已有的规范、ADR或设计文档
  • 如有相关权限，查阅相关的issue或PR
网络调研（如适用）：（并行任务3/3）
  • 对应领域的最佳实践
  • 类似的实现或设计模式
  • 安全注意事项
如需查看各环境（Claude Code、Codex、API）下的详细探索命令，可参阅 
references/exploration-patterns.md
。

Phase 2: Interview

阶段2：访谈

Conduct the interview in stages, adapting questions based on interview type.
分阶段开展访谈，根据访谈类型调整问题。

Stage 1: Goal Confirmation

环节1：目标确认

Start by confirming the overall objective:
Environment-specific approach:
  • Claude Code: Use AskUserQuestion tool for structured choices
  • Other environments: Present numbered options and ask user to reply with number or description
Core Questions:
  • What is the primary goal or outcome expected?
  • Who are the stakeholders or users affected?
  • What does success look like?
Interview Type Selection:
Ask the user to select the interview type to tailor subsequent questions:
TypeUse Case
RequirementsNew feature, specification, API design
InvestigationBug analysis, performance issue, incident
ArchitectureDesign review, technology selection, refactoring
SecuritySecurity audit, vulnerability assessment
DocumentationReport creation, knowledge transfer
GeneralOpen-ended exploration, brainstorming
首先确认整体目标：
不同环境的适配方案：
  • Claude Code：使用AskUserQuestion工具提供结构化选项
  • 其他环境：展示编号选项，请用户回复对应编号或描述
核心问题：
  • 预期的核心目标或产出是什么？
  • 受影响的利益相关方或用户有哪些？
  • 成功的衡量标准是什么？
访谈类型选择：
请用户选择访谈类型，以便定制后续的问题：
类型适用场景
需求新功能、规范、API设计
调查Bug分析、性能问题、事件
架构设计评审、技术选型、重构
安全安全审计、漏洞评估
文档报告编写、知识传递
通用开放式探索、头脑风暴

Stage 2: Deep Dive

环节2：深度调研

Based on the selected interview type, ask targeted questions.
For detailed question frameworks and output templates per interview type, read 
references/interview-types.md
.
根据选中的访谈类型，提出针对性问题。
如需查看各访谈类型的详细问题框架和输出模板，可参阅 
references/interview-types.md
。

Stage 3: Confirmation and Prioritization

环节3：确认与优先级排序

Before concluding:
  1. Summarize Understanding - Restate key points for confirmation
  2. Identify Gaps - Note any undecided or unclear items
  3. Prioritize - Classify requirements as Must/Should/Could
  4. Confirm Scope - Agree on what is in/out of scope
结束访谈前：
  1. 总结理解：重述核心要点请用户确认
  2. 识别差距：标注所有未确定或不清晰的事项
  3. 优先级划分：将需求分为必须有（Must）/应该有（Should）/可以有（Could）
  4. 确认范围：就范围包含/排除的内容达成一致

Deep Dive Strategies

深度调研技巧

Use these techniques to reduce ambiguity:
TechniqueWhen to Use
"Specifically?"When details are vague
"Why?"When motivation is unclear
"What else?"When list seems incomplete
"For example?"When concept needs illustration
"What if...?"When edge cases need exploration
使用以下技巧减少歧义：
技巧适用场景
"可以具体说明吗？"当描述模糊时
"为什么？"当动机不明确时
"还有其他吗？"当列表看起来不完整时
"可以举个例子吗？"当概念需要举例说明时
"如果…会怎么样？"当需要探索边界情况时

Phase 3: Output

阶段3：输出

Generate a structured summary document.
生成结构化的总结文档。

Output Template

输出模板

markdown
undefined
markdown
undefined

[Interview Type]: [Topic]

[Interview Type]: [Topic]

Summary

Summary

[1-2 sentence overview]
[1-2 sentence overview]

Goal

Goal

  • Objective: [Primary goal]
  • Stakeholders: [Who is affected]
  • Success Criteria: [How to measure success]
  • Objective: [Primary goal]
  • Stakeholders: [Who is affected]
  • Success Criteria: [How to measure success]

Requirements / Findings

Requirements / Findings

Must Have

Must Have

  • [Item 1]
  • [Item 2]
  • [Item 1]
  • [Item 2]

Should Have

Should Have

  • [Item 1]
  • [Item 1]

Could Have

Could Have

  • [Item 1]
  • [Item 1]

Constraints

Constraints

  • [Technical constraints]
  • [Business constraints]
  • [Timeline constraints]
  • [Technical constraints]
  • [Business constraints]
  • [Timeline constraints]

Undecided / Open Questions

Undecided / Open Questions

  • [Question 1]
  • [Question 2]
  • [Question 1]
  • [Question 2]

Next Steps

Next Steps

  1. [Action item 1]
  2. [Action item 2]
  1. [Action item 1]
  2. [Action item 2]

References

References

  • [Link or file reference 1]
  • [Link or file reference 2]
  • [Link or file reference 1]
  • [Link or file reference 2]

Affected Files / Components

Affected Files / Components

  • path/to/file1
  • path/to/file2
undefined
  • path/to/file1
  • path/to/file2
undefined

Usage Examples

使用示例

For detailed usage examples with sample outputs, see 
references/usage-examples.md
.
Quick reference:
  • /interview Add user authentication
    → Requirements interview
  • /interview Investigate 504 errors
    → Investigation interview
  • /interview Review database schema
    → Architecture interview
如需查看带示例输出的详细使用案例，可参阅 
references/usage-examples.md
。
快速参考：
  • /interview Add user authentication
    → 需求类访谈
  • /interview Investigate 504 errors
    → 调查类访谈
  • /interview Review database schema
    → 架构类访谈

Guidelines

指导原则

  1. Adapt to Context - Adjust question depth based on task complexity
  2. Avoid Overwhelming - Ask 2-3 questions at a time, not all at once
  3. Be Specific - Reference actual code, files, or examples when possible
  4. Document Everything - Capture decisions and their rationale
  5. Identify Gaps Early - Surface undecided items for follow-up
  6. Output Language - Follow user's language preference (check conversation history)
  1. 适配上下文：根据任务复杂度调整问题深度
  2. 避免信息过载：每次提问2-3个问题，不要一次性抛出所有问题
  3. 具体明确：尽可能参考实际代码、文件或示例
  4. 全程记录：记录所有决策及其背后的rationale
  5. 尽早识别差距：将未确定的事项同步给相关方跟进
  6. 输出语言：遵循用户的语言偏好（可查阅对话历史确认）

User Input Methods

用户输入方式

Claude Code Environment

Claude Code 环境

Use the AskUserQuestion tool for structured choices:
Question: "What type of interview is this?"
Header: "Type"
Options:
  - "Requirements (Recommended)" - New feature or specification
  - "Investigation" - Bug or issue analysis
  - "Architecture" - Design or technology review
  - "Security" - Security assessment
This enables efficient selection with clickable options.
使用AskUserQuestion工具提供结构化选项：
Question: "What type of interview is this?"
Header: "Type"
Options:
  - "Requirements (Recommended)" - New feature or specification
  - "Investigation" - Bug or issue analysis
  - "Architecture" - Design or technology review
  - "Security" - Security assessment
这样用户可以直接点击选项高效选择。

Other Environments (Codex, API, etc.)

其他环境（Codex、API等）

Present numbered options in plain text and wait for user response:
What type of interview is this?

1. Requirements - New feature or specification (Recommended)
2. Investigation - Bug or issue analysis
3. Architecture - Design or technology review
4. Security - Security assessment
5. Documentation - Report creation, knowledge transfer
6. General - Open-ended exploration

Please reply with a number (1-6) or describe your needs:
Wait for the user's response before proceeding. Accept both:
  • Number selection (e.g., "1", "2")
  • Free-form description (e.g., "I need to investigate a performance issue")
以纯文本形式展示编号选项，等待用户回复：
What type of interview is this?

1. Requirements - New feature or specification (Recommended)
2. Investigation - Bug or issue analysis
3. Architecture - Design or technology review
4. Security - Security assessment
5. Documentation - Report creation, knowledge transfer
6. General - Open-ended exploration

Please reply with a number (1-6) or describe your needs:
等待用户回复后再继续。可接受两种回复形式：
  • 选择编号（例如："1"、"2"）
  • 自由描述（例如："我需要排查一个性能问题"）