brainstorming

Coordinate exploratory brainstorming sessions to clarify needs and produce design concepts.

6|1|Updated Dec 29, 2025

Search Tags:#architecture #brainstorming #ideation #requirements #design-doc #stakeholder-alignment #design-process

Ready to run

npx skills add https://github.com/mgajewskik/opencode-config --skill brainstorming-mgajewskik

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/mgajewskik/opencode-config/tree/main/skills/brainstorming
Command: npx skills add https://github.com/mgajewskik/opencode-config --skill brainstorming-mgajewskik

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Brainstorming upfront ensures you understand user needs, align on goals, and specify requirements before diving into design or implementation.

Core Features & Use Cases

Structured discovery: assess project context, constraints, and success metrics to shape the design brief.
Guided questioning: sequential clarifications to refine scope, success criteria, and constraints.
Design-forward output: produce a clear design direction and decision record for stakeholder alignment.

Quick Start

Begin by clarifying the project goal, constraints, and success criteria, then ask one clarifying question at a time to refine the brief.

Frequently Asked Questions about brainstorming

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

FAQPage Schema

How do I gather requirements and align stakeholders before starting product design?▼

Structured brainstorming clarifies user needs by assessing project context, constraints, and success metrics to shape the design brief. It uses sequential questioning to refine scope and produces a decision record for stakeholder alignment.

What is the design-first brainstorming process for project discovery?▼

Design-first brainstorming is a structured discovery process that explores project context, asks clarifying questions, proposes approaches, presents designs, and writes a design doc for user sign-off before implementation.

How do I translate exploratory ideation into a concrete design doc?▼

Translate ideation into a design doc by guiding sequential clarifications to refine constraints, proposing design directions, and documenting the final decisions to secure user sign-off before technical implementation.

Can I use this structured brainstorming approach for UX and technical architecture projects?▼

Yes, this approach applies to product, UX, and technical architecture projects requiring upfront discovery, requirements gathering, and design validation before implementation begins.

When do I need a design validation phase before moving to implementation?▼

You need design validation when projects require upfront discovery and stakeholder alignment. Brainstorming ensures you understand user needs and specify requirements before diving into implementation.

What's the best way to start a discovery session for design requirements?▼

Begin by clarifying the project goal, constraints, and success criteria, then ask one clarifying question at a time to refine the design brief and ensure proper stakeholder alignment.