intent-interview
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseIntent Interview
意向访谈法
A structured methodology for extracting, refining, and documenting product/feature requirements through deep interviewing.
一种通过深度结构化访谈来提取、细化并记录产品/功能需求的方法论。
Output Artifacts
输出产物
intent.md (for Code Agents)
intent.md(面向Code Agents)
Detailed technical specification with:
- Architecture design
- Data contracts and schemas
- Implementation guide with code examples
- Project structure
- Decision rationale
详细的技术规范,包含:
- 架构设计
- 数据契约与schemas
- 附带代码示例的实现指南
- 项目结构
- 决策依据
overview.md (for Humans)
overview.md(面向普通用户)
One-page summary with:
- Problem statement
- Core experience flow
- Architecture diagram (ASCII)
- Key decisions table
- Scope and risks
单页概要,包含:
- 问题陈述
- 核心体验流程
- ASCII架构图
- 关键决策表
- 范围与风险
Interview Process
访谈流程
Phase 1: Problem Space
第一阶段:问题域
Start by understanding WHAT before HOW.
Questions to ask:
- What is the core problem?
- Who is the target user?
- Is this a new product or addition to existing?
- What's the priority/urgency?先明确“是什么”,再考虑“怎么做”。
需要询问的问题:
- 核心问题是什么?
- 目标用户是谁?
- 这是新产品还是现有产品的新增功能?
- 优先级/紧急程度如何?Phase 2: Deep Dive (Iterative)
第二阶段:深度挖掘(迭代式)
Cover these dimensions systematically, 3-4 questions per round:
| Dimension | Key Questions |
|---|---|
| Data | Sources, contracts, validation, conflicts, authentication |
| Rendering | Cross-platform strategy, components, theming, sizing |
| Sync/Update | Real-time requirements, refresh strategy, failure handling |
| Architecture | Storage, sharing, cloud/local, offline capability |
| UX | Configuration flow, error states, feedback mechanisms |
| Edge Cases | Failures, migrations, security, low-end devices |
| Scope | MVP boundaries, what's in/out, phasing |
| Tech Stack | Languages, frameworks, existing code to reuse |
系统覆盖以下维度,每轮3-4个问题:
| 维度 | 关键问题 |
|---|---|
| 数据 | 数据源、契约、验证、冲突、认证 |
| 渲染 | 跨平台策略、组件、主题、尺寸 |
| 同步/更新 | 实时性要求、刷新策略、故障处理 |
| 架构 | 存储、共享、云端/本地、离线能力 |
| 用户体验 | 配置流程、错误状态、反馈机制 |
| 边缘情况 | 故障、迁移、安全、低端设备 |
| 范围 | MVP边界、包含/排除功能、分阶段规划 |
| 技术栈 | 语言、框架、可复用的现有代码 |
Phase 3: Contradiction Resolution
第三阶段:矛盾解决
When answers conflict with earlier choices:
- Point out the contradiction explicitly
- Ask for clarification with specific options
- Update understanding accordingly
当答案与之前的选择冲突时:
- 明确指出矛盾点
- 提供具体选项请求澄清
- 相应更新认知
Phase 4: Implementation Readiness Check
第四阶段:实现就绪检查
Before writing specs, verify:
- Can a code agent implement this without asking questions?
- Are all technical choices specified?
- Are edge cases covered?
If gaps exist, continue interviewing.
在撰写规范前,验证:
- Code Agent是否无需额外提问即可实现?
- 所有技术选择是否已明确?
- 边缘情况是否已覆盖?
若存在缺口,继续访谈。
Question Design
问题设计
Do
建议做法
- Ask non-obvious, probing questions
- Probe tradeoffs ("if X fails, should we Y or Z?")
- Use concrete scenarios
- Offer 3-4 mutually exclusive options
- Match user's language (中文/English)
- 提出非显而易见、有深度的问题
- 探究权衡方案("如果X失败,我们应该选择Y还是Z?")
- 使用具体场景
- 提供3-4个互斥选项
- 匹配用户的语言(中文/English)
Don't
避免做法
- Ask yes/no questions
- Ask obvious implementation details
- Ask multiple unrelated questions at once
- 提出是非题
- 询问显而易见的实现细节
- 同时提出多个不相关的问题
Format
格式
Use tool with:
AskUserQuestion- 1-4 questions per round
- 2-4 options per question
- Short header (max 12 chars)
- Clear option descriptions
使用工具,要求:
AskUserQuestion- 每轮1-4个问题
- 每个问题2-4个选项
- 简短标题(最多12字符)
- 清晰的选项描述
intent.md Template
intent.md 模板
markdown
undefinedmarkdown
undefined[Project] Specification
[项目] 技术规范
1. Overview
1. 概述
- Product positioning
- Core concept
- Priority
- Target user
- Project scope
- 产品定位
- 核心概念
- 优先级
- 目标用户
- 项目范围
2. Architecture
2. 架构
- Data layer
- Rendering layer
- Key subsystems
- 数据层
- 渲染层
- 关键子系统
3. Detailed Behavior
3. 详细行为
- Update/refresh
- Error handling
- Data processing
- 更新/刷新
- 错误处理
- 数据处理
4. User Experience
4. 用户体验
- Key flows
- Configuration
- 关键流程
- 配置
5. Technical Implementation Guide
5. 技术实现指南
- Project structure
- Code examples
- 项目结构
- 代码示例
6. Decisions Summary
6. 决策汇总
| Decision | Choice | Rationale |
| 决策 | 选择 | 依据 |
7. MVP Scope
7. MVP范围
- Included
- Excluded
- 包含功能
- 排除功能
8. Risks
8. 风险
9. Open Items
9. 待办事项
undefinedundefinedoverview.md Template
overview.md 模板
markdown
undefinedmarkdown
undefined[Project]: One-line description
[项目]: 一句话描述
One sentence explanation
一句话说明
Why?
为什么要做?
Problem in plain language
用通俗语言描述问题
Core experience
核心体验
ASCII flow diagram
ASCII流程图
Architecture
架构
ASCII component diagram
ASCII组件图
Key decisions
关键决策
| Question | Choice | Why |
| 问题 | 选择 | 原因 |
Scope
范围
In / Out
包含/排除
Risk + Mitigation
风险与缓解措施
Next steps
下一步计划
undefinedundefinedWorkflow
工作流程
User describes idea
↓
Phase 1: Problem space (1-2 rounds)
↓
Phase 2: Deep dive (multiple rounds)
↓
Phase 3: Resolve contradictions
↓
Phase 4: Check readiness
↓ (loop if gaps)
Generate intent.md
↓
Ask if overview needed
↓
Generate overview.md
↓
(Optional) Push to repository用户描述想法
↓
第一阶段:问题域(1-2轮)
↓
第二阶段:深度挖掘(多轮)
↓
第三阶段:解决矛盾
↓
第四阶段:就绪检查
↓(若有缺口则循环)
生成intent.md
↓
询问是否需要overview.md
↓
生成overview.md
↓
(可选)推送到代码仓库