brainstorm

分类: 开发与编程 | 上传者: patrick-fu | 下载: 0 | 版本: v1.0（最新）

在规划或编码之前探索想法、明确目标并帮助用户缩小方向。每当用户提出新功能或想法、询问“您对 X 有何看法”、说“我正在考虑构建 Y”、想要比较方法、询问如何解决问题或似乎正在探索而不是准备好执行时，请使用此选项。当用户说“集思广益”、“让我们考虑一下”、“最好的方法是什么......”时，或者任何时候正确的下一步是澄清问题并集中在一个方向上，而不是编写代码时，也可以使用它。 --- # 头脑风暴在做任何事情之前，先问。不要跳到解决方案或实施。目标是找出用户的实际意思，揭示他们尚未说出的内容，并帮助他们集中在一个方向上。将此视为具有动力的苏格拉底式对话：使用问题来引导思维，但不要让用户永远在选项中徘徊。 ## 从上下文开始在提问之前，吸收对话、代码库、文档和项目状态中已经存在的上下文。不要询问您已经可以推断或直接查找的信息。 ## 引导对话

更新日志: Source: GitHub https://github.com/patrick-fu/awesome-skills

目录结构

当前层级: tree/main/brainstorm/

📁 evals/
- 📄 evals.json 3.4 KB
📁 references/
- 📄 visual-aids.md 6.4 KB
📄 SKILL.md 3.0 KB

SKILL.md

---
name: brainstorm
description: >
  Explore ideas, clarify goals, and help the user narrow down directions before planning or coding.
  Use this whenever the user proposes a new feature or idea, asks "what do you think about X",
  says "I'm thinking of building Y", wants to compare approaches, asks how to approach a problem,
  or seems to be exploring rather than ready to execute. Also use it when the user says
  "brainstorm", "let's think about this", "what's the best way to...", or any time the right
  next step is to clarify the problem and converge on a direction, not to write code yet.
---

# Brainstorm

Before anything else, ask. Don't jump to solutions or implementation.

The goal is to draw out what the user actually means, uncover what they have not said yet, and help them converge on a direction. Think of this as Socratic dialogue with momentum: use questions to guide the thinking, but do not leave the user wandering in options forever.

## Start With Context

Before asking, absorb the context that already exists in the conversation, codebase, docs, and project state. Do not ask for information you can already infer or look up directly.

## Guide The Conversation

First figure out where the user is: still exploring, partly narrowed down, or close to a decision.

If the problem is too large, shrink it to the first key subproblem before going deeper. A good brainstorm usually moves one important decision at a time, not five in parallel.

Prefer low-friction questions. Good defaults are:
- binary or multiple-choice questions
- priority questions
- constraint checks
- edge-case probes

Do not dump a long list of questions up front. Ask the single most useful next question, then adapt based on the answer.

## Help Converge

Do not just expand the option space. Once the picture is clear enough, organize the discussion into 2-3 plausible directions and recommend one. Explain the recommendation briefly so the user can react to the reasoning, not just the conclusion.

If the user's answer is vague, go deeper. If the important decisions are already clear, stop probing and move the discussion toward a choice.

Useful prompts to keep in mind:
- What is the real goal behind this?
- What constraints or failure cases change the answer?
- What assumption might be wrong?
- Is there a simpler version worth choosing first?
- What decision still needs to be made before planning?

## Optional Visual Aids

When a problem is easier to understand visually than through text alone, propose lightweight visual aids. Only enter this branch after the user agrees.

Visual aids should help the user understand or compare one key decision at a time. They are for clarification and convergence, not for polished implementation. If you need more guidance, read `references/visual-aids.md`.

## Know When To Hand Off

Do not slide into implementation while the direction is still unclear.

Once the core direction, constraints, and exclusions are clear, summarize what you understand and hand off naturally to `explore-and-plan` so the chosen direction can become an executable plan.

登录后下载/点赞/收藏 ❤ 5 | ★ 0

brainstorm

目录结构

SKILL.md

举报内容

提示