brainstorming

Guide teams from idea to design through structured brainstorming and collaborative dialogue.

4|Updated Feb 26, 2026

Search Tags:#design #planning #brainstorming #collaboration #requirements #product #design-doc

Ready to run

npx skills add https://github.com/oabdelmaksoud/Openclaw-skills-Compilations --skill brainstorming-oabdelmaksoud

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/oabdelmaksoud/Openclaw-skills-Compilations/tree/main/brainstorming
Command: npx skills add https://github.com/oabdelmaksoud/Openclaw-skills-Compilations --skill brainstorming-oabdelmaksoud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams turn vague ideas into concrete design plans by guiding structured brainstorming and collaborative discussion to clarify goals, constraints, and success criteria before any implementation.

Core Features & Use Cases

Explore project context by reviewing repository files, docs, and recent activity to establish a baseline.
Ask clarifying questions one at a time to refine purpose, constraints, and acceptance criteria.
Propose 2-3 approaches with trade-offs and a recommended option.
Present a design outline and obtain user approval before proceeding to implementation planning.
Write a design doc and transition to formal planning workflows.

Quick Start

Initiate a design session by asking one clarifying question to understand the project goal and success criteria.

Frequently Asked Questions about brainstorming

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

FAQPage Schema

How do I turn vague product ideas into concrete design plans and requirements?▼

To turn vague ideas into design plans, use structured brainstorming and collaborative dialogue to clarify goals, constraints, and acceptance criteria. This process guides teams stepwise from initial concept through context checks to a clear design outline ready for implementation.

What is the best way to elicit project requirements for early-stage product work?▼

The best way to elicit requirements for early-stage product work is asking clarifying questions one at a time. This collaborative dialogue refines the project purpose, establishes success criteria, and ensures all constraints are captured before proposing approaches.

How do I scope features and propose design approaches with trade-offs?▼

To scope features and propose design approaches, evaluate the project context by reviewing repository files and recent activity. Then generate two to three approaches with trade-offs and a recommended option to validate the design direction before proceeding.

Can I use structured brainstorming to write a design doc for implementation planning?▼

Yes, you can use structured brainstorming to write a design doc for implementation planning. After proposing approaches and presenting a design outline, the workflow obtains user approval and transitions directly into formal planning actions.

Does this brainstorming workflow work without external dependencies or components?▼

Yes, this brainstorming workflow operates without external dependencies or components. It coordinates a stepwise workflow using context checks and collaborative dialogue natively to guide teams from idea to design-ready plans.

When should I not use a collaborative dialogue approach for design validation?▼

You should not use a collaborative dialogue approach for design validation when your project goals and constraints are already fully defined. This workflow relies on interactive requirements elicitation, making it redundant for tasks that skip early-stage scoping.