'brainstorm' 검색 결과

Explore and debate solutions before writing code. Use when the user poses a design question, asks "how should I approach X", wants to think through options before committing, or says anything like "let's brainstorm", "what's the best way to...", "I'm not sure how to tackle this", or "should I use X or Y". Always runs before /ck:plan for novel or ambiguous features. No code is written — only: explore → clarify → spec → report.

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

Phase 1 of the SRS workflow. User gives a project topic → AI runs a deep, categorized brainstorm (5 mandatory rounds) to fully understand actors, features, scope boundary, tech constraints, and business rules before writing anything.

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

Explore and debate solutions before writing code. Use when the user poses a design question, asks "how should I approach X", wants to think through options before committing, or says anything like "let's brainstorm", "what's the best way to...", "I'm not sure how to tackle this", or "should I use X or Y". Always runs before /ck:plan for novel or ambiguous features. No code is written — only: explore → clarify → spec → report.

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

Phase 1 of the SRS workflow. User gives a project topic → AI runs a deep, categorized brainstorm (5 mandatory rounds) to fully understand actors, features, scope boundary, tech constraints, and business rules before writing anything.

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

Use when the user wants to explore options, weigh approaches, or think through uncertainty before committing to a direction. Collaborative brainstorming and rubber ducking — divergence-first thinking partner.

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

Used by the Lead agent during Phase 6 (Brainstorm) to collaboratively explore user intent, requirements, and alternative approaches before locking in the architecture. Helps turn raw ideas into fully formed specs through natural dialogue.

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

设计脑暴 / 实现前方案校准：当用户想把已基本成立的想法、功能方向或产品问题，在写 PRD、画 mockup 或进入开发计划前，先比较方案、确认取舍、对齐 UI/视觉约束，并收敛成可执行设计 spec 时使用。 可用中文唤起：“先脑暴一下方案”“先不要写 PRD，帮我设计几种路径”“参考 brainstorming 把这个需求变成设计 spec” “实现前先讨论设计”。问题还没定义清楚时先用 ai-collaboration-calibration；已有方案要压力测试时用 grill-me； 直接写 PRD 时用 prd-architect；grill-me 返回精确设计 gap 时，本 Skill 只输出 Design Delta。

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

Generate or compare multiple technical approaches for one validated decision. Do not use for product discovery or an existing plan.

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

Use when answering factual or explanatory questions about the current project — codebase, architecture, conventions, workflows, constraints — with minimal cited evidence. Triggers on "how does X work here", "what does X mean", "why is X structured this way", "is this claim true in the repo", "explain X with sources". NOT for brainstorming or comparing approaches (mk:brainstorming), trade-off decisions (mk:party), debugging/root cause (mk:investigate), code review (mk:review), plans (mk:plan-creator), security audits (mk:cso), visual explanations/diagrams (mk:preview --explain), test-coverage gaps (mk:nyquist), library docs (mk:docs-finder), or workflow navigation (mk:help).

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

/brainstorm のユーザーストーリー品質を INVEST 基準で軽量チェックする。proposal.md 生成前にストーリーの構造的品質を確認し、問題があれば対話で改善を促す

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

PM-mode brainstorm helper. Captures the requirement via Socratic dialogue before any entry phase (`/intake`, `/spec`, `/tdd`) drafts its artifact. Stage 0 skip-check, Stage 1 gap-analysis, Stage 2 probe-loop, Stage 3 confirm-and-persist. Output lives at `docs/brief/<slug>.md`. Never proposes solutions — Stage 2 dialogue discipline is structurally enforced via `discipline.mjs`.

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

通用头脑风暴：4 种模式（产品/内容/构建/探索）× 6 阶段，强制前提挑战和 2-3 方案，产出可跨会话续聊的思考文档；支持 Mermaid/图辅助判断。 触发方式：用户说"头脑风暴"、"brainstorm"、"讨论一下"、"我有个想法"、"帮我想想"、"画图梳理想法"。

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

执行显式、编码前的 Product Discovery，把早期或模糊的软件想法转化为用户确认的 Intent、丰富方案卡片、对比矩阵、可编辑画布和可持续 D0 文档基线。仅当用户明确调用 $flight-brainstorm，准备在 Flight Control Run 之前探索空白、稀疏、不确定或方向发生重大变化的项目时使用；禁止因模糊请求或普通开发工作隐式触发。

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

Cursorで判断に迷う重要な論点を独立した熟考担当に検討させ、結論と未解決点を整理する。選択肢の比較や設計判断に確信を持てない場合に使う。要件をユーザーと決める場合は brainstorm、計画作成は deepplan。

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

判断に迷う重要な論点を独立した熟考担当に検討させ、結論と未解決点を整理する。選択肢の比較や設計判断に確信を持てない場合に使う。要件をユーザーと決める場合は brainstorm、計画作成は deepplan。

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

Interactive idea refinement using Socratic method to develop fully-formed designs

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

One-question-at-a-time design interrogation. Use when: 'grill me', 'interrogate this', 'one question at a time', 'brainstorm', 'let's brainstorm', 'let's discuss', 'lets discuss', 'discuss', 'walk me through', or design review start. Produces ADRs and glossary as decisions settle. Use for unsettled designs; for settled designs go straight to architecture-mode. When the design is unsettled and also has high ambiguity, several technical approaches, or security/data risk, load architecture-mode alongside.

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

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.

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

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.

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

Facilitate ideation, explore alternatives, and refine concepts through structured brainstorming techniques before implementation. Use when starting new projects, designing features, exploring solutions, evaluating tradeoffs, challenging assumptions, generating creative ideas, planning architecture, or refining rough concepts into detailed designs.

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

YC Office Hours — two modes. Startup mode: six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. Builder mode: design thinking brainstorming for side projects, hackathons, learning, and open source. Saves a design doc. Use when asked to "brainstorm this", "I have an idea", "help me think through this", "office hours", or "is this worth building". Proactively invoke this skill (do NOT answer directly) when the user describes a new product idea, asks whether something is worth building, wants to think through design decisions for something that doesn't exist yet, or is exploring a concept before any code is written. Use before /plan-ceo-review or /plan-eng-review. (gstack)

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

Orchestrator for the pre-decision business-idea lifecycle — generate ideas, model them, evaluate them, validate them with customers, and only then hand off to product-soul / brainstorming. Routes through `idea-generation`, `business-modeling`, `idea-evaluation`, and `customer-discovery`. Load when the user asks to explore business ideas, find a startup idea, evaluate a venture, validate an idea, says "what business should I start", "should I build this", "is this a good business", "I have a startup idea", "evaluate this venture", "model this business", "validate this idea", "Mom Test this", "Lean Canvas this", "Business Model Canvas", "Value Proposition Canvas", "go/no-go on this idea". Pre-decision suite — once one idea is committed, hands off to `product-soul`. Does NOT design features (use `brainstorming`) or audit built products (use `reality-check`).

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

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.

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