Brainstorming
ed3dai/ed3d-plugins
A skill your agent uses when creating or developing anything, before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning…
Structured brainstorm — from quick Socratic refinement to full C-suite strategy sessions.
$ npx skills add andrew-yangy/gru-ai --skill brainstorm -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install andrew-yangy/gru-ai brainstorm --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/andrew-yangy/gru-ai.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/brainstorm .claude/skills/brainstorm && 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 "brainstorm" agent skill from https://github.com/andrew-yangy/gru-ai/tree/main/.claude/skills/brainstorm into .claude/skills/brainstorm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brainstorm", 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/andrew-yangy/gru-ai/tree/main/.claude/skills/brainstormType 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 andrew-yangy/gru-ai --skill brainstorm -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install andrew-yangy/gru-ai brainstorm --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/andrew-yangy/gru-ai.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/brainstorm .agents/skills/brainstorm && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "brainstorm" agent skill from https://github.com/andrew-yangy/gru-ai/tree/main/.claude/skills/brainstorm into .agents/skills/brainstorm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brainstorm", 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 andrew-yangy/gru-ai --skill brainstorm -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install andrew-yangy/gru-ai brainstorm --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/andrew-yangy/gru-ai.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/brainstorm .cursor/skills/brainstorm && 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 "brainstorm" agent skill from https://github.com/andrew-yangy/gru-ai/tree/main/.claude/skills/brainstorm into .cursor/skills/brainstorm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brainstorm", 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/andrew-yangy/gru-ai.git --path .claude/skills/brainstorm--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 andrew-yangy/gru-ai --skill brainstorm -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install andrew-yangy/gru-ai brainstorm --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/andrew-yangy/gru-ai.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/brainstorm .gemini/skills/brainstorm && 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 "brainstorm" agent skill from https://github.com/andrew-yangy/gru-ai/tree/main/.claude/skills/brainstorm into .gemini/skills/brainstorm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brainstorm", 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 andrew-yangy/gru-ai brainstormInstalls 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 andrew-yangy/gru-ai --skill brainstorm -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/andrew-yangy/gru-ai.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/brainstorm .github/skills/brainstorm && 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 "brainstorm" agent skill from https://github.com/andrew-yangy/gru-ai/tree/main/.claude/skills/brainstorm into .github/skills/brainstorm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brainstorm", 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 andrew-yangy/gru-ai --skill brainstorm -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install andrew-yangy/gru-ai brainstorm --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/andrew-yangy/gru-ai.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/brainstorm .opencode/skills/brainstorm && 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 "brainstorm" agent skill from https://github.com/andrew-yangy/gru-ai/tree/main/.claude/skills/brainstorm into .opencode/skills/brainstorm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brainstorm", 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.
brainstormStructured brainstorm — from quick Socratic refinement to full C-suite strategy sessions.
Brainstorm is an agent skill from andrew-yangy/gru-ai. Structured brainstorm — from quick Socratic refinement to full C-suite strategy sessions. The missing step before /directive: figure out WHAT to do before telling agents to DO it. Takes a question or topic as argument.
Its SKILL.md is about 3.2k 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 and Tutoring and explanations. The repository describes itself as: Autonomous AI agent team for one-man companies. Context engineering + harness engineering drive a pipeline that brainstorms, builds, reviews, and ships. The licence is MIT.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 8fba479. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Brainstorm loads about 3.2k tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 932 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.
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.
The full file from andrew-yangy/gru-ai at commit 8fba479, republished under its MIT licence (© andrew-yangy). 932 words, ~3,190 tokens.
.claude/skills/brainstorm/SKILL.md (or your agent's skills folder).Read .claude/agent-registry.json to map roles to agent names. Use each agent's id as the subagent_type when spawning. The COO = operations/orchestration, the CTO = architecture/technical, the CPO = product/UX, the CMO = growth/marketing.
The CEO has a question: $ARGUMENTS
Read the question. Classify it before doing anything else.
Lightweight — single agent, Socratic dialogue, no external research:
Heavyweight — multi-agent parallel research, synthesis, options:
State the classification:
Classification: {lightweight | heavyweight}
Reasoning: {one sentence}For focused questions. One agent, interactive dialogue. Think 5-minute whiteboard chat.
Pick the right agent based on the question domain:
Spawn the agent (using the registry's id as subagent_type) with:
subagent_type).context/vision.md and .context/preferences.mdYou are {Name}, {Title}. The CEO wants to think through a design question with you.
QUESTION: {question}
Your job: Socratic refinement. Don't jump to an answer. Instead:
1. CLARIFY — Ask 2-3 sharpening questions to make sure you understand what the CEO really needs. What are the constraints? What matters most? What have they already considered?
2. EXPLORE — Once you understand, propose 2 options with clear trade-offs. Be opinionated. "I'd go with A because..." not "both have merit."
3. DETAIL — After the CEO picks a direction, flesh it out: what changes, what the structure looks like, what to watch out for.
Keep it conversational. Short responses. This is a dialogue, not a report.
CRITICAL OUTPUT FORMAT: JSON only. First character `{`, last `}`.
{
"agent": "{name}",
"clarifying_questions": ["question 1", "question 2", "question 3"],
"initial_instinct": "Your gut reaction to the question in 1-2 sentences"
}After the agent asks questions, present them to the CEO via AskUserQuestion or as text. Let the CEO answer. Then re-spawn the agent (or resume) with the answers to get the options.
Final output: Write a brief design note to .context/directives/{relevant-directive}/brainstorm.md capturing the decision. Keep it short — this is a lightweight brainstorm, not a design doc.
If the question turns out to be bigger than expected (agent's questions reveal cross-cutting complexity), upgrade to heavyweight. Tell the CEO: "This is bigger than it looked — upgrading to full brainstorm."
For strategic questions. Full C-suite, parallel research, synthesis, options.
The pattern: Diverge (independent perspectives) → Converge (synthesize options) → Decide (CEO picks) → Capture (design doc).
Read the CEO's question. If it's vague, clarify it with AskUserQuestion before proceeding.
Read context:
.context/vision.md — current north star.context/preferences.md — CEO preferences.context/goals/*/goal.json — current goal structure.context/lessons/scenarios.md — standing user scenarios (if relevant)Frame the question as a clear design challenge:
Show the framing to the CEO before spawning agents. This prevents wasted work on a misunderstood question.
Spawn 2-3 C-suite agents in parallel. Pick the most relevant agents for the question domain:
Always include the COO (they synthesize in Step 3). Pick 1-2 others based on the question.
Each agent receives:
.claude/agents/{name}.md.context/vision.md and .context/preferences.mdYou are {Name}, {Title}. The CEO is brainstorming a strategic question and wants your independent perspective.
QUESTION: {framed question}
CURRENT STATE: {how it works today}
CONSTRAINTS: {non-negotiables}
Your job:
1. RESEARCH first — use WebSearch if external patterns would help (how do other tools/frameworks handle this?). Use Read/Grep/Glob if you need to understand the current system.
2. THINK from your domain expertise — what matters most from your perspective?
3. PROPOSE — give 1-2 concrete options with trade-offs. Don't hedge. Have an opinion.
Structure your response:
{
"agent": "{name}",
"perspective": "Your 2-3 sentence framing of the problem from your domain",
"research": [
{
"finding": "What you found externally or internally",
"source": "URL or file path",
"relevance": "Why it matters to this question"
}
],
"proposals": [
{
"name": "short-name",
"summary": "One paragraph describing the approach",
"pros": ["advantage 1", "advantage 2"],
"cons": ["disadvantage 1", "disadvantage 2"],
"effort": "quick (hours) | medium (days) | large (weeks)",
"opinion": "Why you'd pick this one (or not)"
}
],
"non_negotiables": ["Things that MUST be true regardless of which option we pick"],
"watch_outs": ["Risks or gotchas the CEO should know about"]
}
CRITICAL: First character `{`, last character `}`. JSON only. Have a STRONG opinion — the CEO wants perspectives, not waffling.All agents: subagent_type: "general-purpose", model: "opus".
After all agents return, spawn the COO with a synthesis task.
The COO receives:
You are the COO. The team has brainstormed independently. Your job: synthesize their perspectives into 2-3 clear OPTIONS for the CEO to choose from.
AGENT PERSPECTIVES:
{all agent outputs}
SYNTHESIS RULES:
1. Find the OVERLAPS — where do agents agree? This is the foundation.
2. Find the CONFLICTS — where do they disagree? These are the real decision points.
3. Design 2-3 OPTIONS that represent genuinely different approaches (not just variations).
4. For each option, be honest about trade-offs. Don't create a strawman "bad option" to make one look good.
5. Include a "COO'S PICK" — your recommendation with reasoning.
6. Include the NON-NEGOTIABLES that all agents agreed on (these apply regardless of option).
{
"agreements": ["Things all agents agreed on — the foundation"],
"tensions": [
{
"topic": "What they disagree about",
"positions": {"sarah": "her view", "marcus": "his view"},
"why_it_matters": "What depends on this decision"
}
],
"options": [
{
"name": "Option A: descriptive name",
"summary": "2-3 sentence description",
"inspired_by": ["which agent roles/perspectives contributed"],
"pros": ["advantages"],
"cons": ["disadvantages"],
"effort": "quick | medium | large",
"best_when": "This option is best if the CEO values X over Y"
}
],
"non_negotiables": ["Must be true regardless of option chosen"],
"coo_pick": {
"option": "Option name",
"reasoning": "Why — in 2-3 sentences"
}
}
CRITICAL: First character `{`, last character `}`. JSON only.Present the synthesized options in a readable format:
# Brainstorm: {question title}
## The Team Agrees On
{non-negotiables — things that are true regardless of direction}
## The Key Tensions
{where agents disagreed — these are the real decisions}
## Options
### Option A: {name}
{summary}
**Pros:** {list}
**Cons:** {list}
**Effort:** {estimate}
**Best if:** {when to pick this}
### Option B: {name}
...
### Option C: {name} (if applicable)
...
## COO's Recommendation
{COO's pick and reasoning}
## Research Highlights
{Most interesting external findings from agents — URLs included}Ask the CEO using AskUserQuestion:
After the CEO decides:
Write a design doc to .context/directives/{relevant-directive}/brainstorm.md:
# {Question Title}
Date: {date}
Decision: {chosen option}
Participants: {agents involved}
## Context
{framed question + why it matters}
## Options Considered
{brief summary of each option}
## Decision
{which option + CEO's reasoning}
## Non-Negotiables
{agreed constraints}
## Next Steps
{what needs to happen to implement this — becomes /directive input}If the decision requires implementation, ask the CEO:
| Situation | Action |
|---|---|
| Agent output doesn't parse | Log error, continue with others. 2/3 perspectives is fine. |
| Agents all agree | Great — present the consensus as the recommendation. Still offer 2 options (the consensus + a contrarian alternative). |
| CEO wants to explore further | Spawn additional research on the specific area. Don't re-run the whole brainstorm. |
| Question is too broad | Break it into sub-questions. Brainstorm the most foundational one first. |
Normal path (auto-triggered): Strategic directives trigger a brainstorm automatically inside the /directive pipeline. The CEO never needs to invoke /brainstorm separately — the team detects when strategic thinking is needed and handles it.
CEO gives direction → /directive → triage as "strategic" → C-suite brainstorms → COO plans → executeStandalone path (CEO-invoked): The CEO can still invoke /brainstorm directly for questions that don't need a directive — strategy decisions, process design, framework choices, or "I want to think through X with the team" moments.
CEO invokes /brainstorm → triage → lightweight or heavyweight brainstorm → design docNot every directive needs a brainstorm (simple fixes don't). But strategic work — new data models, workflow changes, architectural shifts — benefits from the team exploring approaches before the COO plans execution.
© andrew-yangy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills/brainstorm of andrew-yangy/gru-ai.
Open the folder on GitHubat commit 8fba479
Brainstorm 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 |
|---|---|---|---|---|---|---|
| Brainstorm this skillandrew-yangy/gru-ai | 155 | — | ~3.2k | Automated safety check: Pass | MIT | |
| Brainstorminged3dai/ed3d-plugins | 250 | 1 repos | ~4.3k | Automated safety check: Pass | None | |
| Socratic BrainstormTheBeardedBearSAS/claude-craft | 107 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Gsd Exploreopen-gsd/gsd-core | 10k | 2 repos | ~176 | Automated safety check: Notes | MIT | |
| BrainstormingxenitV1/Antigravity-Workflows | 130 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Yao Bayesian Skillyaojingang/yao-open-skills | 1.3k | — | ~956 | Automated safety check: Pass | MIT |
ed3dai/ed3d-plugins
A skill your agent uses when creating or developing anything, before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning…
TheBeardedBearSAS/claude-craft
Brainstorming socratique AVANT de coder - clarifier le problème par questions ciblées plutôt que sauter à la solution.
open-gsd/gsd-core
Socratic ideation and idea routing — think through ideas before committing to plans
xenitV1/Antigravity-Workflows
Socratic questioning protocol + user communication. An agent skill from xenitV1/Antigravity-Workflows.
yaojingang/yao-open-skills
Convert uncertain real-world choices into an auditable Bayesian evidence-to-action report with priors, evidence grading, posterior update, action thresholds, sensitivity checks, multi-turn decision…
yaojingang/yao-open-skills
Route CEO-facing competition, negotiation, channel, pricing, platform, M&A, financing, competitor-response, alliance, and regulator problems through an applied game-theory framework router when…
andrew-yangy/gru-ai
Provides comprehensive code review guidance for React 19, Vue 3, Rust, TypeScript, Java, Python, and C/C++.
andrew-yangy/gru-ai
Full website SEO audit with parallel subagent delegation. An agent skill from andrew-yangy/gru-ai.
andrew-yangy/gru-ai
Internal codebase and operations health check — the CTO scans technical health, the COO checks operational health.
andrew-yangy/gru-ai
CEO dashboard with progressive disclosure — 3 tiers: headline (5 lines, default), summary (per-goal detail), deep (full weekly analysis).
andrew-yangy/gru-ai
Pipeline end-to-end smoke test -- creates a trivial directive, runs it through /directive, validates every pipeline step, and reports pass/fail with evidence.
andrew-yangy/gru-ai
Execute work through the directive pipeline — evaluate, plan, cast agents, build, review, and report.
Categories
Structured brainstorm — from quick Socratic refinement to full C-suite strategy sessions. Brainstorm is an agent skill from andrew-yangy/gru-ai. Structured brainstorm — from quick Socratic refinement to full C-suite strategy sessions.
Brainstorm fits situations like: tasks that involve Brainstorming; tasks that involve Tutoring and explanations.
Run `npx skills add andrew-yangy/gru-ai --skill brainstorm -a claude-code`. Or copy the skill folder (.claude/skills/brainstorm in andrew-yangy/gru-ai) into .claude/skills/brainstorm in your project. Claude Code loads it when a task matches its description.
Run `npx skills add andrew-yangy/gru-ai --skill brainstorm -a codex`. Or copy the skill folder (.claude/skills/brainstorm in andrew-yangy/gru-ai) into .agents/skills/brainstorm in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add andrew-yangy/gru-ai --skill brainstorm -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/brainstorm, .gemini/skills/brainstorm, .github/skills/brainstorm and .opencode/skills/brainstorm in your project.
SKILL.md names no scripts, command-line tools or credentials: Brainstorm is instructions for the agent only.
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.
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.
Brainstorm is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.2k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Brainstorm: Brainstorming (ed3dai/ed3d-plugins, 250 stars), Socratic Brainstorm (TheBeardedBearSAS/claude-craft, 107 stars), Gsd Explore (open-gsd/gsd-core, 10k stars) and Brainstorming (xenitV1/Antigravity-Workflows, 130 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
andrew-yangy (a GitHub user) maintains it in andrew-yangy/gru-ai, which has 155 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on March 11, 2026.
Source: andrew-yangy/gru-ai on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.