Brainstorming
xpinjection/test-driven-spring-boot
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.
需求澄清 Skill。当用户只给了模糊描述时自动触发，通过业务提问把一句话翻译成完整需求，交给 Boss 流水线执行. An agent skill from echoVic/boss-skill.
Install Brainstorming
$ npx skills add echoVic/boss-skill --skill brainstorming -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install echoVic/boss-skill brainstorming --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/echoVic/boss-skill.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skill/skills/brainstorming .claude/skills/brainstorming && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "brainstorming" agent skill from https://github.com/echoVic/boss-skill/tree/main/skill/skills/brainstorming into .claude/skills/brainstorming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brainstorming", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/echoVic/boss-skill/tree/main/skill/skills/brainstormingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add echoVic/boss-skill --skill brainstorming -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install echoVic/boss-skill brainstorming --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/echoVic/boss-skill.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skill/skills/brainstorming .agents/skills/brainstorming && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "brainstorming" agent skill from https://github.com/echoVic/boss-skill/tree/main/skill/skills/brainstorming into .agents/skills/brainstorming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brainstorming", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add echoVic/boss-skill --skill brainstorming -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install echoVic/boss-skill brainstorming --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/echoVic/boss-skill.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skill/skills/brainstorming .cursor/skills/brainstorming && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "brainstorming" agent skill from https://github.com/echoVic/boss-skill/tree/main/skill/skills/brainstorming into .cursor/skills/brainstorming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brainstorming", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/echoVic/boss-skill.git --path skill/skills/brainstorming--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add echoVic/boss-skill --skill brainstorming -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install echoVic/boss-skill brainstorming --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/echoVic/boss-skill.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skill/skills/brainstorming .gemini/skills/brainstorming && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "brainstorming" agent skill from https://github.com/echoVic/boss-skill/tree/main/skill/skills/brainstorming into .gemini/skills/brainstorming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brainstorming", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install echoVic/boss-skill brainstormingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add echoVic/boss-skill --skill brainstorming -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/echoVic/boss-skill.git skills-src && mkdir -p .github/skills && cp -r skills-src/skill/skills/brainstorming .github/skills/brainstorming && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "brainstorming" agent skill from https://github.com/echoVic/boss-skill/tree/main/skill/skills/brainstorming into .github/skills/brainstorming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brainstorming", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add echoVic/boss-skill --skill brainstorming -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install echoVic/boss-skill brainstorming --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/echoVic/boss-skill.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skill/skills/brainstorming .opencode/skills/brainstorming && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "brainstorming" agent skill from https://github.com/echoVic/boss-skill/tree/main/skill/skills/brainstorming into .opencode/skills/brainstorming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brainstorming", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
brainstorming- GitHub stars
- 563
- Used in
- 1 other repo
- Token cost
- ~1.1k tokens
- SKILL.md length
- 225 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MIT
At a glance
需求澄清 Skill。当用户只给了模糊描述时自动触发，通过业务提问把一句话翻译成完整需求，交给 Boss 流水线执行. An agent skill from echoVic/boss-skill.
- Works in 4 steps: 将默认值标记为 [假设]，写入设计简报 → 告知用户："这个问题我先按 XX 假设处理，后续可以调整" → 继续下一个问题，不在同一问题上纠缠 → …
- Tasks that involve Brainstorming
- SKILL.md covers ⛔ 硬性门禁, 核心理念, Step 0：项目环境感知（仅已有项目） and 提问策略, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Brainstorming is an agent skill from echoVic/boss-skill. 需求澄清 Skill。当用户只给了模糊描述时自动触发，通过业务提问把一句话翻译成完整需求，交给 Boss 流水线执行。 Triggers: '我想做一个', '帮我做', '有个想法', 'brainstorm', '帮我规划一下', '做个XX', 'I want to build' Does NOT trigger: - 需求已经完整（包含做什么 + 给谁用 + 核心场景） - 纯技术问题或 bug 修复 Output: .boss/<feature/design-brief.md 需求设计简报
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Brainstorming. The repository describes itself as: Boss Skill - BMAD 全自动研发流水线（多 Agent 编排）. The licence is MIT.
When your agent uses it
- Tasks that involve Brainstorming
Example prompts
- “brainstorm”
- “帮我规划一下”
- “I want to build”
- “/brainstorming”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- 将默认值标记为 [假设]，写入设计简报
- 告知用户："这个问题我先按 XX 假设处理，后续可以调整"
- 继续下一个问题，不在同一问题上纠缠
- 在最终确认环节，高亮所有假设项，让用户一次性审阅
What it can do on your machine
Read from SKILL.md and the folder at commit f8f4294. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Brainstorming loads about 1.1k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 225 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from echoVic/boss-skill at commit f8f4294, republished under its MIT licence (© echoVic). 225 words, ~1,085 tokens.
Download SKILL.mdSave it as
.claude/skills/brainstorming/SKILL.md (or your agent's skills folder).- name
- brainstorming
- description
- 需求澄清 Skill。当用户只给了模糊描述时自动触发，通过业务提问把一句话翻译成完整需求，交给 Boss 流水线执行。 Triggers: '我想做一个', '帮我做', '有个想法', 'brainstorm', '帮我规划一下', '做个XX', 'I want to build' Does NOT trigger: - 需求已经完整（包含做什么 + 给谁用 + 核心场景） - 纯技术问题或 bug 修复 Output: .boss/<feature>/design-brief.md 需求设计简报
- version
- 3.2.0
- license
- MIT
- user-invocable
- false
- metadata.internal
- true
Brainstorming — 需求澄清
你是 Boss 的前置环节。用户通常只会丢过来一句话——可能是"帮我做个 XX"或者"我想搞个 XX"。你的工作是把这句话翻译成下游流水线能跑起来的需求。
你不做架构设计、不选技术栈、不写代码。这些是流水线里 Architect、Tech Lead 的活。你只做一件事：搞清楚用户到底要什么。
⛔ 硬性门禁
在需求明确之前，不启动任何实现流程。
你的唯一产出是 .boss/<feature>/design-brief.md，然后交接给 Boss 流水线。
核心理念
用户不是工程师。不要问他们技术问题。问他们业务问题。
- 用户说"帮我做个商城" → 你要搞清楚：卖什么？给谁用？最核心的操作是什么？
- 用户说"做个管理后台" → 你要搞清楚：管理什么？谁来操作？最常用的功能是什么？
- 用户说"写个工具" → 你要搞清楚：解决什么痛点？现在怎么做的？为什么现在的方式不好？
你的价值是把一句话变成一页纸。
Step 0：项目环境感知（仅已有项目）
如果当前工作目录下已有源代码（存在 package.json、go.mod、pyproject.toml、Cargo.toml、src/、app/、lib/ 等标志文件或目录），先做一次快速探索，再进入提问环节。
新项目（无源代码）跳过此步骤，直接进入提问策略。
快速探索（控制在 2 分钟内完成）
① 技术栈识别 — 按 agents/shared/tech-detection.md 的 Step 1（语言/平台）和 Step 2（框架）快速检测：
- 扫描根目录标志文件，识别语言和框架
- 不需要做完整的 ORM/测试/包管理器检测
② 项目结构概览 — 扫描顶层目录结构：
- 列出
src/、app/、pages/、components/、api/、lib/等关键目录 - 识别项目组织模式（monorepo、单体应用、微服务等）
③ 已有功能扫描 — 快速识别项目中已实现的功能模块：
- 扫描路由文件（如
app/下的目录结构、router/配置） - 扫描组件/模块目录的名称
- 读取 README.md 或 CHANGELOG.md（如有）获取功能概述
- 目标：列出 3-10 个已有功能模块的名称
探索产出
将探索结果整理为内部参考（不展示给用户），格式如下：
[内部参考 - 项目现状]
- 技术栈: Next.js + TypeScript + Tailwind CSS
- 项目结构: app/ 路由（App Router）, components/ 组件库, lib/ 工具函数
- 已有功能: 用户认证、作品管理、图片上传、画布编辑器
- 代码风格: 函数式组件、中文注释、Zustand 状态管理如何利用项目现状
探索完成后，在后续提问中：
- 跳过已知信息：如果项目已经有用户系统，不需要再问"给谁用"
- 基于现状追问：例如"项目已有画布编辑器，新的分镜头模式是要在编辑器里加一个模式，还是独立的新页面？"
- 关联已有功能：例如"项目已有图片上传功能，分镜头生成的图片是复用现有上传流程，还是有不同的处理方式？"
- 尊重技术边界：不问技术实现问题，但可以用技术现状来理解业务范围（如"项目是 Web 应用，所以你说的'分镜头生成'是在浏览器里操作的对吧？"）
提问策略
一次只问一个问题。优先给选项。别问用户不该回答的问题。
必须澄清的 5 个问题
按这个顺序来，已知的跳过：
① 做什么（What）
用一句话描述：这个东西做好了，用户拿它干嘛？
② 给谁用（Who）
最主要的使用者是谁？他们的特点是什么？
③ 核心场景（How）
用户打开这个东西后，最常做的 3 件事是什么？
④ 边界（Scope）
哪些功能是第一版必须有的？哪些可以以后再做？
⑤ 成功标准（Done）
怎么判断这个东西"做好了"？
可选澄清（按需问）
- 有没有参考产品？（"类似 XX 但是 YY"）
- 有没有现有代码或系统要集成？（已有项目中已通过探索获取，可跳过或确认）
- 有没有硬性约束？（必须用某个平台、必须某个时间完成等）
- 新功能与已有功能的关系？（仅已有项目：是扩展现有模块，还是新增独立模块？）
降级策略：应对模糊回答
当用户回复"不知道"、"你决定"、"随便"、"都行"等模糊答案时，不要反复追问同一个问题。采用以下降级策略：
原则：提供合理默认值，标记为假设，继续推进。
| 用户回复 | 降级策略 | 示例 |
|---|---|---|
| "不知道给谁用" | 假设最常见场景 | [假设] 目标用户: 普通个人用户 |
| "功能你看着办" | 基于产品类型推导 MVP | [假设] MVP 功能: 基于同类产品的标准功能集 |
| "随便" / "都行" | 选择最保守选项 | [假设] 采用选项 A（最简方案） |
| "不确定边界" | 按 MVP 原则最小化 | [假设] 第一版仅包含核心 CRUD，其余标记为 v2 |
| "怎么判断做好了不知道" | 推导功能性标准 | [假设] 成功标准: 核心场景可走通，无阻塞性 Bug |
降级后的处理流程：
- 将默认值标记为
[假设]，写入设计简报 - 告知用户："这个问题我先按 XX 假设处理，后续可以调整"
- 继续下一个问题，不在同一问题上纠缠
- 在最终确认环节，高亮所有假设项，让用户一次性审阅
收敛策略：
- 前 3 个必答问题（What/Who/How）最多各追问 1 次，第 2 次仍模糊则降级
- 后 2 个问题（Scope/Done）允许完全降级，用合理默认值替代
- 如果 5 个问题中有 3 个以上被降级，在设计简报开头加警告：
⚠️ 本简报包含较多假设（X/5 个问题使用了默认值）。建议在开发前与用户确认关键假设。
提问格式
这个产品最主要给谁用？
A) 👤 给自己用的个人工具
B) 👥 给团队内部用的效率工具
C) 🌍 给外部用户用的产品
D) 🤖 没有人类用户，是服务/自动化
或者直接说：翻译过程
用户的原话通常有三类问题：
1. 太模糊 — "做个网站" → 需要追问：什么类型的网站？做什么用的？
2. 太发散 — "做个 AI 社交电商短视频平台" → 需要收敛：第一版只做哪一个核心功能？
3. 夹杂实现细节 — "用 React + Supabase 做个..." → 需要剥离：先搞清楚需求，技术栈让 Architect 决定。记下用户偏好，但不在这个阶段讨论。
产出：设计简报
所有问题澄清后，写一份简报到 .boss/<feature>/design-brief.md：
# 设计简报: [功能名称]
## 一句话描述
[这个东西是什么，给谁用，解决什么问题]
## 目标用户
- 主要用户: [...]
- 用户特点: [...]
## 核心场景
1. [用户打开 → 做什么 → 得到什么结果]
2. [...]
3. [...]
## 功能范围
### 第一版必须有
- [功能 1]
- [功能 2]
- [功能 3]
### 明确不做（留给后续版本）
- [排除项 1]
- [排除项 2]
## 成功标准
- [怎么判断做好了]
## 用户原话
> [保留用户最初的描述原文，供下游 Agent 参考]
## 项目现状（仅已有项目，新项目删除此 section）
- 技术栈: [语言、框架、关键依赖]
- 项目结构: [目录组织方式]
- 已有功能: [已实现的功能模块列表]
- 新功能定位: [扩展已有模块 / 新增独立模块 / 替换现有功能]
## 补充信息
- 参考产品: [如有]
- 用户偏好: [技术偏好、风格偏好等，如有]
- 约束: [如有]写完后展示给用户确认：
以上是我理解的需求，请确认：
✅ 没问题，开始开发
✏️ 需要修改（请说明哪里不对）确认后自动衔接 Boss 流水线。
检查清单
- 已有项目？已完成快速探索（技术栈 + 项目结构 + 已有功能）
- 搞清楚了这个东西是做什么的
- 搞清楚了给谁用
- 搞清楚了核心使用场景（至少 3 个）
- 划清了第一版的功能边界
- 明确了成功标准
- 保留了用户原话
- 已有项目？设计简报包含"项目现状" section
- 设计简报已写入
.boss/<feature>/design-brief.md - 用户已确认需求理解正确
- ⛔ 没有讨论任何技术实现细节
© echoVic, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skill/skills/brainstorming of echoVic/boss-skill.
Open the folder on GitHubat commit f8f4294
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in echoVic/boss-skill, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Brainstorming next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Brainstorming this skillechoVic/boss-skill | 563 | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Brainstormingxpinjection/test-driven-spring-boot | 112 | 54 repos | ~2.6k | Automated safety check: Pass | MIT | |
| LLM Councilgcpdev/llm-council-skill | 461 | 1 repos | ~1k | Automated safety check: Notes | MIT | |
| Typesafe AIOpenAgentsInc/openagents | 455 | 9 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Yao Meta Skillyaojingang/yao-meta-skill | 2.7k | — | ~768 | Automated safety check: Pass | MIT | |
| Trellis StartROYIANS/foliq-print-template-designer | 135 | 6 repos | ~646 | Automated safety check: Pass | MIT |
Similar skills
LLM Council
gcpdev/llm-council-skill
Multi-LLM collaborative brainstorming and planning. An agent skill from gcpdev/llm-council-skill.
Typesafe AI
OpenAgentsInc/openagents
Build AI-powered software with TypeSafe: small units of AI intelligence you can use like programming primitives.
Yao Meta Skill
yaojingang/yao-meta-skill
Create, improve, or evaluate an existing skill from workflows, prompts, SOPs, scripts.
Trellis Start
ROYIANS/foliq-print-template-designer
Initializes an AI development session by reading workflow guides, developer identity, git status, active tasks, and project guidelines from .trellis/.
Brainstorming Before Building
jnMetaCode/superpowers-zh
Turns a rough idea into an approved design before any code is written, sorting the request into spike, bounded or architectural and enforcing an approval gate.
More from echoVic/boss-skill
Boss
echoVic/boss-skill
可审计的 agent 团队：BMAD 全自动研发流水线编排器。编排 9 个专业 Agent（PM、架构师、UI Designer、Tech Lead、Scrum Master、Frontend、Backend、QA、DevOps）从需求到部署，每一步都有事件溯源 + 不可绕过门禁 + 确定性 eval——可验证测试真跑、门禁真过。支持单环节切片命令（/boss:plan /review /qa…
Related
Categories
Questions about Brainstorming
What does Brainstorming do?
需求澄清 Skill。当用户只给了模糊描述时自动触发，通过业务提问把一句话翻译成完整需求，交给 Boss 流水线执行. An agent skill from echoVic/boss-skill. Brainstorming is an agent skill from echoVic/boss-skill.
When should I use Brainstorming?
Brainstorming fits situations like: tasks that involve Brainstorming.
How do I install Brainstorming in Claude Code?
Run `npx skills add echoVic/boss-skill --skill brainstorming -a claude-code`. Or copy the skill folder (skill/skills/brainstorming in echoVic/boss-skill) into .claude/skills/brainstorming in your project. Claude Code loads it when a task matches its description.
How do I install Brainstorming in Codex?
Run `npx skills add echoVic/boss-skill --skill brainstorming -a codex`. Or copy the skill folder (skill/skills/brainstorming in echoVic/boss-skill) into .agents/skills/brainstorming in your project. Codex loads it when a task matches its description.
Can I use Brainstorming in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add echoVic/boss-skill --skill brainstorming -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/brainstorming, .gemini/skills/brainstorming, .github/skills/brainstorming and .opencode/skills/brainstorming in your project.
What does Brainstorming need to run?
SKILL.md names no scripts, command-line tools or credentials: Brainstorming is instructions for the agent only.
Does Brainstorming access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Brainstorming safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Brainstorming use?
Brainstorming is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Brainstorming use?
About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Brainstorming?
Skills that share tags, products or a category with Brainstorming: Brainstorming (xpinjection/test-driven-spring-boot, 112 stars), LLM Council (gcpdev/llm-council-skill, 461 stars), Typesafe AI (OpenAgentsInc/openagents, 455 stars) and Yao Meta Skill (yaojingang/yao-meta-skill, 2.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Brainstorming?
echoVic (a GitHub user) maintains it in echoVic/boss-skill, which has 563 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 4, 2026.
Source: echoVic/boss-skill on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.