Skip to content
FunCoding

Search

Search docs, Skills and MCP

nw-brainstorming

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

前端开发617nWave/skills/nw-brainstorming/SKILL.md

Install

Send this to Claude Code, Codex or Cursor. The agent checks the Skill for safety first and installs it only after you confirm.

读取 https://funcoding.ai/skills/nwave-ai/nwave/nw-brainstorming/install.md ,按里面的步骤帮我安装这个 Skill。

SKILL.md

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.

LetterLensQuestionWhat it produces
SSubstituteWhat if the core mechanism were replaced entirely?Alternative technology/approach
CCombineWhat if this job were merged with an adjacent job?Integrated solution
AAdaptWhat works well in a different domain? Could we borrow it?Cross-domain transfer
MModify/MagnifyWhat if the most important dimension were amplified?Focused excellence
PPut to other useWho else has this job? Could the solution serve them too?Market extension
EEliminateWhat if we removed the most complex part?Radical simplification
RReverseWhat 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:

  1. List all generated options (7+ from SCAMPER + supplements)
  2. Remove exact duplicates only — not similar ones, exact
  3. Group options that are genuine variations of the same approach → keep the strongest representative
  4. 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-patternWhy it failsCorrection
Generating one good idea and elaborating itConfirmation bias — narrows too earlyApply all SCAMPER letters before stopping
"Improved version of the existing approach"Not divergent — variation, not optionApply E (Eliminate) or R (Reverse)
Filtering during generation ("that won't work")Destroys divergent thinkingGenerate everything, filter in taste phase
Options that share the same core mechanismFalse diversityApply diversity test before curating
Skipping HMW framingSolution space collapses prematurelyHMW must precede any generation

DIVERGE Output for Brainstorming Phase

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

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

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

Similar Skills

frontend-design
anthropics/skills180k

frontend-design

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

Frontend

web-artifacts-builder
anthropics/skills180k

web-artifacts-builder

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.

Frontend

api-and-interface-design
addyosmani/agent-skills103k

api-and-interface-design

Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.

Frontend

frontend-ui-engineering
addyosmani/agent-skills103k

frontend-ui-engineering

Builds production-quality, accessible, responsive user-facing UIs. Use when building or modifying interfaces and pages, creating components, implementing layouts, meeting WCAG accessibility requirements, managing state, or when the output needs to look and feel production-quality rather than AI-generated.

Frontend

performance-optimization
addyosmani/agent-skills103k

performance-optimization

Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.

Frontend

html-ppt-graphify-dark-graph
nexu-io/open-design100k

html-ppt-graphify-dark-graph

OpenDesign's feature business case for the plugin marketplace: the user pain, options, tradeoffs, and the measure of success. Built as a decision-grade product management deck for PM, eng, design, leadership.

Frontend