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.