product-brainstorming

Facilitates structured product brainstorming sessions using ideation frameworks and assumption testing.

Updated Sep 15, 2026
One-click install
npx skills add https://github.com/Nadav011/nadavai-claude --skill product-brainstorming-nadav011
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-brainstorming
Source: https://github.com/Nadav011/nadavai-claude/tree/main/plugins/nadavai/skills/product-brainstorming
Command: npx skills add https://github.com/Nadav011/nadavai-claude --skill product-brainstorming-nadav011

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product managers often converge on solutions too early, anchor on the first idea, or brainstorm without structure, leading to weak specs built on untested assumptions. This Skill acts as a thinking partner that challenges assumptions, pushes divergent thinking, and helps PMs explore problem spaces before committing to a direction. ## Core Features & Use Cases - Four Brainstorming Modes: Problem exploration, solution ideation, assumption testing, and strategy exploration, adapting to where the PM is in their thinking. - Ideation Frameworks: How Might We, Jobs-to-be-Done, Opportunity Solution Trees, First Principles, SCAMPER, OODA Loop, and Reverse Brainstorming applied as thinking tools. - Structured Session Flow: A five-phase rhythm (frame, diverge, provoke, converge, capture) that opens up thinking before narrowing down. - Use Case: A PM believes users need a new dashboard feature. The skill probes who has the problem, what they do today, generates 5-7 alternative approaches, identifies the riskiest assumption, and suggests the cheapest way to test it before any spec is written. ## Quick Start Ask the assistant to brainstorm solutions for a product problem you are exploring, such as improving new user activation, and have it challenge your assumptions before converging.

Frequently Asked Questions about product-brainstorming

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I brainstorm product ideas with structure instead of random ideation?

Use a five-phase session structure: frame the problem and constraints, diverge to generate many ideas without judgment, provoke with challenging questions, converge on 2-3 directions, and capture assumptions and next steps. Frameworks like SCAMPER and How Might We systematically open new angles.

What frameworks help generate product solutions for a defined problem?

Jobs-to-be-Done reframes the problem from the user's motivation, How Might We turns pain points into actionable questions, and Opportunity Solution Trees map outcomes to opportunities, solutions, and experiments. First Principles and Reverse Brainstorming help when the team is stuck in incremental thinking.

How do I test assumptions before building a product feature?

List every assumption the idea depends on across user, problem, solution, business, feasibility, and adoption categories. Identify the riskiest assumption that would kill the idea if wrong, then design the cheapest possible test for it before investing in execution.

When should I stop brainstorming and do user research instead?

Stop brainstorming when the session keeps circling because no one knows the answer to a factual question about users or the market. Brainstorming generates hypotheses; questions about actual user behavior, frequency, and willingness to pay require research and data.

What are common product brainstorming mistakes to avoid?

Common anti-patterns include solutioning before framing the problem, copying competitors without understanding the underlying user need, anchoring on technical constraints during divergent thinking, and treating a single pre-decided idea as a brainstorm.