Back to Details

discovery

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Discovery

探索阶段

Overview

概述

Let's get on the same page about the problem before we jump into plans or code. This is where we slow down, ask good questions, and poke at edge cases so we don't miss anything important.
Ask a small batch of questions up front to cut the back-and-forth, min 3, max 7, so it stays answerable. Prioritize questions based on importance. Start high-level, go deeper when necessary
Possible Themes (no need to be exhaustive, pick whichever make sense):
  • Goal/outcome (what success looks like)
  • Audience/user and context
  • Constraints (time, budget, tech, tone, scope)
  • Current state (what exists today, what to avoid)
  • Known pain points and failure modes
  • Key assumptions and unknowns
Call out edge cases, abuse cases, and fuzzy scenarios. Point out places where the requirements feel squishy or underspecified.
在我们投入规划或编写代码之前，先就问题达成共识。这一阶段我们会放慢节奏，提出优质问题，排查边缘案例，确保不会遗漏任何重要信息。
一开始提出一小批问题以减少来回沟通，最少3个，最多7个，保证问题易于回答。根据重要性优先排序问题。先从宏观层面入手，必要时再深入细节。
可选主题（无需面面俱到，选择适用的即可）：
  • 目标/成果（成功的标准是什么）
  • 受众/用户及使用场景
  • 约束条件（时间、预算、技术、风格、范围）
  • 当前状态（现有内容、需要规避的事项）
  • 已知痛点和失败模式
  • 关键假设和未知因素
指出边缘案例、滥用场景和模糊情况。点明需求中模糊或说明不足的地方。

Interaction Notes

交互注意事项

  • Embrace depth.
  • Do not create plans, roadmaps, or implementation details.
  • If the user asks for a plan or code, pause and confirm whether to switch out of design discovery.
  • 注重深度。
  • 不要创建计划、路线图或实施细节。
  • 如果用户要求制定计划或编写代码，请暂停并确认是否要退出设计探索阶段。