Back to Details

brainstorming

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
<HARD-GATE> Do NOT write any code, scaffold any project, or take any implementation action until you have presented a design and the user has approved it. This applies to EVERY project regardless of perceived simplicity. </HARD-GATE>
<HARD-GATE> 在提交设计方案并获得用户批准之前，不得编写任何代码、搭建任何项目框架或采取任何开发实现行动。无论项目看似多么简单，这条规则适用于所有项目。 </HARD-GATE>

Anti-Pattern: "Too Simple for a Design"

反模式：“项目太简单，无需设计”

Every project goes through this process — a todo list, a single-function utility, a config change. "Simple" projects are where unexamined assumptions cause the most wasted work. The design can be a few sentences, but it must be presented and approved.
所有项目都必须遵循此流程——无论是待办事项列表、单一功能工具，还是配置变更。“简单”项目恰恰是未经审视的假设导致大量无效工作的重灾区。设计方案可以只有几句话，但必须提交并获得批准。

Process

流程步骤

Complete these steps in order, creating a task for each:
按顺序完成以下步骤，为每个步骤创建任务：

1. Explore project context

1. 调研项目背景

Check files, docs, and recent commits to understand the current state.
查看文件、文档和近期提交记录，了解当前状态。

2. Ask clarifying questions

2. 提出澄清问题

  • One question per message — if a topic needs more exploration, break it up
  • Prefer multiple-choice questions; open-ended is fine when choices aren't obvious
  • Focus on purpose, constraints, and success criteria
  • 每条消息仅包含一个问题——若某个主题需要深入探讨，拆分提问
  • 优先使用选择题；当选项不明确时，开放式问题也可
  • 聚焦于项目目的、约束条件和成功标准

3. Propose 2–3 approaches

3. 提出2-3种实施方案

  • Lead with your recommendation and explain why
  • Include trade-offs for each approach
  • Apply YAGNI ruthlessly — remove unnecessary features from all options
  • 首先给出你的推荐方案并说明理由
  • 列出每种方案的利弊权衡
  • 严格践行YAGNI原则——从所有方案中移除不必要的功能

4. Present design incrementally

4. 逐步提交设计方案

  • Scale each section to its complexity (a sentence if simple, a few paragraphs if nuanced)
  • Cover: architecture, components, data flow, error handling, testing
  • Ask after each section whether it looks right — revise until approved
  • Go back and clarify if something doesn't make sense
  • 根据内容复杂度调整每个部分的篇幅（简单内容用一句话，复杂内容用几段文字）
  • 涵盖：架构、组件、数据流、错误处理、测试
  • 每个部分提交后询问是否合适——直至修改到获得批准
  • 若有内容不合理，回溯并澄清

5. Write design doc

5. 撰写设计文档

Save the approved design to 
~/.agents/brainstorming/<project-name>/YYYY-MM-DD-<topic>.md
and give the path to the user. Plan mode continues with implementation planning.
将获批的设计方案保存至
~/.agents/brainstorming/<project-name>/YYYY-MM-DD-<topic>.md
，并将路径告知用户。计划模式将进入后续的开发实现规划阶段。