brainstorming

Guide brainstorming ideas into concrete designs through one-question-at-a-time exploration.

4|Updated Dec 7, 2025
One-click install
npx skills add https://github.com/icartsh/icartsh_plugin --skill brainstorming-icartsh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/icartsh/icartsh_plugin/tree/main/icartsh-plugin/skills/brainstorming
Command: npx skills add https://github.com/icartsh/icartsh_plugin --skill brainstorming-icartsh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

코드나 구현 계획을 작성하기 전, 아이디어를 구체화하기 어렵거나 팀과의 협업이 필요할 때, 거친 아이디어를 공통 설계로 발전시키는 데 도움을 줍니다. 협력적인 질문, 대안 탐색 및 점진적 검증을 통해 아이디어를 명확한 설계로 다듬고, 구현 전에 합의를 이끌어냅니다. 단, 이미 명확한 'Mechanical' 프로세스가 필요한 경우에는 사용하지 마십시오.

Core Features & Use Cases

  • 협업 대화를 통해 아이디어의 목적, 제약 조건, 성공 기준을 정리합니다.
  • 2-3가지 대안 설계 방향을 제시하고 비교합니다.
  • 아이디어를 200-300자 분량의 설계 섹션으로 나눠 제시하고, 각 섹션에서 합의를 확인합니다.
  • 점진적 검증과 설계 확장을 지원합니다.

Quick Start

현재 프로젝트 맥락을 이해한 뒤, 아이디어를 구체화하기 위한 첫 질문을 한 가지씩 제시하도록 시작합니다.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn rough ideas into concrete designs before implementing?

Brainstorming facilitation structures idea refinement through collaborative questioning and incremental validation. It guides you from loose concepts through architecture, components, and data flow decisions, breaking designs into 200-300 character sections so each part is validated with your team before proceeding to implementation.

When should I use collaborative ideation versus jumping straight to code?

Use collaborative ideation when ideas are still rough, team alignment is needed, or architecture isn't yet clear. Skip it if you already have a defined mechanical process. The Skill excels at aligning stakeholders and uncovering constraints early, preventing rework after code begins.

How does structured design exploration improve team collaboration on projects?

Structured exploration presents 2-3 design alternatives for comparison, clarifies purpose and success criteria upfront, and validates agreement section-by-section. This prevents misaligned assumptions, ensures everyone understands constraints, and builds consensus before development starts.

Can I use this approach for product development workflows?

Yes. The Skill applies to product development, architectural planning, and collaborative design work. It guides teams through systematic refinement covering architecture, components, data flow, error handling, and test criteria—all standard concerns in product feature design.

What should I have ready before starting the design process?

You need the project context, initial rough ideas or problem statement, and ideally your team available for collaborative input. The Skill begins by understanding your current situation, then asks focused questions one at a time to crystallize intent and constraints.