chatter-driven-development
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseChatter-Driven Development
对话驱动开发（Chatter-Driven Development）
Overview
概述
A development paradigm where AI agents monitor unstructured team communications (Slack, Linear, meetings) to infer intent and proactively generate code without formal specifications.
Core principle: Use existing team "chatter" as input—discussions, complaints, questions—and let agents draft solutions before being asked.
这是一种开发范式，AI Agent会监控团队的非结构化沟通内容（如Slack、Linear、会议记录），以此推断意图并主动生成代码，无需依赖正式规格说明。
核心原则： 将团队现有的“对话内容”作为输入——包括讨论、反馈、疑问——让Agent在被请求前就起草解决方案。
The Flow
流程
┌─────────────────────────────────────────────────────────────────┐
│ 1. SIGNAL INPUT │
│ Slack messages, meeting transcripts, Reddit complaints │
│ │ │
│ ▼ │
│ 2. INTENT EXTRACTION │
│ Agent parses chatter to identify: │
│ • Bugs • Feature requests • Questions │
│ │ │
│ ▼ │
│ 3. PROACTIVE ARTIFACT GENERATION │
│ Agent drafts: │
│ • Pull Requests • Answers • Analysis │
│ │ │
│ ▼ │
│ 4. HUMAN VERIFICATION │
│ Simple approval interface ("Swipe right" / Merge) │
└─────────────────────────────────────────────────────────────────┘┌─────────────────────────────────────────────────────────────────┐
│ 1. SIGNAL INPUT │
│ Slack messages, meeting transcripts, Reddit complaints │
│ │ │
│ ▼ │
│ 2. INTENT EXTRACTION │
│ Agent parses chatter to identify: │
│ • Bugs • Feature requests • Questions │
│ │ │
│ ▼ │
│ 3. PROACTIVE ARTIFACT GENERATION │
│ Agent drafts: │
│ • Pull Requests • Answers • Analysis │
│ │ │
│ ▼ │
│ 4. HUMAN VERIFICATION │
│ Simple approval interface ("Swipe right" / Merge) │
└─────────────────────────────────────────────────────────────────┘Key Principles
核心原则
| Principle | Description |
|---|---|
| Ubiquitous Listening | Agent connected to Slack, Email, Meetings as passive observer |
| Context Inference | Parse unstructured chatter to identify actionable items |
| Proactive Execution | Draft PR/answer/analysis BEFORE being explicitly asked |
| Low-Friction Review | Humans approve via simple interfaces, not deep code review |
| 原则 | 描述 |
|---|---|
| 全域监听 | Agent作为被动观察者接入Slack、邮件、会议等渠道 |
| 上下文推断 | 解析非结构化对话内容，识别可执行任务 |
| 主动执行 | 在被明确请求前就起草PR、回复内容或分析报告 |
| 低摩擦审核 | 人类通过简单界面完成审批，无需深度代码审查 |
Enablement Requirements
启用要求
- Agent has access to team communication channels
- Agent can parse natural language intent
- Agent can create artifacts (PRs, docs, analyses)
- Simple approval workflow exists
- Agent可访问团队沟通渠道
- Agent能解析自然语言意图
- Agent可生成制品（PR、文档、分析报告）
- 存在简单的审批工作流
Common Mistakes
常见误区
- Requiring formal specs: Train agents to interpret natural discussions
- No proactive action: Waiting for explicit prompts defeats the purpose
- High-friction review: Make approval as simple as possible
- 要求正式规格说明：应训练Agent解读自然讨论内容
- 缺乏主动行动：等待明确提示违背了该范式的初衷
- 高摩擦审核：应让审批流程尽可能简单
Real-World Examples
实际案例
- Block: "Goose" listens to meetings and proactively drafts PRs/emails
- OpenAI: Codex answers data queries directly in Slack
Source: Alexander Embiricos (OpenAI Codex) via Lenny's Podcast
- Block：名为“Goose”的Agent监听会议内容并主动起草PR/邮件
- OpenAI：Codex在Slack中直接回复数据查询
来源：Alexander Embiricos（OpenAI Codex），来自Lenny播客