skilless.ai-brainstorming

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Brainstorming: From Idea to Plan

头脑风暴:从想法到计划

Help turn ideas into fully formed plans through natural collaborative dialogue.
Works for: product features, business ideas, creative projects, process improvements, technical designs, or any new initiative.
通过自然协作对话帮助将想法转化为完整成熟的计划。
适用场景:产品功能、商业构想、创意项目、流程优化、技术设计或任何新举措。

Core Process

核心流程

Understand → Explore → Decide → Plan
  1. Understand the idea — What are you trying to achieve?
  2. Clarify context — Who is this for? What constraints exist?
  3. Explore options — Propose 2-3 approaches with trade-offs
  4. Decide together — Get your approval on the direction
  5. Create a plan — Document the agreed approach
理解 → 探索 → 决策 → 规划
  1. 理解想法 — 你想要实现什么目标?
  2. 明确背景 — 这是为谁设计的?存在哪些限制条件?
  3. 探索方案 — 提出2-3种带有权衡分析的方案
  4. 共同决策 — 获取你对方向的认可
  5. 制定计划 — 记录已达成共识的方案

Golden Rules

黄金准则

  • Group questions, ask in batches — Identify which questions are independent of each other and ask them together; hold back questions whose answers depend on earlier responses
  • Use question tools first — If
    ask_questions
    ,
    ask
    , or
    questions
    tools are available, use them; otherwise ask in plain text
  • Start broad, then narrow — Understand the big picture first
  • No assumptions — "Simple" ideas often have hidden complexity
  • Stay flexible — Go back and clarify when needed
  • 批量提问 — 识别出彼此独立的问题并一起提问;暂缓那些答案依赖于前期回复的问题
  • 优先使用提问工具 — 如果有
    ask_questions
    ask
    questions
    工具可用,请优先使用;否则用普通文本提问
  • 从宽泛到具体 — 先理解整体概况
  • 不做假设 — "简单"想法往往隐藏着复杂性
  • 保持灵活 — 必要时回溯并澄清问题

Checklist

检查清单

  1. Understand the goal — What problem are you solving? Who is it for?
  2. Clarify context — Timeline, budget, resources, constraints
  3. Explore approaches — 2-3 options with pros/cons
  4. Get approval — Present your recommendation, confirm with user
  5. Document the plan — Create a clear, actionable plan
<HARD-GATE> Do NOT start implementing until the user has approved the plan. Even "simple" ideas need clarity first.
  1. 理解目标 — 你要解决什么问题?服务对象是谁?
  2. 明确背景 — 时间线、预算、资源、限制条件
  3. 探索方案 — 2-3种带有优缺点的方案
  4. 获取认可 — 提出你的推荐方案,与用户确认
  5. 记录计划 — 创建清晰、可执行的计划
<HARD-GATE> 在用户批准计划前,切勿开始实施。即使是“简单”的想法也需要先明确细节。

Process Flow

流程示意图

dot
digraph brainstorming {
    "Explore project context" -> "Ask clarifying questions";
    "Ask clarifying questions" -> "Propose 2-3 approaches";
    "Propose 2-3 approaches" -> "Present design sections";
    "Present design sections" -> "User approves design?";
    "User approves design?" -> "Write design doc" [label="yes"];
    "Write design doc" -> "Implementation";
}
The terminal state is approved design → implementation plan.
dot
digraph brainstorming {
    "Explore project context" -> "Ask clarifying questions";
    "Ask clarifying questions" -> "Propose 2-3 approaches";
    "Propose 2-3 approaches" -> "Present design sections";
    "Present design sections" -> "User approves design?";
    "User approves design?" -> "Write design doc" [label="yes"];
    "Write design doc" -> "Implementation";
}
最终状态为:已批准的设计 → 实施计划。

The Process

详细流程

Understanding the idea:
  • Check any existing context first (files, docs, prior notes, recent work)
  • Gather all clarifying questions upfront — use
    ask_questions
    ,
    ask
    , or
    questions
    tool if available; plain text otherwise
  • Focus on: purpose, who it's for, constraints, success criteria, timeline
Exploring approaches:
  • Propose 2-3 different approaches with trade-offs
  • Lead with your recommended option and explain why
Presenting the plan:
  • Scale depth to complexity of the idea
  • Ask after each section whether it looks right
  • Cover dimensions relevant to the domain: structure, key decisions, risks, next steps
理解想法:
  • 首先查看所有现有背景信息(文件、文档、前期笔记、近期工作内容)
  • 提前收集所有需要澄清的问题——如果有
    ask_questions
    ask
    questions
    工具可用则使用;否则用普通文本提问
  • 重点关注:目的、服务对象、限制条件、成功标准、时间线
探索方案:
  • 提出2-3种不同的方案,并附上权衡分析
  • 优先推荐你的首选方案并说明理由
呈现计划:
  • 根据想法的复杂程度调整内容深度
  • 每展示完一个部分后询问是否合适
  • 涵盖与领域相关的维度:结构、关键决策、风险、后续步骤

Key Principles

核心原则

  • Batch questions by dependency - Ask independent questions together in one round; hold dependent ones for the next round after getting answers
  • Multiple choice preferred - Easier to answer than open-ended when possible
  • YAGNI ruthlessly - Remove unnecessary scope from all plans
  • Explore alternatives - Always propose 2-3 approaches before settling
  • Incremental validation - Present plan section by section, get approval before moving on
  • Domain-agnostic - Works for product, business, creative, process, and technical ideas alike
  • Be flexible - Go back and clarify when something doesn't make sense
  • 按依赖关系批量提问 — 将独立问题在一轮中一起提出;将依赖问题留到获取答案后的下一轮再问
  • 优先选择选择题形式 — 可能的话,选择题比开放式问题更容易回答
  • 严格践行YAGNI原则 — 从所有计划中移除不必要的范围
  • 探索替代方案 — 在确定最终方案前,始终提出2-3种可选方案
  • 增量验证 — 分部分呈现计划,获得批准后再推进下一步
  • 领域无关 — 适用于产品、商业、创意、流程和技术等各类想法
  • 保持灵活 — 当遇到不合理的内容时,回溯并澄清

Cross-References

交叉引用

  • Need research? → Invoke
    skilless.ai-research
    to search the web, read pages, extract video transcripts, or conduct deep multi-source investigations
  • Ready to document the plan? → Invoke
    skilless.ai-writing
    to produce a professional, structured design doc or report from the approved plan
  • 需要调研? → 调用
    skilless.ai-research
    进行网页搜索、页面读取、视频文稿提取或多源深度调研
  • 准备记录计划? → 调用
    skilless.ai-writing
    根据已批准的计划生成专业、结构化的设计文档或报告