brainstorming

Name: brainstorming
Availability: InStock
Author: whmathews15

Clarify ambiguous feature requests through one-at-a-time questioning and option comparison.

1|Updated Jun 28, 2026

Search Tags:#brainstorming #ideation #requirements #clarification #tradeoffs #product-discovery #feature-planning

Ready to run

npx skills add https://github.com/whmathews15/DEX-Personal-Operating-System --skill brainstorming-whmathews15

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/whmathews15/DEX-Personal-Operating-System/tree/main/.claude/plugins/compound-engineering/skills/brainstorming
Command: npx skills add https://github.com/whmathews15/DEX-Personal-Operating-System --skill brainstorming-whmathews15

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn vague or conflicting feature ideas into a clear, well-scoped direction before planning or implementation begins. It is useful when requirements are unclear, multiple solutions are possible, or the user has not yet defined success criteria.

Core Features & Use Cases

Requirement discovery: Ask focused questions to uncover the purpose, audience, constraints, and desired outcomes of an idea.
Approach exploration: Compare 2-3 viable options with clear pros, cons, and best-fit scenarios.
Design capture: Summarize the chosen direction in a concise structure that is ready for handoff into planning.
Use case: A product manager says “make onboarding better,” and this Skill helps narrow that into a specific problem, audience, and solution direction.

Quick Start

Tell the brainstorming skill your rough idea, and let it ask one question at a time until the problem, users, constraints, and success criteria are clear.

Frequently Asked Questions about brainstorming

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

FAQPage Schema

How do I clarify ambiguous feature requests before development begins?▼

Clarify ambiguous feature requests by asking focused questions to uncover the purpose, audience, constraints, and desired outcomes. This requirement discovery process narrows vague ideas into a specific problem and solution direction through one-at-a-time questioning.

What's the best way to explore trade-offs when multiple valid approaches exist?▼

Explore trade-offs by comparing 2-3 viable approaches with clear pros, cons, and best-fit scenarios. This approach exploration validates explicit assumptions and helps select a well-scoped direction when multiple solutions are possible.

How do I turn a rough product idea into a structured handoff for planning?▼

Turn a rough product idea into a structured handoff by capturing the chosen direction in a concise design summary. This design capture ensures the problem, users, constraints, and success criteria are clear and ready for planning.

Can I use this for requirement discovery when scope is not yet defined?▼

Yes, requirement discovery is designed exactly for undefined scope. It supports early-stage product ideas by asking one question at a time until the problem, users, constraints, and success criteria become clear.

How does requirement discovery work for early-stage product ideas?▼

Requirement discovery works by asking one question at a time to validate explicit assumptions about the idea's purpose and audience. This iterative questioning continues until the problem, users, constraints, and success criteria are fully clear.

When should I not use structured brainstorming for feature planning?▼

Avoid structured brainstorming when requirements are already clear, success criteria are defined, and a single valid approach exists. This process is specifically for unclear requirements, multiple possible solutions, or undefined scope.