Agent Skills › codeaholicguy/ai-devkit › brainstorm

brainstorm

GitHub

提供发散到收敛的思维框架，用于头脑风暴、创意生成、方案对比及决策评估。通过设定基线、多角度发散、挑战假设和精简比较，输出最优选项及下一步计划。

skills/brainstorm/SKILL.md codeaholicguy/ai-devkit

Trigger Scenarios

用户请求头脑风暴或构思创意需要评估产品想法或技术路径要求比较概念并缩小选择范围

Install

npx skills add codeaholicguy/ai-devkit --skill brainstorm -g -y

More Options

Use without installing

npx skills use codeaholicguy/ai-devkit@brainstorm

指定 Agent (Claude Code)

npx skills add codeaholicguy/ai-devkit --skill brainstorm -a claude-code -g -y

安装 repo 全部 skill

npx skills add codeaholicguy/ai-devkit --all -g -y

预览 repo 内 skill

npx skills add codeaholicguy/ai-devkit --list

SKILL.md

Frontmatter

{
    "name": "brainstorm",
    "description": "AI DevKit · Use when the user asks to brainstorm, ideate, generate ideas, expand options, challenge ideas, pressure-test ideas, compare concepts, narrow choices, name something, plan content angles, explore strategy, evaluate product ideas, technical approaches, experiments, or decisions."
}

Brainstorm

Run a compact diverge-to-converge loop.

Workflow

Frame: goal, constraints, audience, success criteria, assumptions.
Baseline: state the simplest honest solution first. Every option must beat it; the baseline stays a candidate.
Diverge: distinct options across practical, high-leverage, and unusual angles.
Challenge: weak assumptions, failure modes, tradeoffs, rejections. Always: reject speculative generality (each abstraction, layer, flag, and data copy needs a current caller) and verify load-bearing "needed" claims in the consuming code, not doc assertions.
Compare: only relevant criteria, plus deletion cost (how easily the option can be removed later). Ties go to the smaller option.
Converge: strongest 3 picks with rationale and a next step. Self-review first: for each new constant, object, layer, and flag ask "why do we need this?" Cut answers that are only messaging or future-proofing.

Formats

Use Quick by default. Use Deep only for ambiguous or high-stakes decisions. Ask at most one clarifying question only if missing context would materially change the brainstorm; otherwise state assumptions and proceed.

Quick: clusters, challenges, 3 picks.
Deep: assumptions, clusters, evaluation table, recommendation.
Naming: tone groups, fit, ambiguity, pronunciation.
Technical: approaches, tradeoffs, risks, validation.
Content: angles, hooks, audiences, outlines.

Avoid filler, near-duplicates, generic best practices, premature recommendations, and scope without a current caller. If asked for more ideas, explore a new axis before listing variants.