'brainstorm' 검색 결과

Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods. Use when the user says help me brainstorm or help me ideate.

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

Structured creativity methods for idea generation: SCAMPER, Six Thinking Hats, Mind Mapping, Reverse Brainstorming, TRIZ, and Rapid Ideation.

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

Combines multi-agent brainstorming, the /grill-me slash command, and the 3 Core Godmodes (godmode-engineering, godmode-ui-ux, godmode-shipping) to force a comprehensive, multi-agent ideation and technical design workflow, ending in a plan-canvas review and a hand-off to /startcycle-graph. Use when the user asks to brainstorm, ideate, design, scope or sharpen a plan, idea or product, or when broad exploration before a build is the situation.

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

Multi-agent brainstorming: async opinion collision with expert personas. Mixed Codex/Claude Code engine. Use when multiple AI agents need to collaboratively discuss, debate, and converge on solutions through structured dialog. Triggers: brainstorm, multi-perspective discussion, opinion collision, expert debate, war room, collective intelligence, 头脑风暴, 多视角讨论, 集思广益.

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

Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods. Use when the user says help me brainstorm or help me ideate.

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

Turn a rough idea into a fully approved design before any code is written. Load when the user wants to brainstorm, explore ideas, design a feature, think through approaches, plan a new capability, or figure out what to build. Also triggers on "let's think through", "help me design", "explore options", "what's the best approach for", "I have an idea for", "before we build", or any request to design something before implementation. Enforces a hard gate: no code, no implementation until user approves a design. For executable feature specs (FRs, NFRs, ACs as Given/When/Then), route to `feature-spec` instead — brainstorming owns approach and architecture, not machine-readable requirements.

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

Explore a product or project idea before writing code. Use startup questions to examine demand, alternatives, and a focused starting point, or brainstorm personal and learning projects in Builder mode, then save a design document.

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

• Examine demand for a new product idea
• Brainstorm a personal or learning project
• Narrow the initial target and scope

Turn rough ideas into developed designs through structured questions and exploration of alternatives. Use it early in concept work to clarify an initial idea, consider different directions, and shape a more concrete design.

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

• Developing a rough idea into a concrete design
• Exploring alternative directions for a concept
• Clarifying an idea through structured questions

Generate domain name ideas for a new product or startup, then check availability across domain endings such as .com, .io, .dev, and .ai to help compare naming options.

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

• Brainstorming domain names for a new service
• Checking availability across several domain endings
• Comparing domain options for a product name

Generate domain name ideas based on a project's purpose and audience, then check availability across endings such as .com, .ai, and .dev. Receive alternative names and explanations to help compare suitable options.

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

• Choosing a domain for a new product
• Finding alternatives to a taken domain
• Naming a personal portfolio website

Ask Claude or Gemini through a locally installed command-line tool for focused questions, reviews, brainstorming, or second opinions. Save the prompt, original response, summary, and next steps in a reusable Markdown file.

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

• Get a second opinion on a proposed approach
• Ask Claude or Gemini to review work
• Save brainstorming results for later use

Explore product problems, generate alternative solutions, and challenge the assumptions behind an idea through conversation. It helps product managers compare directions, identify weak points, and choose questions or experiments to investigate before committing to development.

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

• Exploring the user problem behind a feature request
• Generating alternatives to an initial product idea
• Testing the assumptions that could undermine an idea

Explore features for a new product through product management, design, and engineering perspectives. Generate five ideas from each viewpoint, then select five priorities with reasoning and assumptions to test before developing the concept further.

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

• Exploring features for a startup idea
• Comparing ideas from three professional perspectives
• Choosing five ideas to validate first

Draft three alternative sets of team OKRs, pairing a qualitative goal with three measurable results. Use company strategy and team context to propose numerical targets, explain each option, and support discussions about quarterly priorities and customer or business outcomes.

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

• Drafting quarterly team goals
• Aligning team priorities with company strategy
• Turning broad objectives into measurable results

Generate five marketing ideas for a product and its target audience, with limited budgets and resources in mind. Each idea includes a channel, a core message, an explanation of audience appeal, and reasons it uses resources efficiently.

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

• Brainstorming promotions on a limited budget
• Comparing campaign channels and messages
• Exploring fresh approaches to product promotion

Build a quick, disposable game prototype in HTML, a game engine, or on paper to test one core mechanic. Use playtest findings to decide whether to continue, change direction, stop, or leave the idea unassessed.

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

• Test whether a core game mechanic is fun
• Compare several variations of a game concept
• Explore a mechanic change during production

Turn a vague feature idea into clear requirements through dialogue. Define what to build, its scope, and success criteria, then capture the result in a short chat summary or a requirements document ready for implementation planning.

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

• Clarifying a vague feature idea
• Narrowing the scope of an ambitious improvement
• Documenting requirements before implementation planning

Develop a product or side-project idea through guided questions and premise checks. Startup discussions examine evidence of demand, while builder discussions explore possibilities and scope, producing a design document before implementation begins.

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

• Examining demand for a startup idea
• Defining the smallest useful internal project
• Shaping a hackathon or side-project idea

Generate domain name ideas based on a project's purpose and audience, then check availability across endings such as .com, .ai, and .dev. Receive alternative names and explanations to help compare suitable options.

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

• Choosing a domain for a new product
• Finding alternatives to a taken domain
• Naming a personal portfolio website

Create and edit FigJam boards through Figma's use_figma tool. Organize meeting or brainstorming content with sections, sticky notes, shapes, connectors, and tables, and inspect existing board elements before updating their text, styling, or positions.

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

• Prepare a brainstorming board with sticky notes
• Build a retrospective or meeting board
• Draw diagrams with shapes and connectors

Create and edit FigJam boards through Figma's use_figma tool. Organize meeting or brainstorming content with sections, sticky notes, shapes, connectors, and tables, and inspect existing board elements before updating their text, styling, or positions.

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

• Prepare a brainstorming board with sticky notes
• Build a retrospective or meeting board
• Draw diagrams with shapes and connectors

Interactive system flow tracing across CODE, API, AUTH, DATA, NETWORK layers with SQLite persistence and Mermaid export. Use for security audits, compliance documentation, flow tracing, feature ideation, brainstorming, debugging, architecture reviews, or incident post-mortems. Triggers on audit, trace flow, document flow, security review, debug flow, brainstorm, architecture review, post-mortem, incident review.

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

Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.

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

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.

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