brainstorming

Facilitate structured brainstorming with one-question-at-a-time clarification and a decision log.

3|Updated Apr 1, 2026

Search Tags:#design #architecture #brainstorming #ideation #requirements #facilitation #decision-making

Ready to run

npx skills add https://github.com/vtgiang-dotcom/Solo-Code-Harness --skill brainstorming-vtgiang-dotcom

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/vtgiang-dotcom/Solo-Code-Harness/tree/main/.gemini/antigravity/skills/brainstorming
Command: npx skills add https://github.com/vtgiang-dotcom/Solo-Code-Harness --skill brainstorming-vtgiang-dotcom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured ideation is often uncoordinated, leading to misaligned design decisions, scope creep, and missed constraints. This skill acts as a design facilitator to slow the process, surface assumptions, and keep the team aligned before designing.

Core Features & Use Cases

One-question-at-a-time clarification to gather intent and constraints.
Mandatory non-functional requirements capture to ensure quality attributes are considered early.
Explore 2-3 viable design approaches with trade-offs to surface risks and dependencies.
Maintain a Decision Log with rationale and exit criteria to document choices and next steps.

Quick Start

Start by stating the goal and constraints, then answer one clarifying question per message to align on intent.

Frequently Asked Questions about brainstorming

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

FAQPage Schema

How do I facilitate structured brainstorming for product design and architecture exploration?▼

Structured brainstorming is facilitated by asking one clarifying question at a time, capturing non-functional requirements, exploring 2-3 design approaches, and maintaining a decision log with clear exit criteria.

What is the best way to refine requirements and align teams before starting design?▼

Requirement refinement is best handled by slowing down the process to surface assumptions, explicitly capturing mandatory non-functional requirements early, and exploring viable design approaches with documented trade-offs.

How does one-question-at-a-time clarification work for design ideation?▼

One-question-at-a-time clarification works by guiding users to state their goal and constraints first, then answering a single clarifying question per message to progressively align on design intent.

Why do I need to document a decision log with rationale during architecture exploration?▼

Documenting a decision log with rationale during architecture exploration ensures that design choices, risks, dependencies, and next steps are recorded to prevent scope creep and misaligned decisions.

Can this structured ideation process help with decision-making across teams?▼

Yes, structured ideation helps with decision-making across teams by acting as a design facilitator that surfaces assumptions, explores 2-3 viable approaches with trade-offs, and documents choices with clear exit criteria.

When should I not use a structured brainstorming approach for design?▼

You should avoid structured brainstorming when rapid prototyping is needed without requirement alignment, as this approach intentionally slows ideation to capture constraints and surface non-functional requirements.