Back to Details

explore-unknowns

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Explore Unknowns

探索未知项

The map is not the territory. The prompt, the plan, and the context window are the map; the codebase, the domain, and the user's actual intent are the territory. The gap between them is the unknowns — and an unknown found before code is written costs minutes, while the same unknown found three PRs later costs the three PRs.
This skill is a guided conversation: the quadrant walk. Together with the user you fill in a four-quadrant map of the task, one quadrant per stage, and the user walks away holding the completed map. The map is the deliverable; implementation is a different task that starts only after the map is handed over.
Two moves apply at every stage:
  • Reacting beats imagining. Never ask the user to describe what they want when you can hand them something concrete to react to — a rendered option, a clickable mock, a decisions table. Reacting extracts knowledge the user has but cannot articulate unprompted.
  • Every artifact assembles the reply. End each artifact with the user's next message pre-drafted: steal/skip chips, resonate checkboxes, a decisions table, a copyable sharpened prompt — so their reaction becomes their next message with near-zero typing.
地图不等同于实际领域。提示词、计划和上下文窗口是“地图”；代码库、业务领域和用户的真实需求是“实际领域”。两者之间的差距就是未知项——在编写代码前发现未知项只需花费数分钟，而在三个PR之后才发现同样的未知项，代价则是这三个PR的工作量。
本技能是一个引导式对话流程：quadrant walk（四象限梳理流程）。你将与用户一起逐步填写任务的四象限图，每个阶段完成一个象限，最终用户将拿到完整的四象限图。该四象限图是本次任务的交付成果；代码实现是另一项任务，需在拿到四象限图后才开始。
每个阶段都适用两个原则：
  • 反馈胜于空想。当你可以提供具体内容让用户反馈时，绝不要让用户描述他们想要什么——比如渲染好的选项、可点击的原型、决策表。反馈能挖掘出用户拥有但无法自发表述的信息。
  • 每个产出物都简化回复流程。每个产出物结尾都要预先拟好用户的下一条消息：可选择的选项、确认复选框、决策表、可复制的精准提示词——让用户只需极少输入就能给出反馈。

The Quadrant Walk

四象限梳理流程

Five stages, walked in order, one at a time. When you enter a stage, read its reference file and follow it. Name the current quadrant as you go — the user should always know where they stand on the map — and finish the stage in front of you before opening the next.
  1. Known knowns — scan the territory, then open with the settled ground.
  2. Known unknowns — the questions you can name; resolve them one at a time.
  3. Unknown knowns — extract the taste and tacit context nobody has put into words.
  4. Unknown unknowns — sweep the territory for landmines.
  5. Hand over the map — the completed four-quadrant map, the walk's only done-condition.
When the user moves on to build, review, or merge what the walk mapped, read after the walk — the map lives on past planning.
共五个阶段，需按顺序逐步完成。进入某个阶段时，请阅读对应的参考文件并遵循其指引。过程中要明确当前所在的象限——用户应始终清楚自己在四象限图中的位置——完成当前阶段后再进入下一阶段。
  1. 已知已知项 —— 梳理实际领域，从已明确的内容开始。
  2. 已知未知项 —— 列出能明确提出的问题，逐一解决。
  3. 未知已知项 —— 挖掘出无人明确表述的偏好和隐性背景信息。
  4. 未知未知项 —— 排查实际领域中的潜在风险。
  5. 交付四象限图 —— 完成完整的四象限图，这是梳理流程完成的唯一标志。
当用户开始基于梳理好的四象限图进行开发、评审或合并时，请阅读梳理后指引——四象限图在规划阶段后仍会发挥作用。

Rules

规则

  • Walk the quadrants in order, one stage at a time, naming the current quadrant. The walk ends with the map in the user's hands — no map, not done.
  • Stages order the walk; they never embargo information. A finding that materially bears on a decision in flight is disclosed the moment you have it, then filed on the map under its quadrant — never held back for its stage's scheduled turn.
  • Nothing closes off-screen. Any question or judgment call the map records as closed must have been shown to the user first — including ones the territory answered.
  • Claims about the territory cite real files actually read; invented data is labeled as such. A fabricated specific destroys the map's authority.
  • HTML artifacts are self-contained single files: inline CSS/JS, no external requests, plausible fake data over lorem ipsum.
  • Stop at every stage boundary that needs the user's reaction. Never barrel into implementation on unconfirmed guesses — implementing is a separate task that begins after the map is delivered.
  • 按顺序逐步完成四象限梳理，明确当前所在的象限。梳理流程以用户拿到四象限图为结束标志——未交付四象限图则不算完成。
  • 阶段用于规划梳理顺序，但绝不限制信息披露。如果发现的内容对当前决策有实质性影响，应立即告知用户，然后将其归入对应象限的四象限图中——绝不要等到该阶段的预定时间再披露。
  • 所有事项都需公开处理。四象限图中记录为已解决的任何问题或判断，都必须先展示给用户确认——包括实际领域已给出答案的事项。
  • 关于实际领域的表述需引用真实读取的文件；虚构数据需明确标注。虚构的具体内容会破坏四象限图的权威性。
  • HTML产出物需为独立的单文件：内联CSS/JS，无外部请求，使用合理的假数据而非乱码文本。
  • 在每个需要用户反馈的阶段节点暂停。绝不要在未确认猜测的情况下直接进入实现环节——实现是交付四象限图之后才开始的独立任务。