brainstorm

Structure open-ended questions into evaluated options with trade-offs.

8|2|Updated May 3, 2026
One-click install
npx skills add https://github.com/ejoongseok/claude-settings --skill brainstorm-ejoongseok
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/ejoongseok/claude-settings/tree/main/claude-code/skills/brainstorm
Command: npx skills add https://github.com/ejoongseok/claude-settings --skill brainstorm-ejoongseok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

이 스킬은 열린 질문과 아이디어 발산을 구조화해서, 회의나 메모 단계에서 끝나지 않고 코드베이스 맥락에서 트레이드오프로 평가한 뒤 다음 실행 단계까지 연결되도록 돕습니다.

Core Features & Use Cases

  • 유형 기반 브레인스토밍: 문제 해결 / 기술 의사결정 / 아이디어 발산 / 정리 구조화 중 입력 상황에 맞게 접근합니다.
  • 프로젝트 맥락 기반 평가: 가능한 경우 CLAUDE.md, bot/INDEX.md(또는 .local.claude/INDEX.md), .local.claude/modules/*.md 등 문서를 읽어 “이미 있는 패턴 재사용 가능성”을 우선 확인합니다.
  • 발산 → 수렴(비교표) 출력: 구현 난이도·시간·영향 범위·확장성·리스크를 기준으로 비교표를 만들고 추천을 트레이드오프 관점에서 제공합니다.
  • 다음 스킬 파이프라인 연결: 결론 후 /prd, /srs, /todo, /poc 중 적절한 다음 단계로 넘길 입력을 구성합니다.

Quick Start

CLAUDE 코드베이스를 참고해 “새 기능 X를 어떤 방식으로 구현할지”에 대한 브레인스토밍을 진행해 비교표와 추천 방향, 그리고 /todo로 넘길 요약을 만들어줘.

Frequently Asked Questions about brainstorm

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

FAQPage Schema
How do I evaluate technical decisions with a trade-off analysis from brainstorming notes?

Trade-off analysis for technical decisions structures open-ended brainstorming notes by comparing implementation difficulty, time, impact, scalability, and risk to produce an evaluated recommendation table.

What is the best way to turn project ideas into evaluated next steps for engineering planning?

Turning project ideas into evaluated next steps involves structuring ideation against existing codebase patterns, generating a comparison table across defined criteria, and preparing pipeline handoff inputs.

How do I structure brainstorming sessions to check codebase reuse possibilities before roadmapping?

Structuring brainstorming for codebase reuse reads project context documents like CLAUDE.md and INDEX.md to identify existing patterns, ensuring roadmapping prioritizes reuse before generating new technical decisions.

Can I use project context documents to generate a comparison table for technical decision-making?

Yes, project context documents provide the foundation to generate comparison tables for technical decision-making, evaluating options against implementation difficulty, time, impact, scalability, and risk.

Does brainstorming output support pipeline handoff to downstream skills like PRD or POC generation?

Yes, brainstorming output supports pipeline handoff by preparing structured inputs that route evaluated conclusions to downstream steps like PRD, SRS, todo, or POC generation.

What are the limitations of using structured ideation expansion for complex engineering trade-offs?

Structured ideation expansion for complex engineering trade-offs requires available project context documents for codebase reuse evaluation, limiting its effectiveness when context files are missing or incomplete.