'launch' 검색 결과

디자인팀의 제품 도입 제안을 의사 결정에 쓸 수 있는 HTML 슬라이드로 만듭니다. 전용 템플릿으로 구성과 본문, 발표자 노트를 정리해 내부 공유를 돕습니다.

• 디자인팀에 제품 도입을 제안할 때
• 팀 책임자와 IT 담당자용 자료를 만들 때
• 내부 추진자가 공유할 제안서를 만들 때

Launch and supervise gator agents for specific GitHub issues or pull requests in OpenShell. Check isolated execution environments, inspect logs, restart stalled agents, and test model or image overrides without changing default settings.

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

• Launch gator to review and monitor a specific pull request
• Inspect sandbox status and runtime logs
• Restart a stalled or outdated gator agent

Prepare an initial review of patents that might affect a product launch. Compare product features with individual patent claim elements, record uncertainties and search limits, and produce a memo for patent counsel. It does not determine launch clearance.

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

• Review possible patent obstacles before a launch
• Compare product specifications with patent claim elements
• Organize questions for patent counsel

Connect an Expo project to the Codex app Run button by creating a local launch script and action configuration. Start the development server from the app, view its logs, and optionally add platform-specific launch buttons.

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

• Starting an Expo project from the Codex app Run button
• Adding iOS, Android, or web launch buttons
• Using the same launch script in Codex and the shell

Set up a repeatable build, launch, and debugging workflow for macOS apps using Xcode or SwiftPM, Swift’s package manager. A project script handles relaunching, connects to the Codex Run button, and supports logs and process checks.

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

• Build and launch a macOS app with one script
• Connect a project to the Codex Run button
• Investigate build errors or startup failures

Use when the user asks to "plan launch pricing", "design pricing tiers / packaging", or "set up a launch discount / early-bird offer"; produces a launch pricing and packaging plan — tier structure and naming, a value-to-price map aligned to the message house, a launch-offer ladder with a true deadline reason, beta / early-adopter pricing with a post-launch graduation path, and guarantee / refund terms — with every price claim and offer term submitted to memory/events/claims.ndjson. Not for the canonical offer / claim record — use offer-claims-registry; not for paid-newsletter subscription economics — use newsletter-monetization-planner; not for ad bidding — use bid-strategy-planner. 发布定价/梯度打包/早鸟优惠/保证设计

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

Takes something built and gets it into the market — tiering the launch to match what it actually warrants, sequencing internal readiness before external announcement, preparing sales and support to answer the questions it creates, choosing the date for a reason, and measuring adoption rather than announcement reach. Use this to plan a launch, right-size one that is consuming more than it deserves, work out why a released feature nobody uses was launched loudly, or run the weeks after launch day.

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

Plan and execute e-commerce product launches. Pre-launch, launch day, and post-launch playbooks for Amazon, Shopify, and multi-channel sellers. Covers inventory, pricing, advertising, and review strategy.

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

When the user wants to plan cold start, get first users, or launch a new product with zero traction. Also use when the user mentions "cold start," "cold start problem," "first users," "seed users," "finding users," "finding early users," "Fiverr Upwork," "comment outreach," "Twitter search users," "product launch strategy," "0 to 1 growth," "early-stage acquisition," "launch channels," "get first customers," "Product Hunt launch," "AppSumo," "LTD," "indie hacker," "bootstrapping," or "solo founder." For directory listing copy and submissions, use directory-submission. For Product Hunt day-of execution, use product-hunt-launch. For GTM motion design, use gtm-strategy.

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

When the user wants to launch on Product Hunt, prepare a PH submission, or plan launch day (hunter, first comment, timing, upvotes). Also use when the user mentions "Product Hunt," "launch on Product Hunt," "PH launch," "Product Hunt submission," "hunter," "Product of the Day," "upvotes," or "Product Hunt first comment." For multi-platform directory listings and paste-ready copy beyond PH, use directory-submission.

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

Plan and execute product launches and feature announcements: phased plans (alpha, beta, GA), channel strategy, Product Hunt playbooks, and post-launch momentum. Use when launching a new product or feature, or planning a Product Hunt launch.

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

Plan a product launch: pre-launch, hour-by-hour launch day, follow-up, owners, risks. "plan our product launch"

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

Builds a launch plan, launch story and press/distribution plan, then drafts the pitch emails and announcement copy. Use when you say 'launch plan', 'how do I get press', 'pitch a reporter', 'announce funding', 'go-to-market for a feature', 'Product Hunt', 'press release', 'launch messaging' or 'we shipped and nobody noticed'. Draws on 394 insights from 124 Lenny's Podcast guests, led by Emilie Gerber, Lulu Cheng Meservey and Jason Feifer.

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

Plan and execute technical product launches for developer tools, APIs, and technical products. Use this skill when technical PMMs need to "plan a launch", "create a launch strategy", "coordinate a product release", or "prepare for GA/beta launch".

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

Comprehensive product launch planning including GTM strategy, launch checklists, stakeholder communication, beta testing plans, and post-launch analysis. Execute successful product launches with coordinated teams.

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

产品营销 (PMM, Product Marketing) — 拥有「产品如何被定位 / 表达 / 发布 / 卖进市场」的从业者认知操作系统: 是产品 / 销售 / 市场 / 客户之间的连接组织, 负责把产品能力翻译成市场价值, 并把市场声音带回产品。覆盖 (a) 定位与差异化 (April Dunford 「刻意选择语境」框架 + 竞争性替代方案 + 卖价值不卖功能 + 选择「让你优势成立的市场参照系」, 对照 Ries & Trout 经典「定位是占领心智」), (b) 信息传递与叙事 (messaging 层级 / 信息屋 + 价值主张 + 收益导向 vs 战略叙事「换框架」Andy Raskin + 表达清晰度 Emma Stratton / Punchy + 初创 homepage 定位 FletchPMM), (c) 进入市场 (GTM) 策略与产品发布 (发布分级 T1/T2/T3 + 发布流程与跨职能编排 + GTM 打法 PLG vs SLG vs 混合 + 滩头细分选择), (d) 市场与竞争情报 (竞品分析 + battlecard 战卡 + 输赢分析 win/loss + 竞争赋能 Klue/Crayon/Clozd), (e) 买家与客户研究 (ICP 理想客户画像 + 买家 / 用户 persona + Jobs-to-be-Done 任务理论 Christensen/Moesta/Ulwick ODI + 客户之声 VoC + 用真实买家测信息 Wynter/Peep Laja), (f) 销售赋能 (战卡 + pitch / 销售 deck + 一页纸 + demo 叙事 + 异议处理 + 销售培训 + 内容采用率 — 你的产出只值销售实际用到的那部分), (g) 定价与打包 (价值定价 + 打包分层 + 《Monetizing Innovation》Ramanujam/Simon-Kucher + PLG 定价 — 常与产品 / 财务共担), (h) 细分与品类 (市场细分 + TAM/SAM/SOM + 技术采用生命周期与跨越鸿沟 Geoffrey Moore + 品类设计与叙事 Play Bigger / Christopher Lochhead — 稀有且昂贵, 不是默认选项), (i) 需求生成与内容协同 (campaign 信息 + 思想领导力 + 漏斗内容 TOFU/MOFU/BOFU + ABM 基于客户营销), (j) 分析师与影响者关系 (Gartner 魔力象限 + Forrester Wave + 分析师 briefing — To B 场景, 对 pay-to-play 影响诚实标注), (k) 客户营销与倡导 (参考客户 + case study + 评测站 G2/TrustRadius/Capterra 运营 + 社区), (l) PMM 运营与度量 (影响管道 + 赢率 + 发布采用率 + 信息穿透率 + 角色汇报线「向产品还是向市场」之争 + PMM 作为战略职能 vs 接单工具人陷阱); 跨 B2B SaaS (该学科重心) / B2C 消费 / 开发者 PLG / 平台产品。不含 产品管理 (PM 造产品 / 拥有 roadmap, PMM 拥有市场 — 相邻且极易混淆) / 增长 / 效果营销 / 付费投放 (平行学科) / 品牌 / 企业传播 / 公关为终点 / 需求生成为终点 (PMM 与之协同但不等同) / 平面设计 /「做 slide 和周边的团队」(PMM 抗争的接单工具人窄化) / 泛泛「市场营销」。 (Product Marketing (PMM) — the cognitive operating system of practitioners who own how a product is positioned, messaged, launched, and sold into a market: the connective tissue between product, sales, marketing, and customers, responsible for translating product capability into market value and bringing the voice of the market back into product. Covers (a) positioning & differentiation (April Dunford's deliberate-context framing, competitive alternatives, value-not-features, framing the market in which your strengths matter — vs Ries & Trout classic perception-in-the-mind positioning), (b) messaging & narrative (messaging hierarchy / house, value proposition, benefit-led vs strategic-narrative / change-the-frame messaging Andy Raskin, clarity craft Emma Stratton/Punchy, homepage & startup positioning FletchPMM), (c) go-to-market (GTM) strategy & product launches (launch tiers T1/T2/T3, launch process & cross-functional orchestration, GTM motion PLG vs SLG vs hybrid, beachhead segment selection), (d) market & competitive intelligence (competitive analysis, battlecards, win/loss analysis, competitive enablement Klue/Crayon/Clozd), (e) buyer & customer research (ICP ideal customer profile, buyer & user personas, Jobs-to-be-Done Christensen/Moesta/Ulwick ODI, voice of customer, message testing with real buyers Wynter/Peep Laja), (f) sales enablement (battlecards, pitch & sales decks, one-pagers, demo narratives, objection handling, sales training, content adoption — output is only as good as what sales actually uses), (g) pricing & packaging (value-based pricing, packaging & tiering, Monetizing Innovation Ramanujam/Simon-Kucher, PLG pricing — often shared with product/finance), (h) segmentation & category (market segmentation, TAM/SAM/SOM, technology adoption lifecycle & crossing the chasm Geoffrey Moore, category design & narrative Play Bigger / Christopher Lochhead — rare and expensive, not a default), (i) demand-gen & content partnership (campaign messaging, thought leadership, funnel content TOFU/MOFU/BOFU, ABM account-based marketing), (j) analyst & influencer relations (Gartner Magic Quadrant, Forrester Wave, analyst briefings — for B2B, with honest read on pay-to-play perception), (k) customer marketing & advocacy (references, case studies, reviews G2/TrustRadius/Capterra presence, community), (l) PMM operations & metrics (influenced pipeline, win rate, launch adoption, message pull-through, the role's reporting line product-vs-mark

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

Chooses how to launch subagents from Claude Code (the Agent tool, a Workflow script, or headless claude -p children) and runs a headless fan-out from one background command. Use for "fan this out to 50 agents", "run these tasks in parallel", "launch subagents for each file", "should I spawn agents or write a workflow", "batch this through Haiku", "run claude -p in parallel", "dispatch a task list without the launches eating my context", or before any launch of more than a handful of subagents, where the launching itself is the cost. Covers the parent-turn cost of each mechanism, concurrency ceilings, what context and tools each child gets, effort control, output contracts, a cost ledger, and resume after interruption.

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

🇺🇸 Hardware + SaaS GTM Playbook — End-to-end go-to-market for consumer hardware products with software subscription models. Covers crowdfunding engineering (Kickstarter/Indiegogo/Makuake), KOL matrix for physical products, hardware PMF validation metrics, device-as-funnel subscription design, localization entry timing, and community flywheel mechanics. Built from verified Plaud, Insta360, and DJI case data. 🇨🇳 硬件+软件订阅 GTM 实操手册 — 面向消费硬件产品的完整出海及增长打法。覆盖众筹超额工程（KS/IGG/Makuake）、硬件 KOL 矩阵策略、硬件 PMF 验证、设备即漏斗订阅设计、本地化进入时机判断、社区飞轮构建。基于 Plaud/Insta360/大疆真实案例数据撰写。 🇯🇵 ハードウェア＋SaaS GTMプレイブック — クラウドファンディング（Kickstarter/IGG/Makuake）を起点とした消費者向けハードウェア製品のGTM戦略。KOLマトリクス、PMF検証、デバイスをファネルとするサブスクリプション設計、ローカライゼーション進入タイミング、コミュニティフライホイールまで網羅。Plaud・Insta360・DJIの実例データに基づく。 🇰🇷 하드웨어+SaaS GTM 플레이북 — 크라우드펀딩(Kickstarter/IGG/Makuake) 기반 소비자 하드웨어 제품의 엔드투엔드 GTM 전략. KOL 매트릭스, PMF 검증, 디바이스-as-퍼널 구독 설계, 현지화 진입 타이밍, 커뮤니티 플라이휠 포함. Plaud·Insta360·DJI 실제 사례 데이터 기반. Triggers: "hardware GTM" | "crowdfunding strategy" | "hardware+SaaS" | "Kickstarter launch" | "hardware KOL" | "hardware PMF" | "device subscription" | "hardware product launch" | "consumer hardware growth" | "Makuake" | "众筹策略" | "硬件出海" | "硬件+订阅" | "硬件GTM" | "KS众筹" | "硬件PMF" | "设备订阅" | "硬件冷启动" | "ハードウェアGTM" | "クラファン" | "하드웨어 GTM" | "크라우드펀딩"

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

Run a full pre-launch quality gate before shipping — chains product review, growth audit, UX audit, security scan, and deployment preflight into a go/no-go launch decision. Stops on critical blockers. Use before v1 launch, beta release, major version rollout, or feature launch.

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

Use when taking a repo open source, or hardening one that already is. Run /oss-launch and it scans the repo (stack, existing files, git remote, secrets), asks only what it cannot infer, then generates a tailored OSS file collection (README, LICENSE, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY, CHANGELOG, .gitignore, .github/ issue + PR templates, CI/CD). Also covers launch (GitHub metadata, badges, Show HN, Reddit, YouTube), release cadence (SemVer + CHANGELOG), and demo-GIF generation. Triggers on "open source this", "OSS checklist", "prep for launch", "make this repo public", "add a license / contributing / security policy", "Show HN", "release workflow", "star growth", "get contributors".

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

Use when creating Product Hunt launch carousel images for developer tools, AI tools, open-source projects, GitHub launches, or technical products. Research comparable launches, inspect the project, extract verified proof points, then generate 4-5 launch-ready images with consistent branding, product surfaces, readable copy, and source-grounded claims.

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

Use when the user asks to "plan launch pricing", "design pricing tiers / packaging", or "set up a launch discount / early-bird offer"; produces a launch pricing and packaging plan — tier structure and naming, a value-to-price map aligned to the message house, a launch-offer ladder with a true deadline reason, beta / early-adopter pricing with a post-launch graduation path, and guarantee / refund terms — with every price claim and offer term submitted to memory/events/claims.ndjson. Not for the canonical offer / claim record — use offer-claims-registry; not for paid-newsletter subscription economics — use newsletter-monetization-planner; not for ad bidding — use bid-strategy-planner. 发布定价/梯度打包/早鸟优惠/保证设计

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

Use when the user asks to "plan an influencer campaign", "build a campaign blueprint", or "launch a product with creators"; produces campaign objectives, platform and influencer-tier strategy, content requirements, a phased timeline, budget allocation, and KPI targets. Not for writing individual creator briefs — use brief-generator; not for the overall product-launch plan (tiering, calendar, press, community day) — use launch-tier-planner, which hands this skill the creator lane. A launch request that does not mention creators routes to the launch discipline, not here. 达人营销策划/种草方案

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

Launch new products from idea to first customers. Use when launching products, finding early adopters, building launch week playbooks, diagnosing why adoption stalls, or learning that press coverage does not equal growth. Includes the three-layer diagnosis, the 2-week experiment cycle, and the launch that got 50K impressions and 12 signups.

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