/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
$ npx -y skills add aj-geddes/claude-code-bmad-skills --skill bmad-brainstorm --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/bmad-brainstorm
Context preview
The summary Claude sees to decide when to auto-load this skill.
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
SKILL.md
bmad-brainstorm.SKILL.mdname: bmad-brainstorm
description: |
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.
allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebSearch, WebFetch, TodoWrite
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.
1. **Gather context** — Ask: topic/problem, relevant constraints, which BMAD track is active 2. **Read project context** — Load `bmad-output/project-context.md` and `bmad-output/decision-log.md` if present 3. **Select techniques** — Choose 2-4 complementary techniques; confirm with user 4. **Execute sessions** — Apply each technique systematically (diverge first, do not filter) 5. **Organize ideas** — Categorize all generated ideas; label Impact (H/M/L) and Feasibility (H/M/L) 6. **Extract insights** — Identify top 3-5 actionable insights across all techniques 7. **Identify risks** — Capture risks surfaced during ideation 8. **Produce report** — Fill `templates/brainstorm-session.template.md`; save to output folder 9. **Update decision-log** — Record key decisions or directions confirmed during the session 10. **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.mdOutput 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:**
1. Write brainstorming objective to `bmad-output/brainstorm-objective.md` 2. Select 2-6 techniques; launch one agent per technique with context path 3. Each agent generates 10-20 ideas/insights using its assigned technique 4. Main context synthesizes all outputs into `bmad-output/brainstorming-report.md` 5. 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.
Read more
name: bmad-brainstorm description: | 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. allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebSearch, WebFetch, TodoWrite
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.
1. **Gather context** — Ask: topic/problem, relevant constraints, which BMAD track is active 2. **Read project context** — Load `bmad-output/project-context.md` and `bmad-output/decision-log.md` if present 3. **Select techniques** — Choose 2-4 complementary techniques; confirm with user 4. **Execute sessions** — Apply each technique systematically (diverge first, do not filter) 5. **Organize ideas** — Categorize all generated ideas; label Impact (H/M/L) and Feasibility (H/M/L) 6. **Extract insights** — Identify top 3-5 actionable insights across all techniques 7. **Identify risks** — Capture risks surfaced during ideation 8. **Produce report** — Fill `templates/brainstorm-session.template.md`; save to output folder 9. **Update decision-log** — Record key decisions or directions confirmed during the session 10. **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.mdOutput 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:**
1. Write brainstorming objective to `bmad-output/brainstorm-objective.md` 2. Select 2-6 techniques; launch one agent per technique with context path 3. Each agent generates 10-20 ideas/insights using its assigned technique 4. Main context synthesizes all outputs into `bmad-output/brainstorming-report.md` 5. 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.
This repository is a Claude Code plugin marketplace. It ships one plugin — BMAD Planning & Orchestrator — that harnesses the BMAD Method to plan, document, and orchestrate software work as conflict-free parallel workstreams, then hands implementation off to
Repo: aj-geddes/claude-code-bmad-skills
Other skills on claude-code-bmad-skills.
- /bmad-architecture
Solutioning skill (Winston, the Architect). Produces architecture.md with ADRs and systematic NFR coverage, mapping every FR/NFR from the PRD to a concrete design decision. ONE architecture forces all future parallel dev agents to share the same API style, data model, state
Open skill - /bmad-builder
Meta-skill for scaffolding and validating custom PLANNING/ORCHESTRATION skills within the BMAD Planning & Orchestrator plugin. Produces the full skill directory: SKILL.md, scripts, and templates — all pre-targeted at this plugin's path conventions. Includes a scope-violation
Open skill - /bmad-correct-course
CROSS-PHASE mid-stream scope correction. Re-enters planning when requirements, features, architecture, or constraints change after planning has started. Re-shards affected epics/stories, re-sequences sprint-status.yaml, appends rationale to decision-log.md. Routes to
Open skill - /bmad-document-project
BROWNFIELD planning input. Scans an existing codebase READ-ONLY and writes project-documentation.md — ground truth for stack, structure, key flows, conventions, and integration points — so downstream BMAD planning skills start from reality. Does NOT modify code; produces only
Open skill - /bmad-epics-and-stories
Solutioning flagship — shards a PRD + architecture into epics.md and individual {epic}.{story}.{slug}.story.md context objects, the LAST planning artifact before external dev handoff. Each story is a self-contained ~8K-token compiled context object: Dev Notes with SOURCE
Open skill - /bmad-handoff
Emits a dev-tool-agnostic handoff manifest from ready-for-dev stories so an external dev plugin or runner can pick up and execute the work. Use when the user says "generate a handoff", "create handoff manifest", "export stories for dev", "hand off to dev tool", "produce handoff
Open skill

