plugins/nw/skills/nw-brainstorming/SKILL.md
Structured divergent thinking techniques — HMW framing, SCAMPER, Crazy 8s mechanics, and option diversity guarantees. Enforces strict separation of generation and evaluation phases.
npx skillsauth add nwave-ai/nwave nw-brainstormingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
Before generating any options, reframe the problem as a "How Might We" question.
Rules for valid HMW questions:
Example transformation:
The good HMW opens the solution space: the answer isn't necessarily a dashboard.
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.
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.
Before handing off to taste evaluation:
Diversity test — each of the 6 options should answer yes to:
If two options share all three, they are variations — merge them.
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-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 |
Produce docs/feature/{feature-id}/diverge/options-raw.md with:
Gate: 6 curated options, each passing the 3-point diversity test, before taste evaluation begins.
testing
Acceptance test creation methodology for the DISTILL wave. Domain knowledge for the acceptance designer agent: port-to-port principle, prior wave reading, wave-decision reconciliation, graceful degradation, and document back-propagation.
testing
Methodology for minimizing test count while maximizing behavioral coverage - behavior definition, anti-pattern catalog, consolidation patterns, stopping criterion, coverage-preserving validation
testing
Methodology for minimizing test count while maximizing behavioral coverage - behavior definition, anti-pattern catalog, consolidation patterns, stopping criterion, coverage-preserving validation
development
Design mandates for acceptance tests - hexagonal boundary, business language abstraction, user journey completeness, pure function extraction, 3 Pillars (domain language / chained narrative / production composition), and the layered ATD discipline (Universe-bound assertion, layer-dependent PBT mode, two-tier acceptance, example-based sad paths)