混合主动流
- 作者仓库星标 108
- 许可证 MIT
- 作者仓库 ai-design-skills
- 领域
- 通用
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 94 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @Owl-Listener · MIT
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 命令执行
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
# Mixed-Initiative Flow
Mixed-initiative interaction is when both the human and the AI can take the lead. The designer decides who drives at each moment — and how control transfers between them.
## Initiative Spectrum
Interactions sit on a spectrum:
- **User-driven**: The user gives instructions, the AI executes. The user controls pace, direction, and scope.
- **AI-driven**: The AI leads — asking questions, making suggestions, guiding the user through a process.
- **Shared**: Both parties contribute. The AI proposes, the user edits. The user starts, the AI finishes.
Most AI products default to user-driven. The interesting design space is in shared and AI-driven modes.
## Designing Initiative Handoffs
The moment control shifts from one party to the other is where most interactions fail. Design these transitions:
- **Explicit handoff**: "I've drafted three options. Which direction do you want to go?" — the AI clearly passes control.
- **Implicit handoff**: The AI stops generating and waits, signalling the user's turn through UI affordance.
- **Negotiated handoff**: "I could take this further or stop here for your input. What do you prefer?"
- **Forced handoff**: The AI encounters a decision it can't make and must hand back to the human.
## When the AI Should Lead
The AI should take initiative when:
- The user is uncertain or exploring and needs guidance
- The task has a known best-practice sequence the AI can walk through
- The user has explicitly asked for help or coaching
- Proactive suggestions would save time without being intrusive
## When the User Should Lead
The user should retain control when:
- The task involves subjective judgment or creative direction
- Stakes are high and errors are costly
- The user has strong domain expertise
- Privacy or consent decisions are involved
## Anti-Patterns
- **Initiative whiplash**: Control bouncing back and forth too rapidly
- **Passive AI**: Never taking initiative even when it would help
- **Overbearing AI**: Taking over when the user wants control
- **Unclear ownership**: Neither party knows whose turn it is
## Design Artefacts
- Initiative maps showing who leads at each stage
- Handoff trigger definitions (what causes a transfer of control)
- Autonomy level specifications per feature area
章节与文件索引
按说明文件中的顺序排列。
主动频谱
设计主动性交接
人工智能何时应该引领
何时应由用户引导
反模式
文件/命令 -> 原文未列出明确文件或命令
内容校验值 -> ae69c0b6e67b
当前原文的自动摘译,尚未人工审校。
主动频谱
交互有以下范围: 用户驱动:用户发出指令,人工智能执行。用户控制速度、方向和范围。人工智能驱动:人工智能引领——提出问题、提出建议、引导用户完成流程。共享:双方共同贡献。人工智能提出建议,用户编辑。用户开始,人工智能结束。大多数人工智能产品默认都是用户驱动的。有趣的设计空间是共享和人工智能驱动的模式。
设计主动性交接
当控制权从一方转移到另一方时,大多数互动都会失败。设计这些转换: 明确的交接:“我已经起草了三个选项。你想朝哪个方向发展?” ——人工智能显然已经失去了控制权。隐式切换:人工智能停止生成并等待,通过 UI 功能向用户发出轮到的信号。协商交接:“我可以进一步讨论,也可以在这里停下来征求您的意见。您更喜欢什么?”
人工智能何时应该引领
在以下情况下,人工智能应该采取主动: 用户不确定或探索并需要指导 任务具有人工智能可以执行的已知最佳实践序列 用户已明确请求帮助或指导 主动建议可以节省时间而不具有侵入性
何时应由用户引导
在以下情况下,用户应保留控制权: 任务涉及主观判断或创意方向 风险很高,错误代价高昂 用户拥有强大的领域专业知识 涉及隐私或同意决策
反模式
主动鞭打:控制来回弹跳太快 被动人工智能:即使有帮助,也从不采取主动 霸道人工智能:在用户想要控制时接管 不明确的所有权:双方都不知道轮到谁