
bmad-brainstorm
Facilitates structured ideation sessions using proven brainstorming techniques (SCAMPER, SWOT, 5 Whys, Mind Mapping, Six Thinking Hats, Reverse Brainstorming, Starbursting, Brainwriting). Produces a brainstorming-report.md of organized ideas and actionable insights. Operates in three intents: Create (new session), Update (add techniques or deepen coverage), Validate (confirm insights align with project goals). Use when the user says: "brainstorm", "ideate", "generate ideas", "explore options", "SCAMPER", "SWOT analysis", "mind map", "Six Thinking Hats", "5 Whys", "creative session", "what if we", "let's explore", "think through possibilities", "find alternatives", or "problem-solve". This skill PLANS only — it never writes application code or runs tests.
- Installs
- 119
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/aj-geddes/claude-code-bmad-skills --skill bmad-brainstorm- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads bmad-brainstorm automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
BMAD Brainstorm
Structured ideation harness for the BMAD planning lifecycle. Produces a
brainstorming-report.md of organized ideas and insights ready to feed downstream
planning skills (product-brief, PRD, architecture).
Three Intents
Ask the user which intent applies — or infer from context:
| Intent | When to use |
|---|---|
| Create | New brainstorming session on a topic or problem |
| Update | Add techniques, deepen coverage, or incorporate new constraints |
| Validate | Confirm generated insights align with project goals or decision-log |
Technique Menu
| Technique | Best For | Approx Time |
|---|---|---|
| 5 Whys | Root cause analysis | 10-15 min |
| SCAMPER | Feature ideation & creative variations | 20-30 min |
| Mind Mapping | Idea organization & hierarchy | 15-20 min |
| Reverse Brainstorming | Risk and failure-mode identification | 15-20 min |
| Six Thinking Hats | Multi-perspective evaluation | 30-45 min |
| Starbursting | Question exploration (Who/What/When/Where/Why/How) | 20-30 min |
| SWOT Analysis | Strategic positioning | 30-45 min |
| Brainwriting | Silent parallel idea generation | 15-20 min |
Technique Selection Guide
- Exploring a problem? → 5 Whys, then Starbursting
- Generating features or solutions? → SCAMPER, Mind Mapping
- Assessing risk or failure modes? → Reverse Brainstorming, Six Thinking Hats (Black Hat)
- Strategic planning or positioning? → SWOT, Six Thinking Hats (full cycle)
- Need parallel idea volume? → Brainwriting
Session Workflow
Use TodoWrite to track each step.
- Gather context — Ask: topic/problem, relevant constraints, which BMAD track is active
- Read project context — Load
bmad-output/project-context.mdandbmad-output/decision-log.mdif present - Select techniques — Choose 2-4 complementary techniques; confirm with user
- Execute sessions — Apply each technique systematically (diverge first, do not filter)
- Organize ideas — Categorize all generated ideas; label Impact (H/M/L) and Feasibility (H/M/L)
- Extract insights — Identify top 3-5 actionable insights across all techniques
- Identify risks — Capture risks surfaced during ideation
- Produce report — Fill
templates/brainstorm-session.template.md; save to output folder - Update decision-log — Record key decisions or directions confirmed during the session
- Recommend next steps — Which BMAD skill to engage next
Script Utilities
Generate SCAMPER prompts for a specific topic:
bash "${CLAUDE_PLUGIN_ROOT}/skills/bmad-brainstorm/scripts/scamper-prompts.sh" "your topic"
Generate a SWOT analysis scaffold:
bash "${CLAUDE_PLUGIN_ROOT}/skills/bmad-brainstorm/scripts/swot-template.sh" "your subject" > bmad-output/swot-draft.md
Output Artifacts
All artifacts go under the user-configured output folder (default bmad-output/).
| File | Description |
|---|---|
bmad-output/brainstorming-report.md | Primary output — organized ideas + insights |
bmad-output/decision-log.md | Append key decisions made during session |
bmad-output/swot-draft.md | Optional SWOT scaffold (from script) |
Use templates/brainstorm-session.template.md for the report structure.
Subagent Strategy
For sessions covering multiple techniques in parallel, fan out one agent per technique.
Pattern: Fan-Out Ideation
Agents: 2-6 parallel (one per selected technique)
| Agent | Task | Output |
|---|---|---|
| Agent 1 | Apply SCAMPER to generate feature variations | bmad-output/brainstorm-scamper.md |
| Agent 2 | Build Mind Map to organize ideas hierarchically | bmad-output/brainstorm-mindmap.md |
| Agent 3 | Reverse Brainstorming — identify failure modes | bmad-output/brainstorm-risks.md |
| Agent 4 | Six Thinking Hats — multi-perspective analysis | bmad-output/brainstorm-hats.md |
| Agent 5 | Starbursting — Who/What/When/Where/Why/How | bmad-output/brainstorm-questions.md |
| Agent 6 | SWOT Analysis — strategic positioning | bmad-output/brainstorm-swot.md |
Coordination:
- Write brainstorming objective to
bmad-output/brainstorm-objective.md - Select 2-6 techniques; launch one agent per technique with context path
- Each agent generates 10-20 ideas/insights using its assigned technique
- Main context synthesizes all outputs into
bmad-output/brainstorming-report.md - Extract top 3-5 actionable insights; append decisions to
bmad-output/decision-log.md
Example subagent prompt:
Task: Apply SCAMPER technique
Context: Read bmad-output/brainstorm-objective.md for topic and constraints
Output: Write 15-20 creative variations to bmad-output/brainstorm-scamper.md
Apply each SCAMPER letter systematically. Generate 2-4 ideas per letter.
For each idea: one-sentence description, potential value, innovation level
(incremental / breakthrough). Conclude with your top 3 most promising ideas.
Do not implement anything — ideation output only.
BMAD Fidelity Notes
- This skill feeds Phase 1 (Analysis) and Phase 2 (Planning). Insights flow into the product-brief and PRD skills.
- Insights that become commitments must be logged in
bmad-output/decision-log.md. - This skill does not produce stories. It produces raw insight material that upstream skills (product-manager, system-architect) refine into epics and stories.
- Scale-adaptive tracks apply: Quick Flow sessions may use 1-2 techniques; Enterprise sessions should apply 4-6 for comprehensive coverage.
Guiding Principles
- Diverge before converging — generate volume first; filter later
- Structured over freeform — every technique has a defined process; follow it
- Document everything — capture all ideas; even "bad" ones can spark breakthroughs
- Quantify insights — numbers make insights actionable (market size, feature counts)
- Cross-pollinate — consider how other industries or domains solve the same problem
- No implementation — this skill plans; it never writes code or runs tests
Part of the BMAD Planning & Orchestrator plugin — a Claude Code harness for the BMAD Method by the BMAD Code Organization (https://github.com/bmad-code-org/BMAD-METHOD). Implements the spirit of
bmad-brainstorming. All methodology credit belongs to the BMAD Code Organization.
FAQ
What does the bmad-brainstorm skill do?
Facilitates structured ideation sessions using proven brainstorming techniques (SCAMPER, SWOT, 5 Whys, Mind Mapping, Six Thinking Hats, Reverse Brainstorming, Starbursting, Brainwriting). Produces a brainstorming-report.md of organized ideas and actionable insights. Operates in three intents: Create (new session), Update (add techniques or deepen coverage), Validate (confirm insights align with project goals). Use when the user says: "brainstorm", "ideate", "generate ideas", "explore options", "SCAMPER", "SWOT analysis", "mind map", "Six Thinking Hats", "5 Whys", "creative session", "what if we", "let's explore", "think through possibilities", "find alternatives", or "problem-solve". This skill PLANS only — it never writes application code or runs tests.
How do I install bmad-brainstorm?
Run npx skills add https://github.com/aj-geddes/claude-code-bmad-skills --skill bmad-brainstorm in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/bmad-brainstorm/ (personal) or .claude/skills/bmad-brainstorm/ (project).
Which AI agents can use bmad-brainstorm?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is bmad-brainstorm safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains bmad-brainstorm?
It is published by aj-geddes in aj-geddes/claude-code-bmad-skills. It has 119 recorded installs.
More from aj-geddes/claude-code-bmad-skills
business-analyst
aj-geddes/claude-code-bmad-skills
Product discovery and requirements analysis specialist. Conducts stakeholder interviews, market research, problem discovery, and creates product briefs. Use for product brief, brainstorm, research, discovery, requirements gathering, problem analysis, user needs, competitive analysis, and setting foundation before product planning. Hands off to product manager when analysis complete.
product-manager
aj-geddes/claude-code-bmad-skills
Product requirements and planning specialist. Creates PRDs and tech specs with functional/non-functional requirements, prioritizes features using MoSCoW/RICE frameworks, breaks down epics into user stories, and ensures requirements are testable and traceable. Use for PRD creation, requirements definition, feature prioritization, tech specs, epics, user stories, and acceptance criteria.
system-architect
aj-geddes/claude-code-bmad-skills
Designs system architecture, selects tech stacks, defines components and interfaces, addresses non-functional requirements. Trigger words - architecture, system design, tech stack, components, scalability, security, API design, data model, NFR, patterns, microservices, monolith
ux-designer
aj-geddes/claude-code-bmad-skills
Designs user experiences, creates wireframes, defines user flows, ensures accessibility. Trigger keywords - UX design, wireframe, user flow, accessibility, WCAG, mobile-first, responsive, UI design, user journey, interface design, user experience, design system, component design, interaction design
creative-intelligence
aj-geddes/claude-code-bmad-skills
Facilitates structured brainstorming sessions, conducts comprehensive research, and generates creative solutions using proven frameworks. Trigger keywords - brainstorm, ideate, research, SCAMPER, SWOT, mind map, creative, explore ideas, market research, competitive analysis, innovation, problem solving, feature generation
scrum master
aj-geddes/claude-code-bmad-skills
Sprint planning and agile workflow specialist. Breaks epics into user stories, estimates complexity using story points, plans sprint iterations, and tracks velocity. Trigger keywords - sprint planning, user story, story points, velocity, backlog, sprint, epic breakdown, estimation, burndown, agile planning.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.