brainstorming

Transform raw ideas into validated designs through structured dialogue.

150|51|Updated Mar 14, 2026

Search Tags:#design #architecture #brainstorming #ideation #requirements #validation

Ready to run

npx skills add https://github.com/AratKruglik/claude-laravel --skill brainstorming-aratkruglik

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/AratKruglik/claude-laravel/tree/main/.claude/skills/brainstorming
Command: npx skills add https://github.com/AratKruglik/claude-laravel --skill brainstorming-aratkruglik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill transforms vague ideas into clear, validated designs and specifications by facilitating structured dialogue before any implementation begins, preventing premature implementation, hidden assumptions, and misaligned solutions.

Core Features & Use Cases

Idea Validation: Ensures a shared understanding of the purpose, target users, constraints, and success criteria of a proposed feature or design.
Design Facilitation: Guides the exploration of multiple design approaches, clearly explaining trade-offs before a final design is selected.
Use Case: Before starting development on a new user authentication flow, this skill would be used to clarify requirements, explore different security models, and document the final chosen architecture.

Quick Start

Use the brainstorming skill to help design a new user profile page.

Frequently Asked Questions about brainstorming

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

FAQPage Schema

How do I transform raw ideas into validated designs before implementation?▼

Design validation requires disciplined questioning to clarify requirements, target users, and success criteria, ensuring shared understanding and preventing misaligned solutions before architectural planning or development starts.

What is the best way to facilitate brainstorming for architectural planning?▼

Design exploration for architecture requires evaluating multiple approaches and explicitly stating trade-offs. This ensures the final selected design aligns with constraints and prevents premature implementation of unsuitable models.

How do I clarify requirements for a new feature before starting development?▼

Requirements clarification prevents hidden assumptions by using disciplined dialogue to define feature scope and success metrics, resulting in a shared understanding of the design before development begins.

Can I use structured ideation to prevent premature implementation of features?▼

Ideation processes prevent premature implementation by requiring trade-off analysis and explicit assumption clarification, transforming vague concepts into validated specifications before engineering resources are committed.

Does structured dialogue help with exploring design approaches and trade-offs?▼

Exploring design approaches through structured reasoning surfaces hidden assumptions and documents trade-offs, resulting in a validated architectural choice that aligns with the original feature requirements.