'brainstorm' 검색 결과

Decompose tasks into structured, outcome-defined process entries with complexity triage. Load when user says "decompose this", "break this down", "what steps do I need", "plan this out", "what's the process for", "how do I approach this", or when any complex task needs structured execution planning. Includes a problem-understanding pass before complexity triage. Routes to `problem-to-plan` when the user needs planning deliverables (spec + plan + TODO). Does NOT replace brainstorming — brainstorming is design approval (upstream), this is execution planning (downstream).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Facilitate idea generation sessions that actually produce diverse, useful options instead of degenerating into the first plausible answer. Use for product ideation, feature exploration, problem-reframing, naming, design alternatives, strategic option-generation, or any task where the failure mode is "we picked the obvious thing too fast." Covers solo and group sessions, divergence/convergence discipline, technique selection (SCAMPER, Crazy Eights, How Might We, 6-3-5 Brainwriting, Reverse Brainstorming, Worst Possible Idea, Random Stimulus), facilitation moves for handling dominant voices and groupthink, and structured convergence to a shortlist with rationale. Outputs a session artifact with options generated, evaluation, shortlist, and the rejected-but-interesting list.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generates creative, research-backed domain name ideas and checks availability with competitor analysis, pattern recognition, and quality scoring. Use when brainstorming brandable domains for a product or project.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

새 기능이나 기획을 시작하기 전에 대화로 목적, 선호, 제약을 정리합니다. 필요하면 그림이나 시제품으로 이해를 확인하고 작업 규모에 맞는 설계를 작성합니다.

• 새 기능의 목적 명확히 하기
• 강연이나 사업 아이디어 정리
• 화면이나 방의 배치 비교

대화 시작 시 관련 스킬을 확인하고 응답이나 작업 전에 불러오는 절차를 정합니다. 작업 방식을 정하는 스킬을 우선하며 실행 환경별 안내로 연결합니다.

• 대화를 시작할 때 스킬을 확인할 때
• 기능 개발 전에 스킬을 선택할 때
• 오류 조사 전에 스킬을 선택할 때

새 제품이나 개인 프로젝트 아이디어를 대화로 정리하고 문제, 수요, 구현 방법을 검토해 설계 문서로 만듭니다. 창업, 사내 기획, 학습이나 취미 등 목적에 맞춰 질문합니다.

• 창업 아이디어의 수요 검토
• 사내 프로젝트 기획 정리
• 학습이나 취미 개발 아이디어 구체화

업무 절차와 시스템 흐름을 색깔 있는 메모지와 곡선 화살표로 도식화합니다. 분기와 합류를 표현하고, 시작 안내나 운영 설명에 쓸 단일 HTML 파일로 만듭니다.

• 사용 시작까지의 절차 도식화
• 운영 절차 설명
• 시스템 구조 소개

Find suitable marketing partners and plan joint campaigns for SaaS businesses. Compare audience fit, develop shared content or event ideas, and define responsibilities, lead sharing, promotion commitments, and measures of success.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding and comparing potential marketing partners
• Planning a joint webinar or guide
• Defining responsibilities and lead sharing

Find marketing ideas for a SaaS or software product based on its stage, audience, budget, and team. Draw from 139 ideas to shortlist relevant options, with starting steps, expected outcomes, and resources needed.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding new ways to promote a software product
• Choosing marketing tactics on a limited budget
• Exploring promotion ideas before launch

Turn ideas and reference materials into a blog draft through research, outline approval, and revision. The workflow includes source citations, adjustments for the intended audience and tone, and separate files for each draft version.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turning research materials into a blog post
• Planning an article for a specific audience
• Drafting articles with source citations

Turn written descriptions of processes, systems, and ideas into editable Excalidraw diagrams. Create flowcharts, mind maps, relationship diagrams, and architecture diagrams, then receive an .excalidraw file to open and refine.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Visualizing business procedures as flowcharts
• Explaining system components and connections
• Organizing brainstorming ideas into mind maps

Guide an AI partner’s approach to fast creative work and developing ideas. Drawing on Vega’s account of a long collaboration, it emphasizes honest uncertainty, adapting to the person’s pace, thoughtful disagreement, and keeping human ownership of achievements.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Develop ideas during a fast brainstorming session
• Adapt dialogue to a collaborator’s pace
• Build trust through honest uncertainty

Coordinate a small AI development team with planning, implementation, and optional independent testing roles. Adapt the process to the work’s complexity, prepare pull requests, and preserve decisions and next steps so later sessions can continue.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Starting development or taking over an existing project
• Coordinating implementation and independent testing
• Comparing perspectives on product or architecture decisions

Turn a feature idea into a design document through focused dialogue. The skill clarifies goals and constraints, compares two or three approaches, and reviews the design in sections before documenting architecture, data flow, errors, and testing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Clarifying requirements for a new feature
• Comparing alternative implementation approaches
• Reviewing a design section by section

Explore three to five ways to earn revenue from a product or feature. Compare customer fit, estimated costs and returns, and risks, then design low-cost experiments and prioritize which approaches to test first.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Explore revenue models for a new product
• Compare subscription and usage-based pricing
• Design experiments to test willingness to pay

Develop three to five product vision statements from company and product context. Explore a meaningful, realistic future for customers and the business, then recommend the strongest option with reasons and explain its connection to company values and market opportunities.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Defining a vision for a product
• Revising a vision as strategy evolves
• Aligning a team around a shared direction

Turn a new product idea into a testable hypothesis and two or three simple experiments. Define target customers, expected actions, measurement methods, and success thresholds to assess demand through behavior such as sign-ups, pre-orders, or paid commitments.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Testing demand before building a new product
• Planning landing page or waitlist experiments
• Checking willingness to pay through pre-orders

Explore five ways to position a product against competitors. Review five leading competitors, identify gaps in their messaging, and develop positioning statements with audience rationale, supporting messages, and the product advantages behind each idea.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Defining positioning for a new product
• Exploring ways to stand apart from competitors
• Finding gaps in competitor messaging

Generate five product name ideas based on brand values, target customers, and market positioning. Each suggestion includes its rationale, fit with the existing brand, memorability, and potential domain or trademark concerns.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Name a new product or feature
• Explore names when rebranding
• Compare name options before launch

Plan low-effort experiments to check assumptions about an existing product before building a feature. Compare prototypes, A/B tests, and other methods, with a clear assumption, procedure, metric, and success threshold for each experiment.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking feature assumptions before implementation
• Planning prototype usability tests
• Defining metrics and success thresholds for A/B tests

Turn requirements for software or other multi-step work into a structured plan with an approach, constraints, and verification steps. It also helps develop existing plans, researching decisions before handing the work over for execution.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning implementation from requirements
• Breaking complex work into manageable steps
• Adding detail to an existing plan

Build a disposable prototype to test how a product should work, feel, or look before committing to an approach. Let the user experience it, record their choices, and carry those decisions into requirements or further planning.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Trying a navigation flow before committing to it
• Judging layout density and color choices
• Resolving design questions that sketches cannot answer