mcpbeat Sign in

Nw Brainstorming Agent Skill

Structured divergent thinking techniques — HMW framing, SCAMPER, Crazy 8s mechanics, and option diversity guarantees. Enforces strict separation of generation and evaluation phases.

1k tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
588
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/nWave-ai/nWave --skill nw-brainstorming

The instruction itself

9 sections, as written by the author

Structured Brainstorming

The Separation Principle — Foundational Rule

Generation and evaluation CANNOT happen simultaneously. Osborn (1953): "You cannot get hot and cold water from the same faucet at the same time — you only get tepid water."

Consequence for the agent: All options must be generated before any option is scored. Never filter or rank during generation. Self-censorship during generation degrades both the quality of ideas and the quality of evaluation.


Phase 1: HMW Framing — Set Up the Ideation Space

Before generating any options, reframe the problem as a "How Might We" question.

Rules for valid HMW questions:

  • No embedded solutions: "How might we make onboarding faster?" ✓ vs "How might we add tooltips?" ✗
  • Outcome-oriented, not feature-oriented
  • Broad enough for genuinely different approaches
  • Positive framing (not "How might we avoid X?")

Example transformation:

  • Feature request: "Add a dashboard to show workflow status"
  • Bad HMW: "How might we build a better dashboard?"
  • Good HMW: "How might we give teams confidence that their workflow is progressing correctly?"

The good HMW opens the solution space: the answer isn't necessarily a dashboard.


Phase 2: SCAMPER — 7 Structurally Different Lenses

Apply each SCAMPER lens to the validated job to generate one option per letter. This guarantees structural diversity — each letter produces a categorically different type of option.

| Letter | Lens | Question | What it produces |

|--------|------|----------|-----------------|

| S | Substitute | What if the core mechanism were replaced entirely? | Alternative technology/approach |

| C | Combine | What if this job were merged with an adjacent job? | Integrated solution |

| A | Adapt | What works well in a different domain? Could we borrow it? | Cross-domain transfer |

| M | Modify/Magnify | What if the most important dimension were amplified? | Focused excellence |

| P | Put to other use | Who else has this job? Could the solution serve them too? | Market extension |

| E | Eliminate | What if we removed the most complex part? | Radical simplification |

| R | Reverse | What if the workflow ran backwards? User and system switched roles? | Inversion |

Required output: At minimum, one option per SCAMPER letter. Name each option clearly. Do not evaluate during generation.


Phase 3: Crazy 8s Supplement — Volume and Self-Censorship Removal

After SCAMPER, generate 2-4 additional options by imagining you have only 1 minute per idea. The time pressure mechanic prevents evaluation creep.

Constraint: Each additional option must differ structurally from all SCAMPER options. Not a variation — a different type of approach.


Phase 4: Option Curation — Converge to 6

Before handing off to taste evaluation:

  • List all generated options (7+ from SCAMPER + supplements)
  • Remove exact duplicates only — not similar ones, exact
  • Group options that are genuine variations of the same approach → keep the strongest representative
  • Target: 6 options for evaluation (evidence-backed sweet spot: enough diversity, evaluable without overload)

Diversity test — each of the 6 options should answer yes to:

  • Different mechanism? (not just variation in degree)
  • Different assumption about user behavior?
  • Different cost/effort profile?

If two options share all three, they are variations — merge them.


Option Format

Each option in options-raw.md must follow:

### Option N: [Name]

**Core idea**: One sentence — what would a user actually experience?
**Key mechanism**: What makes this work?
**Key assumption**: What must be true for this to succeed?
**SCAMPER origin**: Which lens generated this? (or "Crazy 8s supplement")
**Closest competitor**: What existing product does this most?

Anti-Patterns to Avoid

| Anti-pattern | Why it fails | Correction |

|-------------|-------------|-----------|

| Generating one good idea and elaborating it | Confirmation bias — narrows too early | Apply all SCAMPER letters before stopping |

| "Improved version of the existing approach" | Not divergent — variation, not option | Apply E (Eliminate) or R (Reverse) |

| Filtering during generation ("that won't work") | Destroys divergent thinking | Generate everything, filter in taste phase |

| Options that share the same core mechanism | False diversity | Apply diversity test before curating |

| Skipping HMW framing | Solution space collapses prematurely | HMW must precede any generation |


DIVERGE Output for Brainstorming Phase

Produce docs/feature/{feature-id}/diverge/options-raw.md with:

  • HMW question — the validated framing
  • SCAMPER options — one per letter, named and described
  • Crazy 8s supplements — 2-4 additional structurally distinct options
  • Curated 6 — with diversity test results
  • Eliminated options — brief note on why merged/removed

Gate: 6 curated options, each passing the 3-point diversity test, before taste evaluation begins.

Other skills for the same job

different authors, same section of the catalogue
Doc Coauthoring
by anthropics
vendor ×10

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

4k tokens
File Organizer
by frostant
×10

Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.

3k tokens
Domain Name Brainstormer
by frostant
×8

Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.

1k tokens
Brainstorming
by ZhanlinCui
×4

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

626 tokens
Planning With Files
by ZhanlinCui
×3

Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.

9k tokens scripts
Scientific Brainstorming
by christophacham
×3

Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.

5k tokens
GitHub Project Management
by ComeOnOliver
×3

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

14k tokens
Grill Me
by ComeOnOliver
×3

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

3k tokens

How to use it

Copy the folder

Take nwave-ai/nw-brainstorming from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.