444건 · 관련도순
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Brainstorms and debates approaches, then drives toward an actionable decision. Use whenever someone needs a thinking partner for a decision they're facing: 'discuss', 'debate', 'brainstorm', 'weigh options', 'tradeoffs', 'should I do X or Y', 'help me decide', 'I'm torn between', 'sanity check my thinking', or 'what do you think about'. The user must be asking for help reasoning through a choice — not asking to build, fix, evaluate, plan, or modify something (even if the topic involves this skill itself). Picks the right decision lens, surfaces tradeoffs and blind spots, pushes back when reasoning is genuinely weak, and never implements.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run a structured brainstorm session for startup ideas. Takes a theme or problem and generates ideas with quick gut-checks. Use when the user wants to explore a space or generate new ideas.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
MANUAL TRIGGER ONLY: invoke only when user types /office-hours. 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 suggest when the user describes a new product idea or is exploring whether something is worth building — before any code is written.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Explore vague or ambitious ideas into a right-sized requirements-only unified plan. Use when the user wants to brainstorm, think through scope, decide what to build, or needs collaborative product framing before planning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you have a finalized brainstorm-beagle spec at `.beagle/concepts/<slug>/spec.md` and need a bite-sized, TDD-driven implementation plan before any code is written. Triggers on: "write a plan", "plan this spec", "turn the spec into a plan", "now plan the implementation", "write-plan". Reads the spec, designs the file structure, decomposes work into 2-5 minute TDD steps with exact paths and commands, self-reviews against the spec, gets user approval, then writes to `.beagle/concepts/<slug>/plan.md` and offers to generate an execution handoff prompt via the subagent-prompt skill. Does NOT brainstorm specs, write code, or execute the plan — produces the plan document (and an optional handoff prompt) only.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user has a fuzzy idea and wants to shape it into a concrete project spec before planning or building. Triggers on: "brainstorm this", "I have an idea for...", "help me think through this project", "what should I build", "spec this out". Also catches vague feature descriptions needing structured questioning to clarify scope. Does NOT write code, plan implementation, review strategy docs, or run strategy interviews — produces a WHAT/WHY spec through dialogue, not a HOW plan.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants to pressure-test a product, internal-tool, or OSS concept against Amazon's Working Backwards PRFAQ gauntlet before committing to a spec. Triggers on: "work backwards", "write a PRFAQ", "press release first", "is this idea worth building", "pressure-test this concept", "filter this before brainstorm", "is this a real product". Also catches solution-first pitches ("I want to build X that does Y") and technology-first pitches ("use AI to...") that need customer-first filtering. Produces a binary pass/fail verdict, not a polished doc. Hardcore coaching — direct, skeptical, concrete. On pass, hands off to brainstorm-beagle with a concept brief. Does NOT write code, plan implementation, scaffold projects, or draft specs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use as the follow-up to brainstorm-beagle when a spec has an Open Questions section (or quietly carries latent gaps) that need closing before planning or implementation can begin. Triggers on: "resolve the open questions", "close the gaps in this spec", "research the open items", "finalize my spec", "make this spec implementation-ready", "answer the TBDs". Also triggers whenever the user points at a brainstorm-beagle spec and asks for research, proposals, or answers to unresolved items. Orchestrates parallel research subagents when available (falls back to inline sequential research otherwise), proposes answers one at a time for user approval, then rewrites the spec in place so it arrives at planning with no known gaps. Does NOT write code, design implementation, or create plans — it only produces a complete spec.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you need a bite-sized, TDD-driven implementation plan but do NOT have a brainstorm-beagle spec to plan against. quick-plan reconstructs intent from the current conversation, fans out domain-expert exploration subagents across the codebase, and synthesizes the same plan format write-plan produces — without requiring `.beagle/concepts/<slug>/spec.md`. Triggers on: "quick plan", "plan this out", "plan what we just discussed", "turn this into an implementation plan", "plan this without a spec", "I don't have a spec, just plan it", "write-plan but no spec". Make sure to use this skill whenever the user wants an implementation or TDD plan and there is no spec to plan against — even if they just say "plan it" after discussing a feature. Writes to `.beagle/plans/<slug>/plan.md`. If a finalized spec already exists at `.beagle/concepts/<slug>/spec.md`, prefer write-plan. Does NOT brainstorm specs, write code, or execute the plan — produces the plan document (and an optional handoff prompt) only.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants to build or think through a strategy via guided conversation — for a company, product, team, career, or initiative. Triggers on "help me figure out our direction", "what should we focus on", strategic planning, competitive positioning, go-to-market strategy. Also catches indirect requests like prioritization struggles or "we have too many priorities". Does NOT review existing strategy documents (use strategy-review) or brainstorm project features (use brainstorm-beagle).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when reviewing, critiquing, or stress-testing an existing strategy document. Evaluates seven dimensions — diagnosis quality, guiding policy strength, action coherence, assumption exposure, falsifiability — with optional 7S, Five Forces, Balanced Scorecard, and Hoshin Kanri lenses. Triggers on: review my strategy, poke holes in this plan, what's weak here, strategy audit, red team this. Does NOT build strategy (use strategy-interview) or brainstorm project ideas (use brainstorm-beagle).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants to use Google Gemini for analysis, large files or codebases, sandbox execution, or brainstorming. Uses headless Gemini CLI scripts (no MCP). Triggers on "use Gemini", "analyze with Gemini", "large file", "sandbox", "brainstorm with Gemini".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Socratic design refinement before implementation — challenges assumptions, surfaces alternatives, identifies risks before code is written
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
当用户需要启动AI项目的创意发现阶段，组织跨职能团队寻找AI应用场景时使用。 用户在问"我们该做什么AI项目"、"怎么找到AI落地场景"、"brainstorm AI ideas"时激活。 不适用于: 组织完全没有AI专业知识（无内外部顾问可用）、问题已明确定义无需创意探索的场景。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Investigate a bounded Proto UI Contract, Prototype, Module, Host Capability, Adapter, schema, or ownership question and turn a genuinely unresolved direction into one semantic decision packet. Use for spec brainstorming, admission questions, competing semantic models, uncataloged behavior, or unresolved cross-layer boundaries.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structured marketing brainstorming when direction is unclear. Use when the agent doesn't know which skill to run, the user is vague about what they need, there are multiple valid marketing paths, or someone says 'I don't know where to start', 'what should we market', 'explore approaches', 'help me think through this', 'marketing ideas', 'what campaign should I run', 'where do I start with marketing', 'what's our marketing plan', or 'I have no idea how to promote this'. Explores 2-3 approaches and recommends the best path forward with a specific next-skill handoff. Even vague frustration like 'nobody knows about my product' or 'how do I get users' should trigger this when no specific channel or tactic is mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
캠페인 브레인스토밍 에이전트. 3인 전문가 에이전트(전략가/크리에이터/데이터분석가)가 개별 브레인스토밍 후 크로스리뷰 토론으로 최적안을 도출합니다. campaign_brief.md 생성 → 제안서 파이프라인(Step 3)으로 연계. 트리거: 브레인스토밍, 캠페인 기획, 아이디어, brainstorm, 캠페인 전략, 크리에이티브
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
You MUST use this before any creative work — creating features, building components, drafting documents, designing workflows, or modifying behavior. Explores your human partner's intent, requirements, and design before any implementation begins.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Divergent ideation across model families — the same brainstorm, but each cognitive frame is handed to a different model (Claude sub-agent, OpenAI Codex, a cheap third via OpenCode) so the ideas diverge by frame and by model priors at once. Use for open design questions, architecture and API shape, naming, schema choices, fuzzy bugs with no known root cause, or on "multi adhd", "brainstorm with everyone", "wide ideas from all models". Skip for lookups, syntax, and anything phrased as "quick", "standard" or "canonical".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Timeboxed ideation on a topic where lens-driven proposers generate structurally different ideas, blind critics cull them, and pairwise judges rank the survivors on a tournament ladder instead of 1-10 scores, evolving the leaders until the clock runs out. Use when the user wants to brainstorm, explore ideas, discover features, generate options, or think through possibilities for a specified duration. Triggers on requests like "brainstorm X for 30 minutes", "ideate on X", "spend an hour thinking about X", "what features should we build", "explore options for X". Not for executing a task over time (timeboxed-iterating) or optimizing a measurable metric (autoresearch).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Conduct a complete feature workflow in one skill — brainstorm, plan, TDD implementation, self-review, delivery summary — with hard gates between stages: no stage starts until the prior stage's artifact exists on disk (brainstorm note, plan doc, green tests per step)..
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.