Agent skill

Brainstorming

by feiskyer in feiskyer/claude-code-settings

Explore user intent, requirements, and design options through collaborative dialogue before implementation.

MITAuto-check passedDevelopment

Install Brainstorming

skills CLI
$ npx skills add feiskyer/claude-code-settings --skill brainstorming -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install feiskyer/claude-code-settings brainstorming --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/feiskyer/claude-code-settings.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/brainstorming .claude/skills/brainstorming && rm -rf skills-src

Use ~/.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/

Facts

Skill name
brainstorming
GitHub stars
1.7k
Token cost
~985 tokens
SKILL.md length
165 words
Files
8 (incl. scripts)
Skills in repo
12
Repo updated
First seen
Licence
MIT

At a glance

Explore user intent, requirements, and design options through collaborative dialogue before implementation.

  • Works in 9 steps: 探索项目上下文 — 检查文件、文档、最近的提交 → 适时提供可视化伴侣 —… → 提出澄清问题 — 每次只问一个,理解目的/约束/成功标准 → …
  • Describes something to build and design decisions are involved
  • SKILL.md covers 反模式:"这个太简单了不需要设计", 检查清单, 流程图 and 流程详解, plus 3 more sections
  • Runs JavaScript and Shell scripts from its folder

What it does

Brainstorming is an agent skill from feiskyer/claude-code-settings. Explore user intent, requirements, and design options through collaborative dialogue before implementation. Use before building new features, components, or systems — whenever the user describes something to build and design decisions are involved. Triggers: "brainstorm", "help me design", "think through the requirements", "头脑风暴", "设计方案", "梳理需求". Not for bug fixes, config changes, or tasks with an obvious implementation path.

Its SKILL.md is about 990 tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts (for example `scripts/helper.js`, `scripts/start-server.sh` and `scripts/stop-server.sh`).

It sits in Development, covering Brainstorming, Debugging and Architecture decision records. The repository describes itself as: Curated skills, sub-agents, and config templates that supercharge Claude Code — research, image gen, GitHub automation & more. The licence is MIT.

When your agent uses it

  • Describes something to build and design decisions are involved
  • Tasks that involve Brainstorming
  • Tasks that involve Debugging

Example prompts

  • “brainstorm”
  • “help me design”
  • “think through the requirements”
  • “/brainstorming”

Requirements

  • Node.js
  • A Bash shell

Workflow steps

9 steps, taken from the first numbered list in SKILL.md.

  1. 探索项目上下文 — 检查文件、文档、最近的提交
  2. 适时提供可视化伴侣 — 不要一开始就提供。当某个问题用"看"比"说"更清楚时,在那个时刻提出(单独一条消息);用户同意后为他们打开浏览器标签页。如果整个过程不需要可视化,就不要提。详见下方"可视化伴侣"章节。
  3. 提出澄清问题 — 每次只问一个,理解目的/约束/成功标准
  4. 提出 2-3 个方案 — 附带权衡分析和你的推荐
  5. 呈现设计 — 按复杂度分节展示,每节之后获得用户认可
  6. 编写设计文档 — 保存到 docs/specs/YYYY-MM-DD-<主题>-design.md 并提交
  7. 规格自审 — 快速检查占位符、矛盾、歧义、范围(见下方)
  8. 用户审阅规格 — 请用户审阅规格文件后再继续
  9. 过渡到实现 — 创建实施计划并开始工作

What it can do on your machine

Read from SKILL.md and the folder at commit 95dab59. 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

    Ships 5 files in scripts/ (JavaScript and Shell), which the agent can run.

    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 985 tokens when it runs. Until then it costs about 111 tokens; SKILL.md has 165 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~111
When it runs · the whole SKILL.md, loaded when a task matches
~985

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); the scripts in this folder are not scanned.

SKILL.md

The full file from feiskyer/claude-code-settings at commit 95dab59, republished under its MIT licence (© feiskyer). 165 words, ~985 tokens.

Download SKILL.mdSave it as .claude/skills/brainstorming/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
brainstorming
description
Explore user intent, requirements, and design options through collaborative dialogue before implementation. Use before building new features, components, or systems — whenever the user describes something to build and design decisions are involved. Triggers: "brainstorm", "help me design", "think through the requirements", "头脑风暴", "设计方案", "梳理需求". Not for bug fixes, config changes, or tasks with an obvious implementation path.

头脑风暴:从想法到设计

通过自然的协作对话,帮助用户将想法转化为完整的设计和规格文档。

先了解当前项目上下文,然后逐个提问来细化想法。一旦理解了要构建的内容,呈现设计方案并获得用户认可。

<HARD-GATE>
在呈现设计方案并获得用户认可之前,不要编写任何代码、搭建任何项目脚手架,或执行任何实现操作。无论项目看起来多简单,这一规则都适用。
</HARD-GATE>

反模式:"这个太简单了不需要设计"

一旦触发了这个 skill,即使项目看起来很简单(一个 todo list、一个单函数工具),也要走设计流程。"简单"项目恰恰最容易因为未检验的假设而浪费工作量。设计可以很短(对于真正简单的项目只需几句话),但必须呈现并获得认可。

检查清单

必须为以下每一项创建任务,并按顺序完成:

  1. 探索项目上下文 — 检查文件、文档、最近的提交
  2. 适时提供可视化伴侣 — 不要一开始就提供。当某个问题用"看"比"说"更清楚时,在那个时刻提出(单独一条消息);用户同意后为他们打开浏览器标签页。如果整个过程不需要可视化,就不要提。详见下方"可视化伴侣"章节。
  3. 提出澄清问题 — 每次只问一个,理解目的/约束/成功标准
  4. 提出 2-3 个方案 — 附带权衡分析和你的推荐
  5. 呈现设计 — 按复杂度分节展示,每节之后获得用户认可
  6. 编写设计文档 — 保存到 docs/specs/YYYY-MM-DD-<主题>-design.md 并提交
  7. 规格自审 — 快速检查占位符、矛盾、歧义、范围(见下方)
  8. 用户审阅规格 — 请用户审阅规格文件后再继续
  9. 过渡到实现 — 创建实施计划并开始工作

流程图

探索项目上下文 → 提出澄清问题 → 提出 2-3 个方案 → 分节呈现设计
    ↓
用户认可设计? —[否,修改]→ 返回呈现设计
    ↓ 是
编写设计文档 → 规格自审(就地修复) → 用户审阅规格?
    ↓                                      ↓ 需要修改 → 返回编写设计文档
    ↓                                      ↓ 通过
    └──────────────────────────────────── 开始实现

终态是开始实现。 用户批准规格后,创建分步实施计划并开始编码。

流程详解

理解想法:

  • 先了解当前项目状态(文件、文档、最近提交)
  • 在深入提问之前先评估范围:如果需求描述了多个独立子系统(例如"构建一个有聊天、文件存储、计费和分析的平台"),立即指出这一点。不要花时间细化一个需要先拆分的项目
  • 如果项目对一份规格来说太大,帮助用户分解为子项目:独立的部分有哪些,它们如何关联,应该按什么顺序构建?然后对第一个子项目走正常设计流程。每个子项目有自己的 规格 → 计划 → 实现 循环
  • 对范围合适的项目,逐个提问来细化想法
  • 尽量使用选择题,开放式也可以
  • 每条消息只问一个问题——如果某个话题需要更多探讨,拆成多个问题
  • 关注:目的、约束、成功标准

探索方案:

  • 提出 2-3 个不同方案及其权衡
  • 以对话方式呈现选项,附带你的推荐和理由
  • 先说你推荐的方案并解释为什么

呈现设计:

  • 一旦你认为理解了要构建的内容,呈现设计
  • 每节的详细程度与其复杂度匹配:简单的几句话,复杂的写到讲清为止
  • 每节之后询问用户是否正确
  • 覆盖:架构、组件、数据流、错误处理、测试
  • 准备好在某处不清楚时回头澄清

为隔离和清晰而设计:

  • 将系统拆分为更小的单元,每个单元有一个清晰的职责,通过定义良好的接口通信,可以独立理解和测试
  • 对每个单元,你应该能回答:它做什么,怎么使用它,它依赖什么?
  • 别人能不看内部实现就理解一个单元的功能吗?能修改内部实现而不破坏使用者吗?如果不能,说明边界需要重新划分
  • 更小、边界清晰的单元也更容易处理——对能在上下文中完整容纳的代码,推理更准确,编辑更可靠。当文件变得很大时,通常意味着它做了太多事

在已有代码库中工作:

  • 在提出变更之前先了解现有结构。遵循现有模式
  • 如果现有代码的问题影响到当前工作(例如文件过大、边界不清、职责纠缠),将针对性改进纳入设计——就像一个好开发者在工作时顺手改善接触到的代码
  • 不要提出无关的重构。专注于当前目标

设计之后

文档:

  • 将验证过的设计(规格)写入 docs/specs/YYYY-MM-DD-<主题>-design.md
    • (用户对规格存放位置的偏好优先于此默认路径)
  • 写作要清晰简洁——短句、主动语态、具体细节优于模糊概括
  • 将设计文档提交到 git

规格自审: 写完规格文档后,以全新的视角审视它:

  1. 占位符扫描: 有"TBD"、"TODO"、未完成的章节或模糊的需求吗?修复它们。
  2. 内部一致性: 各章节之间有矛盾吗?架构与功能描述匹配吗?
  3. 范围检查: 这是否聚焦到足以支撑一份实施计划?还是需要拆分?
  4. 歧义检查: 有没有哪个需求可能被理解为两种意思?如果有,选定一种并明确写出。

发现问题就地修复。不需要重新审阅——修完继续。对于复杂规格,可以参考 spec-document-reviewer-prompt.md(在本 skill 目录中)派遣 subagent 进行独立审阅。

用户审阅关卡: 规格自审通过后,请用户审阅:

"规格已编写并提交到 <路径>。请审阅,如有修改意见告诉我,没问题的话我们开始实现。"

等待用户回复。如果要求修改,修改后重新自审。只有用户认可后才继续。

实现:

  • 认可后,创建详细的分步实施计划
  • 将工作拆分为小的、可验证的增量
  • 按计划开始实现

核心原则

  • 每次只问一个问题 — 不要用多个问题轰炸用户
  • 优先选择题 — 比开放式问题更容易回答
  • 严格 YAGNI — 从设计中移除不必要的功能
  • 探索替代方案 — 总是在确定之前提出 2-3 个方案
  • 渐进验证 — 呈现设计,获得认可后再继续
  • 保持灵活 — 发现不对时回头澄清

可视化伴侣

基于浏览器的伴侣工具,用于在头脑风暴中展示 mockup、图表和可视化选项。它是一个工具而非模式。接受伴侣意味着它可用于需要可视化处理的问题,并不意味着每个问题都通过浏览器。

适时提供(just-in-time): 不要一开始就提供。等到某个问题用"看"确实比"说"更清楚——一个真正的 mockup/布局/图表问题,而不仅仅是一个涉及 UI 的话题。第一次出现这种情况时,单独发一条消息提出:

"接下来这个部分可能用看的比说的更清楚——我可以在浏览器标签页中为你展示 mockup、图表和对比。这个功能比较新,会消耗较多 token。要我开吗?"

这个提议必须是独立的一条消息。 不附带任何澄清问题、总结或其他内容。等待用户回复。如果接受,用 --open 启动服务器让浏览器自动打开。如果拒绝,继续纯文本模式,不再主动提供(除非用户主动提起)。

逐问题决策: 即使用户接受了伴侣,也要对每个问题决定是用浏览器还是终端。判断标准:用户看到它会不会比读到它理解得更好?

  • 用浏览器 展示本质是视觉的内容 — mockup、线框图、布局对比、架构图、并排的视觉设计
  • 用终端 展示本质是文字的内容 — 需求问题、概念选择、权衡列表、A/B/C/D 文字选项、范围决策

关于 UI 话题的问题不自动等于视觉问题。"这个上下文中'个性化'是什么意思?"是概念问题——用终端。"这两种向导布局哪个更好?"是视觉问题——用浏览器。

如果用户同意使用伴侣,在继续之前阅读详细指南: visual-companion.md(在本 skill 目录中)

© feiskyer, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 7 other files (scripts) in skills/brainstorming of feiskyer/claude-code-settings.

  • SKILL.md
  • scripts/frame-template.html
  • scripts/helper.js
  • scripts/server.cjs
  • scripts/start-server.sh
  • scripts/stop-server.sh
  • spec-document-reviewer-prompt.md
  • visual-companion.md

Open the folder on GitHubat commit 95dab59

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.

Brainstorming compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Brainstorming this skillfeiskyer/claude-code-settings1.7k—~985Automated safety check: PassMIT
Trellis Session Insightmindfold-ai/Trellis15k4 repos~1.7kAutomated safety check: PassAGPL-3.0
Context FieldsNeoVertex1/context-field147—~1.3kAutomated safety check: PassNone
Grounding A Designandrew-blake/melcloudhome142—~1.1kAutomated safety check: PassMIT
ScopeAlexZio00/sovereign-skills139—~3.8kAutomated safety check: PassMIT
Track Ideacdiggins/plato106—~1.3kAutomated safety check: PassMIT

Similar skills

  • Trellis Session Insight

    mindfold-ai/Trellis

    Reach into past AI conversation history through the trellis mem CLI.

    15k GitHub starsUsed in 4 repos~1.7k tokens
    DevelopmentAuto-check passed
  • Context Fields

    NeoVertex1/context-field

    Apply cognitive constraints that reshape thinking. An agent skill from NeoVertex1/context-field.

    147 GitHub stars~1.3k tokensUpdated 8 mo ago
    DevelopmentAuto-check passed
  • Grounding A Design

    andrew-blake/melcloudhome

    A skill your agent uses when about to propose, brainstorm, review or revise a design, fix approach or plan for a feature or behaviour change in this repo, including "brief" or "quick" design…

    142 GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Scope

    AlexZio00/sovereign-skills

    Scope definition before implementation — two modes. An agent skill from AlexZio00/sovereign-skills.

    139 GitHub stars~3.8k tokensUpdated 13 days ago
    DevelopmentAuto-check passed
  • Track Idea

    cdiggins/plato

    Log a new idea into tracker/ with elaboration — assumptions, design decisions, related work links, approach brainstorm, and simplest implementation.

    106 GitHub stars~1.3k tokensUpdated 11 days ago
    DevelopmentAuto-check passed
  • Comet Hotfix

    rpamis/comet

    Comet preset path: Bug fix / hotfix. An agent skill from rpamis/comet.

    3.2k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed

More from feiskyer/claude-code-settings

All 12 skills in this repo
  • Skill Creator

    feiskyer/claude-code-settings

    Create, refine, and benchmark agent skills. An agent skill from feiskyer/claude-code-settings.

    1.7k GitHub stars~7.6k tokensUpdated 11 days ago
    Auto-check passed
  • Deep Research

    feiskyer/claude-code-settings

    Multi-agent research orchestration: split a research goal into parallel sub-goals, run each via headless claude -p subprocesses, aggregate results into a polished report file.

    1.7k GitHub stars~2.6k tokensUpdated 11 days ago
    Auto-check: notes
  • Codex Skill

    feiskyer/claude-code-settings

    Leverage OpenAI Codex/GPT models for autonomous code implementation, code review, and plan review.

    1.7k GitHub stars~2.7k tokensUpdated 11 days ago
    Auto-check: warnings
  • GitHub Fix Issue

    feiskyer/claude-code-settings

    Fix GitHub issues end-to-end — analysis, branch creation, implementation, testing, and PR submission.

    1.7k GitHub stars~786 tokensUpdated 11 days ago
    Auto-check passed
  • GitHub Review PR

    feiskyer/claude-code-settings

    Review GitHub pull requests with detailed, multi-perspective code analysis using parallel subagents.

    1.7k GitHub stars~9.2k tokensUpdated 11 days ago
    Auto-check passed
  • Gpt Image Skill

    feiskyer/claude-code-settings

    Generate or edit images using OpenAI GPT Image API (gpt-image-2, gpt-image-1, etc).

    1.7k GitHub stars~1.4k tokensUpdated 11 days ago
    Auto-check passed

Questions about Brainstorming

What does Brainstorming do?

Explore user intent, requirements, and design options through collaborative dialogue before implementation. Brainstorming is an agent skill from feiskyer/claude-code-settings. Explore user intent, requirements, and design options through collaborative dialogue before implementation.

When should I use Brainstorming?

Brainstorming fits situations like: describes something to build and design decisions are involved; tasks that involve Brainstorming; tasks that involve Debugging.

How do I install Brainstorming in Claude Code?

Run `npx skills add feiskyer/claude-code-settings --skill brainstorming -a claude-code`. Or copy the skill folder (skills/brainstorming in feiskyer/claude-code-settings) 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 feiskyer/claude-code-settings --skill brainstorming -a codex`. Or copy the skill folder (skills/brainstorming in feiskyer/claude-code-settings) 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 feiskyer/claude-code-settings --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?

Going by SKILL.md and its folder, Brainstorming needs JavaScript and a shell for the scripts in its folder. Our summary lists: Node.js; A Bash shell.

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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Brainstorming use?

Brainstorming is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Brainstorming use?

About 985 tokens (SKILL.md is roughly 3.9k 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: Trellis Session Insight (mindfold-ai/Trellis, 15k stars), Context Fields (NeoVertex1/context-field, 147 stars), Grounding A Design (andrew-blake/melcloudhome, 142 stars) and Scope (AlexZio00/sovereign-skills, 139 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Brainstorming?

feiskyer (a GitHub user) maintains it in feiskyer/claude-code-settings, which has 1,658 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on September 27, 2026.

Source: feiskyer/claude-code-settings on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.