brainstorming

Guide structured brainstorming to define project scope and capture design decisions.

Updated Aug 23, 2026

Search Tags:#design #planning #decision making #brainstorming #requirements gathering #product discovery

Ready to run

npx skills add https://github.com/adamfeldman/compound-workflows --skill brainstorming-adamfeldman

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/adamfeldman/compound-workflows/tree/main/plugins/compound-workflows/skills/brainstorming
Command: npx skills add https://github.com/adamfeldman/compound-workflows --skill brainstorming-adamfeldman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps clarify project requirements, explore different solution approaches, and make informed design decisions before committing to implementation, preventing wasted effort on unclear or suboptimal solutions.

Core Features & Use Cases

Requirement Assessment: Determines if brainstorming is necessary based on the clarity of initial requirements.
Intent Exploration: Asks targeted questions to understand the user's core need, users, constraints, and success criteria.
Approach Comparison: Proposes and evaluates 2-3 distinct implementation strategies, outlining their pros, cons, and best-fit scenarios.
Design Documentation: Summarizes key decisions and rationale in a structured format.
Use Case: Before building a new user authentication flow, this Skill can help explore options like OAuth vs. traditional email/password, discuss security trade-offs, and document the chosen path.

Quick Start

Use the brainstorming skill to explore the requirements for a new user profile page.

Frequently Asked Questions about brainstorming

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

FAQPage Schema

How do I clarify project requirements before starting development?▼

To clarify project requirements, you need to assess initial intent, explore alternative solutions, and capture design decisions. This structured brainstorming process defines the project scope by answering the "WHAT" before proceeding to the "HOW" of implementation.

What is the best way to compare different design approaches for a new feature?▼

The best way to compare design approaches is to evaluate 2-3 distinct implementation strategies, outlining their pros, cons, and best-fit scenarios. This approach comparison helps you make informed design decisions and prevents wasted effort on suboptimal solutions.

When do I need to use a structured brainstorming process for product discovery?▼

You need a structured brainstorming process for product discovery when initial requirements lack clarity. It helps determine if brainstorming is necessary based on your current requirement assessment, ensuring you understand core needs, users, and constraints before building.

How do I document design decisions and rationale for a new authentication flow?▼

You document design decisions and rationale by summarizing key choices in a structured format after exploring options. For a new authentication flow, this involves discussing security trade-offs between approaches like OAuth and traditional email/password, then recording the chosen path.

Does requirements gathering work for exploring user profile page scope?▼

Requirements gathering works effectively for exploring user profile page scope by asking targeted questions to understand your core need, users, constraints, and success criteria. This intent exploration clarifies what needs to be built before committing to a specific implementation.

What are the limitations of brainstorming project scope without defining intent first?▼

Brainstorming project scope without defining intent first leads to wasted effort on unclear or suboptimal solutions. Without intent clarification, you risk committing to an implementation path that fails to address actual user needs or technical constraints.