brainstorming

Facilitate structured brainstorming to clarify vague requirements before planning.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/CuriousCrow123/godot-compound --skill brainstorming-curiouscrow123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/CuriousCrow123/godot-compound/tree/main/skills/brainstorming
Command: npx skills add https://github.com/CuriousCrow123/godot-compound --skill brainstorming-curiouscrow123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming helps teams clarify user intent, explore approaches, and define scope before committing to a plan.

Core Features & Use Cases

  • Phase-based questioning to surface assumptions and identify gaps
  • Guided exploration of approaches before design or implementation
  • Guardrails and handoff to planning with clear criteria

Quick Start

Begin by stating the user's goal, ask one clarifying question, then propose two practical approaches.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I clarify vague requirements before starting project planning?

Structured brainstorming clarifies vague requirements before project planning by using phase-based questioning to surface assumptions and identify gaps. It guides teams through exploring multiple interpretations to ensure design decisions are resolved before implementation begins.

What is the best way to explore design decisions when multiple interpretations exist?

The best way to explore design decisions with multiple interpretations is a guided brainstorming workflow with defined phases. By questioning intent and proposing practical approaches, teams evaluate options systematically and establish clear criteria before committing to an implementation path.

How do I start a brainstorming session to define project scope?

Start defining project scope by stating the user's goal, asking one clarifying question, then proposing two practical approaches. This repeatable brainstorming workflow provides guardrails and a structured handoff to planning with actionable criteria.

When should I use a structured brainstorming workflow instead of jumping straight to planning?

Use a structured brainstorming workflow instead of jumping straight to planning when requirements are unclear, multiple interpretations exist, or design decisions must be explored. It prevents scope ambiguity by resolving user intent and defining boundaries before implementation.

Does this brainstorming approach work for resolving unclear user intent in product management?

Yes, this brainstorming approach works for resolving unclear user intent in product management by applying design-thinking principles. It facilitates structured discussion and questioning to explore approaches, ensuring teams define scope and clarify goals before committing to a plan.