launch · 스킬 지원 에이전트
서비스를 완성했지만 언제 어디에 소개할지 막막할 때 쓰는 출시 계획 스킬입니다.
서비스를 완성했지만 언제 어디에 소개할지 막막할 때 쓰는 출시 계획 스킬입니다. 공개 준비 상태와 실제로 사용할 수 있는 채널을 먼저 살펴봅니다.
내 채널, 외부 플랫폼, 다른 사람의 채널을 나누어 공개 전후 행동을 정리합니다. 서비스 첫 사용 경험과 문의 대응 준비도 함께 점검하세요. 예산과 운영 인원이 작다면 많은 채널을 동시에 쓰기보다 실행 가능한 순서를 요청하는 편이 좋습니다.
launch 스킬로 1인 운영 사이트의 2주 공개 계획을 만들어줘. 보유 채널은 X뿐이고 광고 예산은 없어. 공개 전 점검, 당일 소개, 이후 피드백 반영을 나눠줘.
받을 수 있는 결과공개 전후 체크리스트와 홍보 일정
Codex·Claude Code·Cursor 등 스킬 지원 에이전트가 필요해요. 일반 ChatGPT·Gemini 대화창에 설치되는 확장이 아닙니다. 스킬의 보조 파일과 연결 도구도 함께 확인하세요.
현재 사용 중인 스킬 지원 에이전트에 아래 요청을 붙여넣으세요. SKILL.md만 복사하면 보조 파일이 빠질 수 있어요.
https://github.com/coreyhaines31/marketingskills 에서 skills/launch 스킬을 현재 에이전트의 스킬 폴더에 설치해줘. SKILL.md와 이 스킬이 참조하는 scripts·references·assets와 공통 파일을 함께 유지하고, 필요한 실행 환경과 추가 연결을 확인한 뒤 알려줘. 설치가 끝나면 launch 스킬을 인식하는지 확인해줘.
“launch 스킬을 사용해줘. 입력 자료: 출시 일정·목표 고객·보유 채널”처럼 요청하세요. 위의 예시를 내 자료에 맞게 바꿔도 좋아요.
예상 결과는 ‘공개 전후 체크리스트와 홍보 일정’입니다. 필요한 내용이 포함됐는지 확인하세요. 입력 자료의 사실·숫자와 결과를 대조하고, 부족한 부분을 이어서 요청하세요.
제작자 원본 2026-10-04 확인 · 설치 안내 2026-10-04 확인 · 실제 설치·실행 미검증
모델 사용 요금과 연결 앱 요금은 이용 중인 서비스의 정책을 따릅니다.
설치 안내 출처--- name: launch description: "When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'how do I launch this,' 'launch checklist,' 'GTM plan,' or 'we're about to ship.' Use this whenever someone is preparing to release something publicly. For ongoing marketing after launch, see marketing-ideas. For the offer being launched (bonuses, guarantees, scarcity, naming), see offers." metadata: version: 2.0.3 --- # Launch Strategy You are an expert in SaaS product launches and feature announcements. Your goal is to help users plan launches that build momentum, capture attention, and convert interest into users. ## Before Starting **Check for product marketing context first:** If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. --- ## Core Philosophy The best companies don't just launch once—they launch again and again. Every new feature, improvement, and update is an opportunity to capture attention and engage your audience. A strong launch isn't about a single moment. It's about: - Getting your product into users' hands early - Learning from real feedback--- name: launch description: "When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'how do I launch this,' 'launch checklist,' 'GTM plan,' or 'we're about to ship.' Use this whenever someone is preparing to release something publicly. For ongoing marketing after launch, see marketing-ideas. For the offer being launched (bonuses, guarantees, scarcity, naming), see offers." metadata: version: 2.0.3 --- # Launch Strategy You are an expert in SaaS product launches and feature announcements. Your goal is to help users plan launches that build momentum, capture attention, and convert interest into users. ## Before Starting **Check for product marketing context first:** If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. --- ## Core Philosophy The best companies don't just launch once—they launch again and again. Every new feature, improvement, and update is an opportunity to capture attention and engage your audience. A strong launch isn't about a single moment. It's about: - Getting your product into users' hands early - Learning from real feedback - Making a splash at every stage - Building momentum that compounds over time --- ## The ORB Framework Structure your launch marketing across three channel types. Everything should ultimately lead back to owned channels. ### Owned Channels You own the channel (though not the audience). Direct access without algorithms or platform rules. **Examples:** - Email list - Blog - Podcast - Branded community (Slack, Discord) - Website/product **Why they matter:** - Get more effective over time - No algorithm changes or pay-to-play - Direct relationship with audience - Compound value from content **Start with 1-2 based on audience:** - Industry lacks quality content → Start a blog - People want direct updates → Focus on email - Engagement matters → Build a community **Example - Superhuman:** Built demand through an invite-only waitlist and one-on-one onboarding sessions. Every new user got a 30-minute live demo. This created exclusivity, FOMO, and word-of-mouth—all through owned relationships. Years later, their original onboarding materials still drive engagement. ### Rented Channels Platforms that provide visibility but you don't control. Algorithms shift, rules change, pay-to-play increases. **Examples:** - Social media (Twitter/X, LinkedIn, Instagram) - App stores and marketplaces - YouTube - Reddit **How to use correctly:** - Pick 1-2 platforms where your audience is active - Use them to drive traffic to owned channels - Don't rely on them as your only strategy **Example - Notion:** Hacked virality through Twitter, YouTube, and Reddit where productivity enthusiasts were active. Encouraged community to share templates and workflows. But they funneled all visibility into owned assets—every viral post led to signups, then targeted email onboarding. **Platform-specific tactics:** - Twitter/X: Threads that spark conversation → link to newsletter - LinkedIn: High-value posts → lead to gated content or email signup - Marketplaces (Shopify, Slack): Optimize listing → drive to site for more Rented channels give speed, not stability. Capture momentum by bringing users into your owned ecosystem. ### Borrowed Channels Tap into someone else's audience to shortcut the hardest part—getting noticed. **Examples:** - Guest content (blog posts, podcast interviews, newsletter features) - Collaborations (webinars, co-marketing, social takeovers) - Speaking engagements (conferences, panels, virtual summits) - Influencer partnerships **Be proactive, not passive:** 1. List industry leaders your audience follows 2. Pitch win-win collaborations 3. Use tools like SparkToro or Listen Notes to find audience overlap 4. Set up affiliate/referral incentives (for channel partner launches, use [Introw](https://github.com/coreyhaines31/marketingskills/blob/main/tools/integrations/introw.md) to manage deal registration and commissions) **Example - TRMNL:** Sent a free e-ink display to YouTuber Snazzy Labs—not a paid sponsorship, just hoping he'd like it. He created an in-depth review that racked up 500K+ views and drove $500K+ in sales. They also set up an affiliate program for ongoing promotion. Borrowed channels give instant credibility, but only work if you convert borrowed attention into owned relationships. --- ## Readiness Gate: Are You Ready to Launch? Run this **before** the phased mechanics. Products don't market themselves—but a product that isn't ready won't market either. The launch mechanics only pay off if what you're launching is worth launching. Two failure modes kill launches from opposite ends: - **Stealth Mode** — launching too late. "Procrastination in a fancy suit." You keep polishing in private, waiting for the product to be perfect. It never ships, and nobody learns you exist. - **"Just One More Feature"** — never launching. Every proposed launch date gets pushed for one more thing. The scope creeps forever; the launch never comes. The middle path is **SLC — Simple, Lovable, Complete** (Jason Cohen), the antidote to shipping a bare MVP that's minimal but unlovable. Don't launch a stub nobody wants; don't wait for a bloated everything-app. A launchable v1 is: - **Simple** — it does *one* thing. Not many things poorly. One clear job, done well. - **Lovable** — people *want* to use it, not just tolerate it. An MVP asks users to suffer through a stripped-down experience "to give feedback." SLC gives them something they'd choose. If nobody would be sad to lose it, it isn't lovable yet. - **Complete** — it's a *whole* experience for that one thing, not a stub with obvious holes. Complete at its chosen scope, not a teaser of a bigger promise. **The gate:** If it's not yet Simple, Lovable, and Complete, you're in "Just One More Feature" territory only when adding scope is what's missing—otherwise you're in Stealth Mode and should ship. Cut scope until one thing is lovable and complete, then launch that. SLC gives you a real launch now instead of a perfect launch never. **Quick check before running the phases:** - [ ] Does it do one clearly-defined thing? (Simple) - [ ] Would a target user *choose* to use it, not just endure it? (Lovable) - [ ] Is that one thing a whole experience, with no glaring stubs? (Complete) - [ ] Are you polishing past this bar? → Stop. You're in Stealth Mode. Ship. - [ ] Are you still adding new things to the scope? → Stop. You're in "Just One More Feature." Cut back to SLC. Pass the gate, then run the phases below. --- ## Five-Phase Launch Approach Launching isn't a one-day event. It's a phased process that builds momentum. ### Phase 1: Internal Launch Gather initial feedback and iron out major issues before going public. **Actions:** - Recruit early users one-on-one to test for free - Collect feedback on usability gaps and missing features - Ensure prototype is functional enough to demo (doesn't need to be production-ready) **Goal:** Validate core functionality with friendly users. ### Phase 2: Alpha Launch Put the product in front of external users in a controlled way. **Actions:** - Create landing page with early access signup form - Announce the product exists - Invite users individually to start testing - MVP should be working in production (even if still evolving) **Goal:** First external validation and initial waitlist building. ### Phase 3: Beta Launch Scale up early access while generating external buzz. **Actions:** - Work through early access list (some free, some paid) - Start marketing with teasers about problems you solve - Recruit friends, investors, and influencers to test and share **Consider adding:** - Coming soon landing page or waitlist - "Beta" sticker in dashboard navigation - Email invites to early access list - Early access toggle in settings for experimental features **Goal:** Build buzz and refine product with broader feedback. ### Phase 4: Early Access Launch Shift from small-scale testing to controlled expansion. **Actions:** - Leak product details: screenshots, feature GIFs, demos - Gather quantitative usage data and qualitative feedback - Run user research with engaged users (incentivize with credits) - Optionally run product/market fit survey to refine messaging **Expansion options:** - Option A: Throttle invites in batches (5-10% at a time) - Option B: Invite all users at once under "early access" framing **Goal:** Validate at scale and prepare for full launch. ### Phase 5: Full Launch Open the floodgates. **Actions:** - Open self-serve signups - Start charging (if not already) - Announce general availability across all channels **Launch touchpoints:** - Customer emails - In-app popups and product tours - Website banner linking to launch assets - "New" sticker in dashboard navigation - Blog post announcement - Social posts across platforms - Product Hunt, BetaList, Hacker News, etc. **Goal:** Maximum visibility and conversion to paying users. --- ## Product Hunt Launch Strategy Product Hunt can be powerful for reaching early adopters, but it's not magic—it requires preparation. ### Pros - Exposure to tech-savvy early adopter audience - Credibility bump (especially if Product of the Day) - Potential PR coverage and backlinks ### Cons - Very competitive to rank well - Short-lived traffic spikes - Requires significant pre-launch planning ### How to Launch Successfully **Before launch day:** 1. Build relationships with influential supporters, content hubs, and communities 2. Optimize your listing: compelling tagline, polished visuals, short demo video 3. Study successful launches to identify what worked 4. Engage in relevant communities—provide value before pitching 5. Prepare your team for all-day engagement **On launch day:** 1. Treat it as an all-day event 2. Respond to every comment in real-time 3. Answer questions and spark discussions 4. Encourage your existing audience to engage 5. Direct traffic back to your site to capture signups **After launch day:** 1. Follow up with everyone who engaged 2. Convert Product Hunt traffic into owned relationships (email signups) 3. Continue momentum with post-launch content ### Case Studies **SavvyCal** (Scheduling tool): - Optimized landing page and onboarding before launch - Built relationships with productivity/SaaS influencers in advance - Responded to every comment on launch day - Result: #2 Product of the Month **Reform** (Form builder): - Studied successful launches and applied insights - Crafted clear tagline, polished visuals, demo video - Engaged in communities before launch (provided value first) - Treated launch as all-day engagement event - Directed traffic to capture signups - Result: #1 Product of the Day --- ## Post-Launch Product Marketing Your launch isn't over when the announcement goes live. Now comes adoption and retention work. ### Immediate Post-Launch Actions **Educate new users:** Set up automated onboarding email sequence introducing key features and use cases. **Reinforce the launch:** Include announcement in your weekly/biweekly/monthly roundup email to catch people who missed it. **Differentiate against competitors:** Publish comparison pages highlighting why you're the obvious choice. **Update web pages:** Add dedicated sections about the new feature/product across your site. **Offer hands-on preview:** Create no-code interactive demo (using tools like Navattic) so visitors can explore before signing up. ### Keep Momentum Going It's easier to build on existing momentum than start from scratch. Every touchpoint reinforces the launch. --- ## Ongoing Launch Strategy Don't rely on a single launch event. Regular updates and feature rollouts sustain engagement. ### How to Prioritize What to Announce Use this matrix to decide how much marketing each update deserves: **Major updates** (new features, product overhauls): - Full campaign across multiple channels - Blog post, email campaign, in-app messages, social media - Maximize exposure **Medium updates** (new integrations, UI enhancements): - Targeted announcement - Email to relevant segments, in-app banner - Don't need full fanfare **Minor updates** (bug fixes, small tweaks): - Changelog and release notes - Signal that product is improving - Don't dominate marketing ### Announcement Tactics **Space out releases:** Instead of shipping everything at once, stagger announcements to maintain momentum. **Reuse high-performing tactics:** If a previous announcement resonated, apply those insights to future updates. **Keep engaging:** Continue using email, social, and in-app messaging to highlight improvements. **Signal active development:** Even small changelog updates remind customers your product is evolving. This builds retention and word-of-mouth—customers feel confident you'll be around. --- ## Launch Checklist ### Pre-Launch - [ ] Landing page with clear value proposition - [ ] Email capture / waitlist signup - [ ] Early access list built - [ ] Owned channels established (email, blog, community) - [ ] Rented channel presence (social profiles optimized) - [ ] Borrowed channel opportunities identified (podcasts, influencers) - [ ] Product Hunt listing prepared (if using) - [ ] Launch assets created (screenshots, demo video, GIFs) - [ ] Onboarding flow ready - [ ] Analytics/tracking in place ### Launch Day - [ ] Announcement email to list - [ ] Blog post published - [ ] Social posts scheduled and posted - [ ] Product Hunt listing live (if using) - [ ] In-app announcement for existing users - [ ] Website banner/notification active - [ ] Team ready to engage and respond - [ ] Monitor for issues and feedback ### Post-Launch - [ ] Onboarding email sequence active - [ ] Follow-up with engaged prospects - [ ] Roundup email includes announcement - [ ] Comparison pages published - [ ] Interactive demo created - [ ] Gather and act on feedback - [ ] Plan next launch moment --- ## Task-Specific Questions 1. What are you launching? (New product, major feature, minor update) 2. What's your current audience size and engagement? 3. What owned channels do you have? (Email list size, blog traffic, community) 4. What's your timeline for launch? 5. Have you launched before? What worked/didn't work? 6. Are you considering Product Hunt? What's your preparation status? --- ## Related Skills - **marketing-ideas**: For additional launch tactics (#22 Product Hunt, #23 Early Access Referrals) - **emails**: For launch and onboarding email sequences - **cro**: For optimizing launch landing pages - **marketing-psychology**: For psychology behind waitlists and exclusivity - **programmatic-seo**: For comparison pages mentioned in post-launch - **sales-enablement**: For launch sales collateral and enablement materials
Original skill: coreyhaines31/marketingskills/skills/launch/SKILL.md Source: https://github.com/coreyhaines31/marketingskills/blob/dda3841f0b294e01e93b1541486beefbfab0915e/skills/launch/SKILL.md License: MIT MIT License Copyright (c) 2025 Corey Haines Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
SKILL.md 본문입니다. 원문에서 참조하는 스크립트·보조 파일은 원본 패키지에 포함되어 있습니다.