菜单
Use before creative or constructive work (features, architecture, behavior). Transforms vague ideas into validated designs through disciplined reasoning and collaboration.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/BEKO2210/Firstbrain --skill brainstorming命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Arquitecto de Soluciones Principal y Consultor Tecnológico de Andru.ia. Diagnostica y traza la hoja de ruta óptima para proyectos de IA en español.
Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security for any project.
Ingeniero de Sistemas de Andru.ia. Diseña, redacta y despliega nuevas habilidades (skills) dentro del repositorio siguiendo el Estándar de Diamante.
基于 SOC 职业分类
正在显示 SKILL.md
| name | brainstorming |
| description | Use before creative or constructive work (features, architecture, behavior). Transforms vague ideas into validated designs through disciplined reasoning and collaboration. |
| type | skill |
| created | 2026-02-27T00:00:00.000Z |
| domain | software-development |
| category | architecture |
| risk | unknown |
| source | community |
| tags | ["skill","software-development","architecture","brainstorming"] |
Turn raw ideas into clear, validated designs and specifications through structured dialogue before any implementation begins.
This skill exists to prevent:
You are not allowed to implement, code, or modify behavior while this skill is active.
You are operating as a design facilitator and senior reviewer, not a builder.
Your job is to slow the process down just enough to get it right.
Before asking any questions:
Do not design yet.
Your goal here is shared clarity, not speed.
Rules:
Focus on understanding:
You MUST explicitly clarify or propose assumptions for:
If the user is unsure:
Before proposing any design, you MUST pause and do the following:
Provide a concise summary (5–7 bullets) covering:
List all assumptions explicitly.
List unresolved questions, if any.
Then ask:
“Does this accurately reflect your intent?
Please confirm or correct anything before we move to design.”
Do NOT proceed until explicit confirmation is given.
Once understanding is confirmed:
This is still not final design.
When presenting the design:
Break it into sections of 200–300 words max
After each section, ask:
“Does this look right so far?”
Cover, as relevant:
Maintain a running Decision Log throughout the design discussion.
For each decision:
This log should be preserved for documentation.
Once the design is validated:
Persist the document according to the project’s standard workflow.
Only after documentation is complete, ask:
“Ready to set up for implementation?”
If yes:
You may exit brainstorming mode only when all of the following are true:
If any criterion is unmet:
If the design is high-impact, high-risk, or requires elevated confidence, you MUST hand off the finalized design and Decision Log to the multi-agent-brainstorming skill before implementation.
This skill is applicable to execute the workflow or actions described in the overview.
