brainstorming

Guide structured collaboration to turn ideas into detailed designs.

Updated Jan 14, 2026

Search Tags:#design #documentation #brainstorming #collaboration #ideation #specification #requirements

Ready to run

npx skills add https://github.com/CarlosDoers/poems-guest-book --skill brainstorming-carlosdoers

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/CarlosDoers/poems-guest-book/tree/main/.agent/skills/brainstorming
Command: npx skills add https://github.com/CarlosDoers/poems-guest-book --skill brainstorming-carlosdoers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming ideas into designs can be time-consuming and error-prone without a structured, collaborative approach. This skill guides teams to clarify intent, gather requirements, and converge on a design plan through a sequence of targeted questions and iterative feedback.

Core Features & Use Cases

Structured dialogue that elicits context, goals, and constraints before ideation.
Proposes 2-3 design approaches with trade-offs and a recommended option.
Produces incremental design sections (200-300 words each) with built-in validation prompts and documentation notes.
Supports documentation handoff by outlining architecture, components, data flows, and acceptance criteria.

Quick Start

Explain your idea and let the assistant guide you through a step-by-step design exploration.

Frequently Asked Questions about brainstorming

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

FAQPage Schema

How do I turn early-stage product ideas into detailed designs?▼

To turn product ideas into detailed designs, you provide your initial concept and the assistant guides you through structured, step-by-step collaboration. It elicits context, gathers requirements, and validates incremental design sections to produce a complete plan.

What is the best way to elicit requirements for UX design documentation?▼

Eliciting requirements for UX design documentation is best handled through targeted sequential questions. This approach clarifies intent, gathers constraints, and validates design options iteratively before generating the final specification.

Can I use structured brainstorming for software architecture documentation?▼

Yes, structured brainstorming supports software architecture documentation by guiding context gathering and requirement elicitation. It outlines architecture, components, data flows, and acceptance criteria for project handoff.

Does this approach provide multiple design options during ideation?▼

Yes, this ideation approach proposes 2-3 design options during collaboration. It presents the trade-offs for each approach and provides a recommended option to help teams converge on a validated design plan.

How does incremental validation work during design collaboration?▼

Incremental validation works by producing design sections of 200-300 words each with built-in validation prompts. This allows teams to review, provide iterative feedback, and confirm requirements before moving to the next section.

When do I need a structured dialogue for project specification?▼

You need a structured dialogue for project specification when brainstorming ideas into designs becomes time-consuming or error-prone. It ensures teams clarify intent, gather constraints, and converge on a detailed design plan without missing requirements.