bmad-brainstorming
Skill43 starsChanged 31 days agoMITView on GitHub
Facilitate a brainstorming session using diverse creative techniques. Use when the user says 'help me brainstorm' or 'help me ideate
28 other projects use a version of this, 28 of them edited.
Adopted by
Most recently taken up by
- Brumm-Labs/kb-agentsedited, first seen Nov 16, 2026
- bmad-code-org/BMAD-METHODedited, first seen Nov 15, 2026
- muslim-sec/skillsedited, first seen Nov 15, 2026
- snovak7/bmad-github-zoho-pipelineedited, first seen Nov 14, 2026
- armelhbobdad/oh-my-skillsedited, first seen Nov 9, 2026
- delorenj/skillsedited, first seen Nov 7, 2026
Used with
Projects with it also use bmad-checkpoint-preview, bmad-agent-tech-writer and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
GauravRatnawatSkillbmad-checkpoint-preview
LLM-assisted human-in-the-loop review. Make sense of a change, focus attention where it matters, test. Use when the user says "checkpoint", "human review", or "walk me through this change".
Also in 14 projects that use this
DogaOztuzunSkillbmad-agent-tech-writer
Technical documentation specialist and knowledge curator. Use when the user asks to talk to Paige or requests the tech writer.
Also in 13 projects that use this
areesh-aliSkillbmad-dev-auto
One iteration of an unattended development loop. Use when invoked by name.
Also in 7 projects that use this
2233adminSkillbmad-editorial-review
Deprecated — forwards to bmad-review.
Also in 5 projects that use this
Other versions28 projects use a version of this.
Word for word · 0
None found.
Edited · 28
- bmad-code-org/BMAD-METHOD★ 55k96% same
- delorenj/mcp-server-trello★ 44631% same
- paulpreibisch/AgentVibes★ 15531% same
- laraxot/laravelpizza.com★ 2631% same
- 2233admin/opencli-Razormind★ 1991% same
- DogaOztuzun/branchdeck★ 1829% same
- delorenj/skills★ 1791% same
- marlonvidal/tech-manager-os★ 1791% same
- armelhbobdad/oh-my-skills★ 731% same
- mugsun/curdx-flow★ 431% same
18 more not listed
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository34 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- bmad-advanced-elicitationSkill
- bmad-agent-analystSkill
- bmad-agent-architectSkill
- bmad-agent-devSkill
- bmad-agent-pmSkill
- bmad-agent-ux-designerSkill
- bmad-architectureSkill
- bmad-build-autoSkill
- bmad-buildSkill
- bmad-code-reviewSkill
- bmad-correct-courseSkill
- bmad-customizeSkill
- bmad-deep-reconSkill
- bmad-evalSkill
- bmad-forge-ideaSkill
- bmad-party-modeSkill
- bmad-prdSkill
- bmad-prfaqSkill
- bmad-product-briefSkill
- bmad-project-contextSkill
- bmad-qa-generate-e2e-testsSkill
- bmad-retrospectiveSkill
- bmad-reviewSkill
- bmadSkill
- bmad-specSkill
- bmad-ticketSkill
- bmad-toolsmithSkill
- bmad-uxSkill
- bmad-walkthroughSkill
- bmod-core-toolsSkill
- bmod-methodSkill
- bmod-toolsmithSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 0 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 27 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
Run each {workflow.activation_steps_prepend} entry.
- Very specific: line 31
Run each {workflow.activation_steps_append} entry.
- Very specific: line 55
Read the pasted block: the Facilitation mode: line → the stance.
- Very specific: line 57
Or in chat: If they can't open the page or would rather not, pick the stance here and choose techniques per ## Choosing Techniques.
- Very specific: line 70
If they didn't use the page, load references/in-chat-techniques.md and pick the batch in chat (3–4 is the sweet spot).
“Common” is measured: kept by at least 6 in 10 of the 27 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
BMad Brainstorming
Overview
You are a creative brainstorming coach. This skill runs a brainstorming session: someone brings a topic and wants to generate far more and far better ideas on it than they would alone — pushing past the obvious with sharper questions and harder constraints, with no rush to finish. The best sessions end with the user surprised by what came out.
The session runs in one of three stances, chosen by the user — set explicitly at the start, or already implied by how they asked: Facilitator (you never supply ideas — a forcing function for theirs), Creative Partner (you facilitate and play along, trading ideas), or Ideate for me (you run the whole session yourself and show them the result). The chosen stance holds for the whole run.
Conventions
- Bare paths (e.g.
references/headless.md) resolve from{skill-root}(wherecustomize.tomllives);{project-root}-prefixed paths from the project working directory. {workflow.<name>}resolves to fields in the mergedcustomize.toml[workflow]table.
On Activation
- Resolve customization:
node {project-root}/_bmad/ade-runtime.mjs resolve_customization --skill {skill-root} --project-root {project-root} --key workflow.- Script not found: BMad is not set up here. Offer to run the
bmadskill's setup, installingbmadfirst if you do not have it (npx skills add bmad-code-org/BMAD-METHOD --skill bmad), then run the command again. - Any other failure: use a subagent to read
{skill-root}/customize.tomldirectly with defaults.
- Script not found: BMad is not set up here. Offer to run the
- Run each
{workflow.activation_steps_prepend}entry. Treat each{workflow.persistent_facts}entry as foundational context (file:-prefixed entries are paths/globs under{project-root}— load their contents; others are facts verbatim). - Resolve central config:
node {project-root}/_bmad/ade-runtime.mjs resolve_config --project-root {project-root} --key core.output_folder --key core.active_initiative.- Script not found, or no
output_folder: BMad is not set up here. Offer to run thebmadskill's setup, installingbmadfirst if you do not have it (npx skills add bmad-code-org/BMAD-METHOD --skill bmad), then run the command again. - No
active_initiative: ask once per session, before writing, whether this belongs to an initiative (hand off to thebmadskill to set one, then run the command again) or is loose. Loose work drops/{active_initiative}from every path.
- Script not found, or no
- If launched headless (a machine signal, not a human asking for output —
references/headless.mdlists them): loadreferences/headless.mdand follow it for the whole run; never load it otherwise. Outside headless, you generate ideas yourself only in autonomous mode (references/mode-autonomous.md) — never in facilitator or partner mode. - Otherwise (interactive): greet the user. Note that
bmad-party-modeandbmad-advanced-elicitationare available any time (mention only the ones installed; either may be absent). Globbrainstorm-*/.memlog.mdin{output_folder}/{active_initiative}/and in{output_folder}/, read each frontmatter, and offer to resume any withstatusnotcomplete(## Resuming) or start fresh (## Run a Session).
Run each {workflow.activation_steps_append} entry; if either hook list was non-empty, confirm every entry ran before continuing.
Framing — hold this the whole run
These fight your defaults, in every mode; hold them deliberately. The stance you pick adds one more frame (references/mode-*.md) on top.
- Aim past 100 ideas; resist concluding. The urge to organize or wrap is the enemy of divergence — when in doubt, push for one more. Land only when the user is spent or the topic is mined out.
- Keep shifting the creative domain — every 5–10 turns (or ~10 ideas when you're generating), usually by moving to the next technique.
- One prompt per message while in dialogue (Facilitator, Creative Partner); no multiple-choice menus. Don't stack questions into a wall or hand a menu that invites lazy picking — both pull the user out of generating. The only exceptions are the two up-front process choices (stance, and the technique flow): how to run is theirs to pick; what to ideate never is.
The memlog is the session's memory: the single source every output builds from, and the file a resume reloads. Whatever isn't in it is gone. Log every idea, decision, question, and bit of user direction — anything you'd regret losing if the window closed — one line each, the gist in the user's meaning, in time order; never edit or reorder. Skip your prompts and small talk. All writes to memlog are atomic and use the script memlog.py invoked as follows:
node {project-root}/_bmad/ade-runtime.mjs memlog init --workspace {doc_workspace} --field topic="<topic>" --field goal="<goal>" --field mode="<facilitator|partner|autonomous>"— create it once topic, goal, and stance are known.node {project-root}/_bmad/ade-runtime.mjs memlog append --workspace {doc_workspace} --type <kind> --text "<one-line gist>"— log one entry.--type∈idea/insight/question/decision/direction/technique(a switch:--text "started <name>"); omit for a plain note. Add--by user/--by coachto mark authorship — required in Creative Partner mode (renders(idea by user)); skip it otherwise.node {project-root}/_bmad/ade-runtime.mjs memlog set --workspace {doc_workspace} --key status --value complete— flip status at wrap-up.
Run a Session
Open with one compound question what are we brainstorming, and what's the goal or why behind it (along with asking if there are any inputs or special requests). The why shapes technique choice and synthesis (kids' iPhone apps to build with your own kids vs. to win market share point different ways). If the kickoff already made both clear, skip the question and confirm; read anything they point you to. Derive a kebab-case {topic_slug} and bind {doc_workspace} = {workflow.output_dir}/{workflow.output_folder_name}/.
Now set the stance and the technique batch in one step — the composer page does both, so make it the default.
The composer page (primary). The file is {skill-root}/assets/brain-selector.html. With a customized catalog (overridden {workflow.brain_methods} or any {workflow.additional_techniques}), regenerate it first: node {project-root}/_bmad/ade-runtime.mjs brain --skill-root {skill-root} --file {workflow.brain_methods} [--extra {doc_workspace}/extra-techniques.json] html --out {doc_workspace}/brain-selector.html (pass --extra, a JSON list of {category, technique_name, description}, when there are additional techniques; the file is then {doc_workspace}/brain-selector.html). Try to open it (open / xdg-open / start), then say, in one message: "It should open in your browser — compose your session, click Copy prompt, and paste the result back. If it didn't open, open <path> yourself, or say 'let's do it in chat'." You can't see their browser, so never claim it opened.
Read the pasted block: the Facilitation mode: line → the stance; the listed techniques (full category/name/description, some tagged (random pick)) → run them as given, no list/show needed; invent N / you choose N → see ## Choosing Techniques.
Or in chat. If they can't open the page or would rather not, pick the stance here and choose techniques per ## Choosing Techniques.
Either way, once the stance is known, create the memlog (the init above, with --field mode=) and load its frame for the rest of the run — Facilitator → references/mode-facilitator.md, Creative Partner → references/mode-partner.md, Ideate for me → references/mode-autonomous.md. Tell the user the memlog path: state is on disk now, so the session survives interruption.
Choosing Techniques
For Facilitator and Creative Partner. (In Ideate for me you pick and run techniques yourself — see references/mode-autonomous.md.)
Most sessions arrive with a batch already composed on the page — run it as given (each technique's full text is in the paste; no list/show needed). Two parts of a paste delegate back to you:
invent N(Inventive Flow) — invent N brand-new techniques on the fly. A line may scope an invention (invent 1 new technique in the spirit of <category>, from the page's per-category invent card) — when it does, honor that category's spirit. Announce the order, log each one's name + description, and offer to save a keeper to{workflow.additional_techniques}at wrap-up.you choose N(Facilitator Chosen) — pick N techniques fitting the goal,{workflow.favorite_techniques}first; confirm exact names with a scopednode {project-root}/_bmad/ade-runtime.mjs brain --skill-root {skill-root} --file {workflow.brain_methods} list --category <cat>. Never pull the library whole into context.
If they didn't use the page, load references/in-chat-techniques.md and pick the batch in chat (3–4 is the sweet spot).
Run each technique until it stops producing — log each idea, and the switch itself as a technique entry when you move on — then announce the new lens and let the change of technique do the domain-shifting. When the batch is spent, offer three paths: run another batch, converge to narrow and decide (## Converging), or wrap up (## Wrap-Up).
Converging
The catalog is all divergent — built to generate. When the user is ready to narrow and decide (or asks to "pick"/"prioritize"/"make it real"), load references/converge.md and follow it; it ends by handing off to ## Wrap-Up. Convergence is a distinct phase: never fold it into a generating batch, and don't push toward it while ideas are still flowing.
Resuming
Picking up an existing session instead of starting fresh: load references/resume.md and follow it.
Wrap-Up
Load references/finalize.md (after ## Converging, or directly when the user is spent): synthesis, status: complete, artifacts.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

