Brainstorm 技能：AI 辅助技术方案规划与设计决策工具

brainstorm by boshu2/agentops

256 周安装量

234 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/boshu2/agentops --skill brainstorm

方法论开发项目管理

🇨🇳中文介绍

/brainstorm — 规划前明确目标

目的： 将“做什么”与“如何做”分开。在确定解决方案之前，先探索问题空间。

四个阶段：

评估清晰度 — 目标是否足够具体？
理解想法 — 解决什么问题，谁受益，现状如何？
探索方案 — 生成选项，比较权衡
记录设计 — 为 /plan 编写结构化输出

快速开始

/brainstorm "add user authentication"     # 完整的4阶段流程
/brainstorm                                # 提示输入目标

执行步骤

阶段 1：评估清晰度

如果用户提供了目标字符串，则对其进行评估。否则提示用户输入。

使用 AskUserQuestion 并提供选项来评估清晰度：

清晰 — 目标具体且可操作（例如，“为 API 添加 JWT 认证”）
模糊 — 目标存在但需要细化（例如，“提高安全性”）
探索中 — 尚无明确目标，仅有一个方向（例如，“关于认证的一些事情”）

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

阶段 2：理解想法

回答以下问题（根据需要探索代码库）：

这解决了什么问题？ — 用具体术语说明痛点。
谁受益？ — 最终用户、开发者、运维人员、CI 流水线？
现状如何？ — 当前状态、代码库中现有的方案、相关系统。
哪些约束条件重要？ — 性能、兼容性、安全性、时间线。

在继续之前总结发现。如果有任何不清楚的地方，询问用户。

阶段 3：探索方案

生成 2-3 个不同的方案。对于每个方案：

名称 — 简短标签（例如，“JWT 中间件”、“OAuth 代理”、“会话 Cookie”）
工作原理 — 2-3 句话
优点 — 它做对了什么
缺点 — 它做错了什么或推迟了什么
工作量 — 大致范围（小 / 中 / 大）

展示比较结果，并使用 AskUserQuestion 让用户选择一个方案或请求混合方案。

阶段 4：记录设计

生成日期标识符：YYYY-MM-DD-<目标标识符>（小写，连字符，无空格）。

将输出文件写入 .agents/brainstorm/YYYY-MM-DD-<标识符>.md：

---
id: brainstorm-YYYY-MM-DD-<goal-slug>
type: brainstorm
date: YYYY-MM-DD
---
# Brainstorm: <Goal>
## Problem Statement
## Approaches Considered
## Selected Approach
## Open Questions
## Next Step: /plan

所有五个部分都必须填写。“下一步”部分应包含一个具体的 /plan 调用建议，并将所选方案作为上下文。

如果 .agents/brainstorm/ 目录不存在，则创建它。

阶段 4 输出写入完毕 = 完成。没有后续阶段，没有循环。

写入输出文件后，验证：

文件存在于预期路径
所有 5 个部分（Problem Statement、Approaches Considered、Selected Approach、Open Questions、Next Step: /plan）都存在且非空

向用户报告文件路径。

示例 1：具体目标

User: /brainstorm "add rate limiting to the API"

Phase 1: Goal is clear — add rate limiting to the API.
Phase 2: Problem is uncontrolled request volume causing timeouts.
         Benefits operators and end users. No rate limiting exists today.
Phase 3: Three approaches — token bucket middleware, API gateway,
         per-route decorators. User picks token bucket.
Phase 4: Writes .agents/brainstorm/2026-02-17-rate-limiting.md

示例 2：模糊目标

User: /brainstorm "improve performance"

Phase 1: Goal is vague. Asks: "Which part? API response times,
         build speed, database queries, or something else?"
         User says: "API response times on the search endpoint."
Phase 2: Investigates search endpoint, finds N+1 queries.
Phase 3: Approaches — query optimization, caching layer, pagination.
Phase 4: Writes .agents/brainstorm/2026-02-17-search-performance.md

问题	原因	解决方案
Brainstorm 在阶段 1 循环，无法推进	经过后续提问后目标仍然过于模糊	提供一个具体的、可测试的问题陈述（例如，“将 API 搜索延迟降低到 200 毫秒以下”，而不是“提高性能”）。
输出文件缺少一个或多个必需部分	阶段 4 被中断或技能提前终止	使用相同的目标重新运行 `/brainstorm`；验证输出中是否包含所有 5 个部分（`Problem Statement`、`Approaches Considered`、`Selected Approach`、`Open Questions`、`Next Step: /plan`）。
`.agents/brainstorm/` 目录未创建	技能无法创建目录（权限或路径问题）	使用 `mkdir -p .agents/brainstorm` 手动创建，然后重新运行。
“下一步”部分中的 `/plan` 调用过于通用或不完整	所选方案不够具体，无法生成具体的计划命令	编辑输出文件以完善所选方案，然后构建一个包含方案名称和关键约束的 `/plan` 调用。
Brainstorm 在阶段 3 只产生一个方案	问题空间狭窄或目标约束过多	稍微放宽目标，或明确要求提供替代方案（例如，“考虑缓存方案和查询优化方案”）。

skills/plan/SKILL.md — 将所选方案分解为可执行的任务

🇺🇸English

/brainstorm — Clarify Goals Before Planning

Purpose: Separate WHAT from HOW. Explore the problem space before committing to a solution.

Four phases:

Assess clarity — Is the goal specific enough?
Understand idea — What problem, who benefits, what exists?
Explore approaches — Generate options, compare tradeoffs
Capture design — Write structured output for /plan

Quick Start

/brainstorm "add user authentication"     # full 4-phase process
/brainstorm                                # prompts for goal

Execution Steps

Phase 1: Assess Clarity

If the user provided a goal string, evaluate it. Otherwise prompt for one.

Use AskUserQuestion with options to gauge clarity:

clear — Goal is specific and actionable (e.g., "add JWT auth to the API")
vague — Goal exists but needs narrowing (e.g., "improve security")
exploring — No firm goal yet, just a direction (e.g., "something with auth")

If vague or exploring , ask follow-up questions to sharpen the goal before proceeding. Do NOT move to Phase 2 until you have a concrete problem statement (one sentence, testable).

Phase 2: Understand the Idea

Answer these questions (use codebase exploration as needed):

What problem does this solve? — State the pain point in concrete terms.
Who benefits? — End users, developers, operators, CI pipeline?
What exists today? — Current state, prior art in the codebase, adjacent systems.
What constraints matter? — Performance, compatibility, security, timeline.

Summarize findings before moving on. If anything is unclear, ask the user.

Phase 3: Explore Approaches

Generate 2-3 distinct approaches. For each:

Name — Short label (e.g., "JWT middleware", "OAuth proxy", "Session cookies")
How it works — 2-3 sentences
Pros — What it gets right
Cons — What it gets wrong or defers
Effort — Rough scope (small / medium / large)

Present the comparison and use AskUserQuestion to let the user pick an approach or request a hybrid.

Phase 4: Capture Design

Generate a date slug: YYYY-MM-DD-<goal-slug> (lowercase, hyphens, no spaces).

Write the output file to .agents/brainstorm/YYYY-MM-DD-<slug>.md:

---
id: brainstorm-YYYY-MM-DD-<goal-slug>
type: brainstorm
date: YYYY-MM-DD
---
# Brainstorm: <Goal>
## Problem Statement
## Approaches Considered
## Selected Approach
## Open Questions
## Next Step: /plan

All five sections must be populated. The "Next Step" section should contain a concrete /plan invocation suggestion with the selected approach as context.

Create the .agents/brainstorm/ directory if it does not exist.

Termination

Phase 4 output written = done. No further phases, no loops.

Validation

After writing the output file, verify:

File exists at the expected path
All 5 sections (Problem Statement, Approaches Considered, Selected Approach, Open Questions, Next Step: /plan) are present and non-empty

Report the file path to the user.

Examples

Example 1: Specific goal

User: /brainstorm "add rate limiting to the API"

Phase 1: Goal is clear — add rate limiting to the API.
Phase 2: Problem is uncontrolled request volume causing timeouts.
         Benefits operators and end users. No rate limiting exists today.
Phase 3: Three approaches — token bucket middleware, API gateway,
         per-route decorators. User picks token bucket.
Phase 4: Writes .agents/brainstorm/2026-02-17-rate-limiting.md

Example 2: Vague goal

User: /brainstorm "improve performance"

Phase 1: Goal is vague. Asks: "Which part? API response times,
         build speed, database queries, or something else?"
         User says: "API response times on the search endpoint."
Phase 2: Investigates search endpoint, finds N+1 queries.
Phase 3: Approaches — query optimization, caching layer, pagination.
Phase 4: Writes .agents/brainstorm/2026-02-17-search-performance.md

Troubleshooting

Problem	Cause	Solution
Brainstorm loops in Phase 1 without advancing	Goal remains too vague after follow-up questions	Provide a concrete, testable problem statement (e.g., "reduce API search latency below 200ms" instead of "improve performance").
Output file missing one or more required sections	Phase 4 was interrupted or the skill terminated early	Re-run `/brainstorm` with the same goal; verify all 5 sections (`Problem Statement`, `Approaches Considered`, `Selected Approach`, `Open Questions`, `Next Step: /plan`) are present in the output.
directory not created