[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6D7J2T8RKWDHP5AME14SP1B":3,"skill-same:01M6D7J2T8RKWDHP5AME14SP1B":127},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":6,"ownerHtmlUrl":63,"ownerBlogUrl":64,"ownerDescription":65,"updatedAt":66,"install":67,"resources":80},"01M6D7J2T8RKWDHP5AME14SP1B","launch-strategy",null,"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,' 'GTM plan,' 'launch checklist,' or 'launch momentum.' This skill covers phased launches, channel strategy, and ongoing launch momentum.","oabdelmaksoud\u002FSuperClaw","oabdelmaksoud","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F50699149?v=4","01M6D5CVVN778ZCDP1WHS816SP","Omar Abdelmaksoud","01M6D5CW1RHNSKCJR85GJACBFT",2,"MIT","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fmarketing-skill\u002Flaunch-strategy\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"launch","launch strategy","strategy","gtm","go","feature","product hunt","launch checklist","hunt","checklist","Market","use","marketing","access","plan","beta","product","announcement","release","update","2026-11-10 10:12:30",false,"---\nname: launch-strategy\ndescription: \"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,' 'GTM plan,' 'launch checklist,' or 'launch momentum.' This skill covers phased launches, channel strategy, and ongoing launch momentum.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-03-06\n---\n\n# Launch Strategy\n\nYou 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.\n\n## Before Starting\n\n**Check for product marketing context first:**\nIf `.claude\u002Fproduct-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\n---\n\n## Core Philosophy\n\nThe 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.\n\nA strong launch isn't about a single moment. It's about:\n- Getting your product into users' hands early\n- Learning from real feedback\n- Making a splash at every stage\n- Building momentum that compounds over time\n\n---\n\n## The ORB Framework\n\nStructure your launch marketing across three channel types. Everything should ultimately lead back to owned channels.\n\n### Owned Channels\nYou own the channel (though not the audience). Direct access without algorithms or platform rules.\n\n**Examples:**\n- Email list\n- Blog\n- Podcast\n- Branded community (Slack, Discord)\n- Website\u002Fproduct\n\n**Why they matter:**\n- Get more effective over time\n- No algorithm changes or pay-to-play\n- Direct relationship with audience\n- Compound value from content\n\n**Start with 1-2 based on audience:**\n- Industry lacks quality content → Start a blog\n- People want direct updates → Focus on email\n- Engagement matters → Build a community\n\n**Example - Superhuman:**\nBuilt 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.\n\n### Rented Channels\nPlatforms that provide visibility but you don't control. Algorithms shift, rules change, pay-to-play increases.\n\n**Examples:**\n- Social media (Twitter\u002FX, LinkedIn, Instagram)\n- App stores and marketplaces\n- YouTube\n- Reddit\n\n**How to use correctly:**\n- Pick 1-2 platforms where your audience is active\n- Use them to drive traffic to owned channels\n- Don't rely on them as your only strategy\n\n**Example - Notion:**\nHacked 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.\n\n**Platform-specific tactics:**\n- Twitter\u002FX: Threads that spark conversation → link to newsletter\n- LinkedIn: High-value posts → lead to gated content or email signup\n- Marketplaces (Shopify, Slack): Optimize listing → drive to site for more\n\nRented channels give speed, not stability. Capture momentum by bringing users into your owned ecosystem.\n\n### Borrowed Channels\nTap into someone else's audience to shortcut the hardest part—getting noticed.\n\n**Examples:**\n- Guest content (blog posts, podcast interviews, newsletter features)\n- Collaborations (webinars, co-marketing, social takeovers)\n- Speaking engagements (conferences, panels, virtual summits)\n- Influencer partnerships\n\n**Be proactive, not passive:**\n1. List industry leaders your audience follows\n2. Pitch win-win collaborations\n3. Use tools like SparkToro or Listen Notes to find audience overlap\n4. Set up affiliate\u002Freferral incentives\n\n**Example - TRMNL:**\nSent 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.\n\nBorrowed channels give instant credibility, but only work if you convert borrowed attention into owned relationships.\n\n---\n\n## Five-Phase Launch Approach\n\nLaunching isn't a one-day event. It's a phased process that builds momentum.\n\n### Phase 1: Internal Launch\nGather initial feedback and iron out major issues before going public.\n\n**Actions:**\n- Recruit early users one-on-one to test for free\n- Collect feedback on usability gaps and missing features\n- Ensure prototype is functional enough to demo (doesn't need to be production-ready)\n\n**Goal:** Validate core functionality with friendly users.\n\n### Phase 2: Alpha Launch\nPut the product in front of external users in a controlled way.\n\n**Actions:**\n- Create landing page with early access signup form\n- Announce the product exists\n- Invite users individually to start testing\n- MVP should be working in production (even if still evolving)\n\n**Goal:** First external validation and initial waitlist building.\n\n### Phase 3: Beta Launch\nScale up early access while generating external buzz.\n\n**Actions:**\n- Work through early access list (some free, some paid)\n- Start marketing with teasers about problems you solve\n- Recruit friends, investors, and influencers to test and share\n\n**Consider adding:**\n- Coming soon landing page or waitlist\n- \"Beta\" sticker in dashboard navigation\n- Email invites to early access list\n- Early access toggle in settings for experimental features\n\n**Goal:** Build buzz and refine product with broader feedback.\n\n### Phase 4: Early Access Launch\nShift from small-scale testing to controlled expansion.\n\n**Actions:**\n- Leak product details: screenshots, feature GIFs, demos\n- Gather quantitative usage data and qualitative feedback\n- Run user research with engaged users (incentivize with credits)\n- Optionally run product\u002Fmarket fit survey to refine messaging\n\n**Expansion options:**\n- Option A: Throttle invites in batches (5-10% at a time)\n- Option B: Invite all users at once under \"early access\" framing\n\n**Goal:** Validate at scale and prepare for full launch.\n\n### Phase 5: Full Launch\nOpen the floodgates.\n\n**Actions:**\n- Open self-serve signups\n- Start charging (if not already)\n- Announce general availability across all channels\n\n**Launch touchpoints:**\n- Customer emails\n- In-app popups and product tours\n- Website banner linking to launch assets\n- \"New\" sticker in dashboard navigation\n- Blog post announcement\n- Social posts across platforms\n- Product Hunt, BetaList, Hacker News, etc.\n\n**Goal:** Maximum visibility and conversion to paying users.\n\n---\n\n## Product Hunt Launch Strategy\n\nProduct Hunt can be powerful for reaching early adopters, but it's not magic—it requires preparation.\n\n### Pros\n- Exposure to tech-savvy early adopter audience\n- Credibility bump (especially if Product of the Day)\n- Potential PR coverage and backlinks\n\n### Cons\n- Very competitive to rank well\n- Short-lived traffic spikes\n- Requires significant pre-launch planning\n\n### How to Launch Successfully\n\n**Before launch day:**\n1. Build relationships with influential supporters, content hubs, and communities\n2. Optimize your listing: compelling tagline, polished visuals, short demo video\n3. Study successful launches to identify what worked\n4. Engage in relevant communities—provide value before pitching\n5. Prepare your team for all-day engagement\n\n**On launch day:**\n1. Treat it as an all-day event\n2. Respond to every comment in real-time\n3. Answer questions and spark discussions\n4. Encourage your existing audience to engage\n5. Direct traffic back to your site to capture signups\n\n**After launch day:**\n1. Follow up with everyone who engaged\n2. Convert Product Hunt traffic into owned relationships (email signups)\n3. Continue momentum with post-launch content\n\n### Case Studies\n\n**SavvyCal** (Scheduling tool):\n- Optimized landing page and onboarding before launch\n- Built relationships with productivity\u002FSaaS influencers in advance\n- Responded to every comment on launch day\n- Result: #2 Product of the Month\n\n**Reform** (Form builder):\n- Studied successful launches and applied insights\n- Crafted clear tagline, polished visuals, demo video\n- Engaged in communities before launch (provided value first)\n- Treated launch as all-day engagement event\n- Directed traffic to capture signups\n- Result: #1 Product of the Day\n\n---\n\n## Post-Launch Product Marketing\n\nYour launch isn't over when the announcement goes live. Now comes adoption and retention work.\n\n### Immediate Post-Launch Actions\n\n**Educate new users:**\nSet up automated onboarding email sequence introducing key features and use cases.\n\n**Reinforce the launch:**\nInclude announcement in your weekly\u002Fbiweekly\u002Fmonthly roundup email to catch people who missed it.\n\n**Differentiate against competitors:**\nPublish comparison pages highlighting why you're the obvious choice.\n\n**Update web pages:**\nAdd dedicated sections about the new feature\u002Fproduct across your site.\n\n**Offer hands-on preview:**\nCreate no-code interactive demo (using tools like Navattic) so visitors can explore before signing up.\n\n### Keep Momentum Going\nIt's easier to build on existing momentum than start from scratch. Every touchpoint reinforces the launch.\n\n---\n\n## Ongoing Launch Strategy\n\nDon't rely on a single launch event. Regular updates and feature rollouts sustain engagement.\n\n### How to Prioritize What to Announce\n\nUse this matrix to decide how much marketing each update deserves:\n\n**Major updates** (new features, product overhauls):\n- Full campaign across multiple channels\n- Blog post, email campaign, in-app messages, social media\n- Maximize exposure\n\n**Medium updates** (new integrations, UI enhancements):\n- Targeted announcement\n- Email to relevant segments, in-app banner\n- Don't need full fanfare\n\n**Minor updates** (bug fixes, small tweaks):\n- Changelog and release notes\n- Signal that product is improving\n- Don't dominate marketing\n\n### Announcement Tactics\n\n**Space out releases:**\nInstead of shipping everything at once, stagger announcements to maintain momentum.\n\n**Reuse high-performing tactics:**\nIf a previous announcement resonated, apply those insights to future updates.\n\n**Keep engaging:**\nContinue using email, social, and in-app messaging to highlight improvements.\n\n**Signal active development:**\nEven small changelog updates remind customers your product is evolving. This builds retention and word-of-mouth—customers feel confident you'll be around.\n\n---\n\n## Launch Checklist\n\n### Pre-Launch\n- [ ] Landing page with clear value proposition\n- [ ] Email capture \u002F waitlist signup\n- [ ] Early access list built\n- [ ] Owned channels established (email, blog, community)\n- [ ] Rented channel presence (social profiles optimized)\n- [ ] Borrowed channel opportunities identified (podcasts, influencers)\n- [ ] Product Hunt listing prepared (if using)\n- [ ] Launch assets created (screenshots, demo video, GIFs)\n- [ ] Onboarding flow ready\n- [ ] Analytics\u002Ftracking in place\n\n### Launch Day\n- [ ] Announcement email to list\n- [ ] Blog post published\n- [ ] Social posts scheduled and posted\n- [ ] Product Hunt listing live (if using)\n- [ ] In-app announcement for existing users\n- [ ] Website banner\u002Fnotification active\n- [ ] Team ready to engage and respond\n- [ ] Monitor for issues and feedback\n\n### Post-Launch\n- [ ] Onboarding email sequence active\n- [ ] Follow-up with engaged prospects\n- [ ] Roundup email includes announcement\n- [ ] Comparison pages published\n- [ ] Interactive demo created\n- [ ] Gather and act on feedback\n- [ ] Plan next launch moment\n\n---\n\n## Task-Specific Questions\n\n1. What are you launching? (New product, major feature, minor update)\n2. What's your current audience size and engagement?\n3. What owned channels do you have? (Email list size, blog traffic, community)\n4. What's your timeline for launch?\n5. Have you launched before? What worked\u002Fdidn't work?\n6. Are you considering Product Hunt? What's your preparation status?\n\n---\n\n## Proactive Triggers\n\nProactively offer launch planning when:\n\n1. **Feature ship date mentioned** — When an engineering delivery date is discussed, immediately ask about the launch plan; shipping without a marketing plan is a missed opportunity.\n2. **Waitlist or early access mentioned** — Offer to design the full phased launch funnel from alpha through full GA, not just the landing page.\n3. **Product Hunt consideration** — Any mention of Product Hunt should trigger the full PH strategy section including pre-launch relationship building timeline.\n4. **Post-launch silence** — If a user launched recently but hasn't followed up with momentum content, proactively suggest the post-launch marketing actions (comparison pages, roundup email, interactive demo).\n5. **Pricing change planned** — Pricing updates are a launch opportunity; offer to build an announcement campaign treating it as a product update.\n\n---\n\n## Output Artifacts\n\n| Artifact | Format | Description |\n|----------|--------|-------------|\n| Launch Plan | Markdown doc | Phase-by-phase plan with owners, dates, channels, and success metrics |\n| ORB Channel Map | Table | Owned\u002FRented\u002FBorrowed channel strategy with tactics per channel |\n| Launch Day Checklist | Checklist | Complete day-of execution checklist with time-boxed actions |\n| Product Hunt Brief | Markdown doc | Listing copy, asset specs, pre-launch timeline, engagement playbook |\n| Post-Launch Momentum Plan | Bulleted list | 30-day post-launch actions to sustain and compound the launch |\n\n---\n\n## Communication\n\nLaunch plans should be concrete, time-bound, and channel-specific — no vague \"post on social media\" recommendations. Every output should specify who does what and when. Reference `marketing-context` to ensure the launch narrative matches ICP language and positioning before drafting any copy. Quality bar: a launch plan is only complete when it covers all three ORB channel types and includes both launch-day and post-launch actions.\n\n---\n\n## Related Skills\n\n- **email-sequence** — USE for building the launch announcement and post-launch onboarding email sequences; NOT as a substitute for the full channel strategy.\n- **social-content** — USE for drafting the specific social posts and threads for launch day; NOT for channel selection strategy.\n- **paid-ads** — USE when the launch plan includes a paid amplification component; NOT for organic launch-only strategies.\n- **content-strategy** — USE when the launch requires a sustained content program (blog posts, case studies) in the weeks after; NOT for single-day launch execution.\n- **pricing-strategy** — USE when the launch involves a pricing change or new tier introduction; NOT for feature-only launches.\n- **marketing-context** — USE as foundation to align launch messaging with ICP and brand voice; always load first.\n","# Launch Strategy\n\nYou 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.\n\n## Before Starting\n\n**Check for product marketing context first:**\nIf `.claude\u002Fproduct-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\n---\n\n## Core Philosophy\n\nThe 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.\n\nA strong launch isn't about a single moment. It's about:\n- Getting your product into users' hands early\n- Learning from real feedback\n- Making a splash at every stage\n- Building momentum that compounds over time\n\n---\n\n## The ORB Framework\n\nStructure your launch marketing across three channel types. Everything should ultimately lead back to owned channels.\n\n### Owned Channels\nYou own the channel (though not the audience). Direct access without algorithms or platform rules.\n\n**Examples:**\n- Email list\n- Blog\n- Podcast\n- Branded community (Slack, Discord)\n- Website\u002Fproduct\n\n**Why they matter:**\n- Get more effective over time\n- No algorithm changes or pay-to-play\n- Direct relationship with audience\n- Compound value from content\n\n**Start with 1-2 based on audience:**\n- Industry lacks quality content → Start a blog\n- People want direct updates → Focus on email\n- Engagement matters → Build a community\n\n**Example - Superhuman:**\nBuilt 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.\n\n### Rented Channels\nPlatforms that provide visibility but you don't control. Algorithms shift, rules change, pay-to-play increases.\n\n**Examples:**\n- Social media (Twitter\u002FX, LinkedIn, Instagram)\n- App stores and marketplaces\n- YouTube\n- Reddit\n\n**How to use correctly:**\n- Pick 1-2 platforms where your audience is active\n- Use them to drive traffic to owned channels\n- Don't rely on them as your only strategy\n\n**Example - Notion:**\nHacked 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.\n\n**Platform-specific tactics:**\n- Twitter\u002FX: Threads that spark conversation → link to newsletter\n- LinkedIn: High-value posts → lead to gated content or email signup\n- Marketplaces (Shopify, Slack): Optimize listing → drive to site for more\n\nRented channels give speed, not stability. Capture momentum by bringing users into your owned ecosystem.\n\n### Borrowed Channels\nTap into someone else's audience to shortcut the hardest part—getting noticed.\n\n**Examples:**\n- Guest content (blog posts, podcast interviews, newsletter features)\n- Collaborations (webinars, co-marketing, social takeovers)\n- Speaking engagements (conferences, panels, virtual summits)\n- Influencer partnerships\n\n**Be proactive, not passive:**\n1. List industry leaders your audience follows\n2. Pitch win-win collaborations\n3. Use tools like SparkToro or Listen Notes to find audience overlap\n4. Set up affiliate\u002Freferral incentives\n\n**Example - TRMNL:**\nSent 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.\n\nBorrowed channels give instant credibility, but only work if you convert borrowed attention into owned relationships.\n\n---\n\n## Five-Phase Launch Approach\n\nLaunching isn't a one-day event. It's a phased process that builds momentum.\n\n### Phase 1: Internal Launch\nGather initial feedback and iron out major issues before going public.\n\n**Actions:**\n- Recruit early users one-on-one to test for free\n- Collect feedback on usability gaps and missing features\n- Ensure prototype is functional enough to demo (doesn't need to be production-ready)\n\n**Goal:** Validate core functionality with friendly users.\n\n### Phase 2: Alpha Launch\nPut the product in front of external users in a controlled way.\n\n**Actions:**\n- Create landing page with early access signup form\n- Announce the product exists\n- Invite users individually to start testing\n- MVP should be working in production (even if still evolving)\n\n**Goal:** First external validation and initial waitlist building.\n\n### Phase 3: Beta Launch\nScale up early access while generating external buzz.\n\n**Actions:**\n- Work through early access list (some free, some paid)\n- Start marketing with teasers about problems you solve\n- Recruit friends, investors, and influencers to test and share\n\n**Consider adding:**\n- Coming soon landing page or waitlist\n- \"Beta\" sticker in dashboard navigation\n- Email invites to early access list\n- Early access toggle in settings for experimental features\n\n**Goal:** Build buzz and refine product with broader feedback.\n\n### Phase 4: Early Access Launch\nShift from small-scale testing to controlled expansion.\n\n**Actions:**\n- Leak product details: screenshots, feature GIFs, demos\n- Gather quantitative usage data and qualitative feedback\n- Run user research with engaged users (incentivize with credits)\n- Optionally run product\u002Fmarket fit survey to refine messaging\n\n**Expansion options:**\n- Option A: Throttle invites in batches (5-10% at a time)\n- Option B: Invite all users at once under \"early access\" framing\n\n**Goal:** Validate at scale and prepare for full launch.\n\n### Phase 5: Full Launch\nOpen the floodgates.\n\n**Actions:**\n- Open self-serve signups\n- Start charging (if not already)\n- Announce general availability across all channels\n\n**Launch touchpoints:**\n- Customer emails\n- In-app popups and product tours\n- Website banner linking to launch assets\n- \"New\" sticker in dashboard navigation\n- Blog post announcement\n- Social posts across platforms\n- Product Hunt, BetaList, Hacker News, etc.\n\n**Goal:** Maximum visibility and conversion to paying users.\n\n---\n\n## Product Hunt Launch Strategy\n\nProduct Hunt can be powerful for reaching early adopters, but it's not magic—it requires preparation.\n\n### Pros\n- Exposure to tech-savvy early adopter audience\n- Credibility bump (especially if Product of the Day)\n- Potential PR coverage and backlinks\n\n### Cons\n- Very competitive to rank well\n- Short-lived traffic spikes\n- Requires significant pre-launch planning\n\n### How to Launch Successfully\n\n**Before launch day:**\n1. Build relationships with influential supporters, content hubs, and communities\n2. Optimize your listing: compelling tagline, polished visuals, short demo video\n3. Study successful launches to identify what worked\n4. Engage in relevant communities—provide value before pitching\n5. Prepare your team for all-day engagement\n\n**On launch day:**\n1. Treat it as an all-day event\n2. Respond to every comment in real-time\n3. Answer questions and spark discussions\n4. Encourage your existing audience to engage\n5. Direct traffic back to your site to capture signups\n\n**After launch day:**\n1. Follow up with everyone who engaged\n2. Convert Product Hunt traffic into owned relationships (email signups)\n3. Continue momentum with post-launch content\n\n### Case Studies\n\n**SavvyCal** (Scheduling tool):\n- Optimized landing page and onboarding before launch\n- Built relationships with productivity\u002FSaaS influencers in advance\n- Responded to every comment on launch day\n- Result: #2 Product of the Month\n\n**Reform** (Form builder):\n- Studied successful launches and applied insights\n- Crafted clear tagline, polished visuals, demo video\n- Engaged in communities before launch (provided value first)\n- Treated launch as all-day engagement event\n- Directed traffic to capture signups\n- Result: #1 Product of the Day\n\n---\n\n## Post-Launch Product Marketing\n\nYour launch isn't over when the announcement goes live. Now comes adoption and retention work.\n\n### Immediate Post-Launch Actions\n\n**Educate new users:**\nSet up automated onboarding email sequence introducing key features and use cases.\n\n**Reinforce the launch:**\nInclude announcement in your weekly\u002Fbiweekly\u002Fmonthly roundup email to catch people who missed it.\n\n**Differentiate against competitors:**\nPublish comparison pages highlighting why you're the obvious choice.\n\n**Update web pages:**\nAdd dedicated sections about the new feature\u002Fproduct across your site.\n\n**Offer hands-on preview:**\nCreate no-code interactive demo (using tools like Navattic) so visitors can explore before signing up.\n\n### Keep Momentum Going\nIt's easier to build on existing momentum than start from scratch. Every touchpoint reinforces the launch.\n\n---\n\n## Ongoing Launch Strategy\n\nDon't rely on a single launch event. Regular updates and feature rollouts sustain engagement.\n\n### How to Prioritize What to Announce\n\nUse this matrix to decide how much marketing each update deserves:\n\n**Major updates** (new features, product overhauls):\n- Full campaign across multiple channels\n- Blog post, email campaign, in-app messages, social media\n- Maximize exposure\n\n**Medium updates** (new integrations, UI enhancements):\n- Targeted announcement\n- Email to relevant segments, in-app banner\n- Don't need full fanfare\n\n**Minor updates** (bug fixes, small tweaks):\n- Changelog and release notes\n- Signal that product is improving\n- Don't dominate marketing\n\n### Announcement Tactics\n\n**Space out releases:**\nInstead of shipping everything at once, stagger announcements to maintain momentum.\n\n**Reuse high-performing tactics:**\nIf a previous announcement resonated, apply those insights to future updates.\n\n**Keep engaging:**\nContinue using email, social, and in-app messaging to highlight improvements.\n\n**Signal active development:**\nEven small changelog updates remind customers your product is evolving. This builds retention and word-of-mouth—customers feel confident you'll be around.\n\n---\n\n## Launch Checklist\n\n### Pre-Launch\n- [ ] Landing page with clear value proposition\n- [ ] Email capture \u002F waitlist signup\n- [ ] Early access list built\n- [ ] Owned channels established (email, blog, community)\n- [ ] Rented channel presence (social profiles optimized)\n- [ ] Borrowed channel opportunities identified (podcasts, influencers)\n- [ ] Product Hunt listing prepared (if using)\n- [ ] Launch assets created (screenshots, demo video, GIFs)\n- [ ] Onboarding flow ready\n- [ ] Analytics\u002Ftracking in place\n\n### Launch Day\n- [ ] Announcement email to list\n- [ ] Blog post published\n- [ ] Social posts scheduled and posted\n- [ ] Product Hunt listing live (if using)\n- [ ] In-app announcement for existing users\n- [ ] Website banner\u002Fnotification active\n- [ ] Team ready to engage and respond\n- [ ] Monitor for issues and feedback\n\n### Post-Launch\n- [ ] Onboarding email sequence active\n- [ ] Follow-up with engaged prospects\n- [ ] Roundup email includes announcement\n- [ ] Comparison pages published\n- [ ] Interactive demo created\n- [ ] Gather and act on feedback\n- [ ] Plan next launch moment\n\n---\n\n## Task-Specific Questions\n\n1. What are you launching? (New product, major feature, minor update)\n2. What's your current audience size and engagement?\n3. What owned channels do you have? (Email list size, blog traffic, community)\n4. What's your timeline for launch?\n5. Have you launched before? What worked\u002Fdidn't work?\n6. Are you considering Product Hunt? What's your preparation status?\n\n---\n\n## Proactive Triggers\n\nProactively offer launch planning when:\n\n1. **Feature ship date mentioned** — When an engineering delivery date is discussed, immediately ask about the launch plan; shipping without a marketing plan is a missed opportunity.\n2. **Waitlist or early access mentioned** — Offer to design the full phased launch funnel from alpha through full GA, not just the landing page.\n3. **Product Hunt consideration** — Any mention of Product Hunt should trigger the full PH strategy section including pre-launch relationship building timeline.\n4. **Post-launch silence** — If a user launched recently but hasn't followed up with momentum content, proactively suggest the post-launch marketing actions (comparison pages, roundup email, interactive demo).\n5. **Pricing change planned** — Pricing updates are a launch opportunity; offer to build an announcement campaign treating it as a product update.\n\n---\n\n## Output Artifacts\n\n| Artifact | Format | Description |\n|----------|--------|-------------|\n| Launch Plan | Markdown doc | Phase-by-phase plan with owners, dates, channels, and success metrics |\n| ORB Channel Map | Table | Owned\u002FRented\u002FBorrowed channel strategy with tactics per channel |\n| Launch Day Checklist | Checklist | Complete day-of execution checklist with time-boxed actions |\n| Product Hunt Brief | Markdown doc | Listing copy, asset specs, pre-launch timeline, engagement playbook |\n| Post-Launch Momentum Plan | Bulleted list | 30-day post-launch actions to sustain and compound the launch |\n\n---\n\n## Communication\n\nLaunch plans should be concrete, time-bound, and channel-specific — no vague \"post on social media\" recommendations. Every output should specify who does what and when. Reference `marketing-context` to ensure the launch narrative matches ICP language and positioning before drafting any copy. Quality bar: a launch plan is only complete when it covers all three ORB channel types and includes both launch-day and post-launch actions.\n\n---\n\n## Related Skills\n\n- **email-sequence** — USE for building the launch announcement and post-launch onboarding email sequences; NOT as a substitute for the full channel strategy.\n- **social-content** — USE for drafting the specific social posts and threads for launch day; NOT for channel selection strategy.\n- **paid-ads** — USE when the launch plan includes a paid amplification component; NOT for organic launch-only strategies.\n- **content-strategy** — USE when the launch requires a sustained content program (blog posts, case studies) in the weeks after; NOT for single-day launch execution.\n- **pricing-strategy** — USE when the launch involves a pricing change or new tier introduction; NOT for feature-only launches.\n- **marketing-context** — USE as foundation to align launch messaging with ICP and brand voice; always load first.\n",{"name":5,"license":15,"metadata":54,"description":7},{"author":55,"updated":56,"version":57,"category":41},"Alireza Rezvani",1772755200000,"1.0.0","main","7b610356e36623652299fa2acb477ff821b1d920","upstream-sync\u002Fwork\u002Fclaude-skills\u002Fmarketing-skill\u002Flaunch-strategy",0,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fo-abdelmaksoud\u002F","Full-Stack Engineer | AI Systems Architect | Building autonomous multi-agent systems","2026-03-08 21:12:53",{"source":8,"skillName":5,"commands":68,"prompt":78,"zipAvailable":79},[69,72,75],{"tool":70,"command":71},"npx","npx skills add oabdelmaksoud\u002FSuperClaw --skill launch-strategy",{"tool":73,"command":74},"bunx","bunx skills add oabdelmaksoud\u002FSuperClaw --skill launch-strategy",{"tool":76,"command":77},"pnpm","pnpm dlx skills add oabdelmaksoud\u002FSuperClaw --skill launch-strategy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fmarketing-skill\u002Flaunch-strategy\u002FSKILL.md",true,[81,87,93,97,101,105,111,115,119,123],{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"LICENSE.txt","LICENSE","许可证",11357,"https:\u002F\u002Fgithub.com\u002Fsuvab4gh\u002Fperpguard\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmcp-builder\u002FLICENSE.txt",{"path":88,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":92},"reference\u002Fevaluation.md","REFERENCE","参考文档",21663,"https:\u002F\u002Fgithub.com\u002Fsuvab4gh\u002Fperpguard\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmcp-builder\u002Freference\u002Fevaluation.md",{"path":94,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":95,"sourceHtmlUrl":96},"reference\u002Fmcp_best_practices.md",7330,"https:\u002F\u002Fgithub.com\u002Fsuvab4gh\u002Fperpguard\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmcp-builder\u002Freference\u002Fmcp_best_practices.md",{"path":98,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":99,"sourceHtmlUrl":100},"reference\u002Fnode_mcp_server.md",28550,"https:\u002F\u002Fgithub.com\u002Fsuvab4gh\u002Fperpguard\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmcp-builder\u002Freference\u002Fnode_mcp_server.md",{"path":102,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":103,"sourceHtmlUrl":104},"reference\u002Fpython_mcp_server.md",25099,"https:\u002F\u002Fgithub.com\u002Fsuvab4gh\u002Fperpguard\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmcp-builder\u002Freference\u002Fpython_mcp_server.md",{"path":106,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":109,"sourceHtmlUrl":110},"scripts\u002Fconnections.py","SCRIPT","脚本",4875,"https:\u002F\u002Fgithub.com\u002Fsuvab4gh\u002Fperpguard\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmcp-builder\u002Fscripts\u002Fconnections.py",{"path":112,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":113,"sourceHtmlUrl":114},"scripts\u002Fevaluation.py",12579,"https:\u002F\u002Fgithub.com\u002Fsuvab4gh\u002Fperpguard\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmcp-builder\u002Fscripts\u002Fevaluation.py",{"path":116,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":117,"sourceHtmlUrl":118},"scripts\u002Fexample_evaluation.xml",1194,"https:\u002F\u002Fgithub.com\u002Fsuvab4gh\u002Fperpguard\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmcp-builder\u002Fscripts\u002Fexample_evaluation.xml",{"path":120,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":121,"sourceHtmlUrl":122},"scripts\u002Flaunch_readiness_scorer.py",12292,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fmarketing-skill\u002Flaunch-strategy\u002Fscripts\u002Flaunch_readiness_scorer.py",{"path":124,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":125,"sourceHtmlUrl":126},"scripts\u002Frequirements.txt",29,"https:\u002F\u002Fgithub.com\u002Fsuvab4gh\u002Fperpguard\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmcp-builder\u002Fscripts\u002Frequirements.txt",[128,147,161,189,215,234],{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":137,"publishedAt":49},"01M6D88QCPTBZVCRED0NZ1Y8K8","visa-doc-translate","Translate visa application documents (images) to English and create a bilingual PDF with original and translation","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Fvisa-doc-translate\u002FSKILL.md",[134],{"categoryNo":135,"categoryName":136,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",[138,139,140,141,142,143,144,145,146],"translate","doc","visa doc translate","translation","application","create","images","PDF","documents",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":49},"01M6D88NBM95T3TFM50CYYAP65","verification-loop","A comprehensive verification system for Claude Code sessions.","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[154,155,156,157,158,159,160],"verification","loop","verification loop","sessions","code","claude code sessions","system",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":176,"publishedAt":49},"01M6D88JFZ2P996GVRHJNSZSTM","tdd-workflow","Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Ftdd-workflow\u002FSKILL.md",[167,170,173],{"categoryNo":168,"categoryName":169,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":171,"categoryName":172,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":174,"categoryName":175,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师",[177,178,179,180,181,182,158,183,40,184,185,186,187,188],"tdd","workflow","tdd workflow","e2e tests","e2e","integration","development","test","refactoring","coverage","tests","writing",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":195,"publishedAt":49},"01M6D88FTHRRSVJMXF2G7MQAK3","swiftui-patterns","SwiftUI architecture patterns, state management with @Observable, view composition, navigation, performance optimization, and modern iOS\u002FmacOS UI best practices.","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Fswiftui-patterns\u002FSKILL.md",[],[196,197,198,199,200,201,202,203,204,205,206,207,208,209,210,211,212,213,214],"patterns","swiftui","swiftui patterns","architecture","macos","performance","state management","best practices","state","ui","Optimization","ios","architecture patterns","Composition","performance optimization","view","management","swiftui architecture","navigation",{"skillNo":216,"name":217,"nameZh":6,"description":218,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":219,"categories":220,"keywords":222,"publishedAt":49},"01M6D88D527QTQT9DKHTRFN6EA","swift-protocol-di-testing","Protocol-based dependency injection for testable Swift code — mock file system, network, and external APIs using focused protocols and Swift Testing.","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Fswift-protocol-di-testing\u002FSKILL.md",[221],{"categoryNo":168,"categoryName":169,"taxonomyType":21,"taxonomyTypeDesc":22},[223,224,225,226,158,227,228,229,230,160,231,232,233],"swift protocol di testing","protocol","swift","testing","protocols","file","network","injection","dependency","swift testing","dependency injection",{"skillNo":235,"name":236,"nameZh":6,"description":237,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":238,"categories":239,"keywords":240,"publishedAt":49},"01M6D88AJW8H2QNWSW5ZY82R43","swift-concurrency-6-2","Swift 6.2 Approachable Concurrency — single-threaded by default, @concurrent for explicit background offloading, isolated conformances for main actor types.","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Fswift-concurrency-6-2\u002FSKILL.md",[],[241,242,225,243,244,58],"concurrency","swift concurrency","swift concurrency 6 2","default"]