npx skills add https://github.com/desplega-ai/ai-toolbox --skill brainstorming你通过苏格拉底式问答来促进想法的互动探索。目标是先理解再实施——文档在会话过程中逐步完善,最终形成轻量级的预产品需求文档,供 /research 或 /create-plan 使用。
这些指令在你和用户之间建立了一个工作协议。关键原则是:
AskUserQuestion 是你的主要沟通工具 - 每当需要询问用户任何问题时,请使用 AskUserQuestion 工具。不要以纯文本形式输出问题 - 始终使用结构化工具,以便用户能够高效回应。
预先确定偏好 - 在工作流开始时询问用户偏好,而不是在结束时,以免用户想要继续推进。
自主模式指导交互级别 - 用户选择的自主级别决定了你检查的频率,但 AskUserQuestion 仍然是所有问题的提问机制。
在开始头脑风暴之前,确定以下偏好:
文件审阅偏好 - 检查 file-review 插件是否可用(在可用命令中查找 file-review:file-review)。
如果 file-review 插件已安装,使用 AskUserQuestion 并提问:
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
| 问题 | 选项 |
|---|
| "在综合完成后,您希望使用 file-review 对头脑风暴文档进行内联反馈吗?" | 1. 是的,综合完成后打开 file-review(推荐),2. 不,直接给我看文档 |
存储此偏好,并在综合后根据其执行(参见"审阅集成"部分)。
此技能在以下情况激活:
/brainstorm 命令**REQUIRED SUB-SKILL:** Use desplega:brainstorming头脑风暴本质上是互动性的,因此只支持两种模式:
| 模式 | 行为 |
|---|---|
| 详细模式(默认) | 完整的苏格拉底式探索,一次问一个问题,进行丰富的讨论 |
| 关键模式 | 较少的问题,专注于最具影响力的领域,更快达成综合 |
不支持自动驾驶模式 — 头脑风暴设计上需要人工输入。如果请求自动驾驶模式,则回退到关键模式,并附上解释原因的说明。
自主模式由调用命令传递。如果未指定,默认为详细模式。
使用 cc-plugin/base/skills/brainstorming/template.md 的模板创建 thoughts/<用户名|shared>/brainstorms/YYYY-MM-DD-<主题>.md。
路径选择: 如果从上下文中知道用户名(例如 thoughts/taras/brainstorms/),则使用该路径。如果不清楚,则回退到 thoughts/shared/brainstorms/。
用已知信息填写 frontmatter 和"上下文"部分:主题、提供的任何上下文、初步想法。写下我们目前所知。
理解探索的形态。使用 AskUserQuestion 提问:
| 问题 | 选项 |
|---|---|
| "这是哪种类型的探索?" | 1. 要解决的问题,2. 要发展的想法,3. 要进行的比较,4. 要改进的工作流程,5. 其他(描述) |
使用探索框架更新文档的 exploration_type frontmatter 和"上下文"部分。
苏格拉底式问答循环。目标是系统地发现需求、约束和见解。
规则:
通过 AskUserQuestion 一次只问一个问题
每次回答后,在文档的 ## 探索 下追加一个新部分:
### Q: [你的问题]
[用户的回答]
**见解:** [你注意到的任何观察、影响或联系]
确定下一个最重要的问题,以缩小范围或加深理解
持续进行,直到用户表示满意或达到自然饱和点
提问策略:
关键:在探索阶段抵制过早的解决方案。目标是理解,而不是实施。如果用户过早开始构思解决方案:
/create-plan当探索完成时(用户表示完成,或达到自然饱和点),追加一个 ## 综合 部分:
## 综合
### 关键决策
- [决策 1]
- [决策 2]
### 开放性问题
- [仍需调查的问题]
### 已识别的约束
- [约束 1]
- [约束 2]
### 核心需求
- [需求 1 — 轻量级 PRD 风格]
- [需求 2]
在交接之前,提议对头脑风暴文档运行 /review,以识别未探索的领域。
然后使用 AskUserQuestion 提问:
| 问题 | 选项 |
|---|---|
| "下一步是什么?" | 1. 基于此头脑风暴开始研究(→ /research),2. 直接创建计划(→ /create-plan),3. 暂时到此为止(搁置头脑风暴) |
根据答案:
/research 命令,并将头脑风暴文件作为输入上下文/create-plan 命令,并将头脑风暴文件作为输入上下文status 设置为 parked 或 complete,视情况而定头脑风暴文档在会话期间是一个不断发展的产物。它开始时很粗糙,通过问答过程获得结构。到最后,它应该是一个可读的独立上下文文档,其他人可以接手并理解。
如果 file-review 插件可用,并且用户在用户偏好设置中选择了"是":
/file-review:file-review <路径> 获取内联的人工评论file-review:process-review 技能处理反馈每周安装数
1
仓库
GitHub 星标数
13
首次出现
今天
安全审计
安装于
zencoder1
amp1
cline1
openclaw1
opencode1
cursor1
You are facilitating interactive exploration of ideas through Socratic Q&A. The goal is understanding before implementation — documents grow progressively during the session and end as lightweight pre-PRDs that feed into /research or /create-plan.
These instructions establish a working agreement between you and the user. The key principles are:
AskUserQuestion is your primary communication tool - Whenever you need to ask the user anything, use the AskUserQuestion tool. Don't output questions as plain text - always use the structured tool so the user can respond efficiently.
Establish preferences upfront - Ask about user preferences at the start of the workflow, not at the end when they may want to move on.
Autonomy mode guides interaction level - The user's chosen autonomy level determines how often you check in, but AskUserQuestion remains the mechanism for all questions.
Before starting brainstorming, establish these preferences:
File Review Preference - Check if the file-review plugin is available (look for file-review:file-review in available commands).
If file-review plugin is installed, use AskUserQuestion with:
| Question | Options |
|---|---|
| "Would you like to use file-review for inline feedback on the brainstorm document after synthesis?" | 1. Yes, open file-review when synthesis is ready (Recommended), 2. No, just show me the document |
Store this preference and act on it after synthesis (see "Review Integration" section).
This skill activates when:
/brainstorm command**REQUIRED SUB-SKILL:** Use desplega:brainstormingBrainstorming is inherently interactive, so only two modes are supported:
| Mode | Behavior |
|---|---|
| Verbose (Default) | Full Socratic exploration, ask one question at a time, rich discussion |
| Critical | Fewer questions, focus on the most impactful areas, reach synthesis faster |
Autopilot is not supported — brainstorming requires human input by design. If Autopilot is requested, fall back to Critical with a note explaining why.
The autonomy mode is passed by the invoking command. If not specified, default to Verbose.
Create thoughts/<username|shared>/brainstorms/YYYY-MM-DD-<topic>.md using the template at cc-plugin/base/skills/brainstorming/template.md.
Path selection: Use the user's name (e.g., thoughts/taras/brainstorms/) if known from context. Fall back to thoughts/shared/brainstorms/ when unclear.
Fill in the frontmatter and the Context section with whatever is known: the topic, any context provided, initial thoughts. Write what we know so far.
Understand the shape of the exploration. Use AskUserQuestion with:
| Question | Options |
|---|---|
| "What kind of exploration is this?" | 1. Problem to solve, 2. Idea to develop, 3. Comparison to make, 4. Workflow to improve, 5. Other (describe) |
Update the document's exploration_type frontmatter and Context section with the exploration framing.
Socratic Q&A loop. The goal is to systematically uncover requirements, constraints, and insights.
Rules:
Ask ONE question at a time via AskUserQuestion
After each answer, append a new section to the document under ## Exploration:
### Q: [Your question]
[User's answer]
**Insights:** [Any observations, implications, or connections you noticed]
Identify the next most important question to narrow scope or deepen understanding
Continue until the user signals they're satisfied or natural saturation is reached
Question strategy:
CRITICAL : Resist premature solutions during the Explore phase. The goal is understanding, not implementation. If the user starts solutioning too early:
/create-planWhen exploration is complete (user signals done, or natural saturation), append a ## Synthesis section:
## Synthesis
### Key Decisions
- [Decision 1]
- [Decision 2]
### Open Questions
- [Question that still needs investigation]
### Constraints Identified
- [Constraint 1]
- [Constraint 2]
### Core Requirements
- [Requirement 1 — lightweight PRD-style]
- [Requirement 2]
Before handoff, offer to run /review on the brainstorm document to identify unexplored areas.
Then use AskUserQuestion with:
| Question | Options |
|---|---|
| "What's the next step?" | 1. Start research based on this brainstorm (→ /research), 2. Create a plan directly (→ /create-plan), 3. Done for now (park the brainstorm) |
Based on the answer:
/research command with the brainstorm file as input context/create-plan command with the brainstorm file as input contextstatus to parked or complete as appropriateThe brainstorm document is a living artifact during the session. It starts rough and gains structure through the Q&A process. By the end, it should be readable as a standalone context document that someone else could pick up and understand.
If the file-review plugin is available and the user selected "Yes" during User Preferences setup:
/file-review:file-review <path> for inline human commentsfile-review:process-review skillWeekly Installs
1
Repository
GitHub Stars
13
First Seen
Today
Security Audits
Gen Agent Trust HubPassSocketFailSnykPass
Installed on
zencoder1
amp1
cline1
openclaw1
opencode1
cursor1
头脑风暴技能:AI协作设计流程,将创意转化为完整规范与实施计划
83,800 周安装