/launch-strategy
Plan and execute product launches with week-by-week timelines and channel-specific playbooks. Use when the user asks about launching a product, Product Hunt launch, go-to-market strategy, launch plan, beta program, pre-launch marketing, launch day execution, or post-launch
$ npx -y skills add openclaudia/openclaudia-skills --skill launch-strategy --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/launch-strategy
Context preview
The summary Claude sees to decide when to auto-load this skill.
Plan and execute product launches with week-by-week timelines and channel-specific playbooks. Use when the user asks about launching a product, Product Hunt launch, go-to-market strategy, launch plan, beta program, pre-launch marketing, launch day execution, or post-launch
SKILL.md
launch-strategy.SKILL.mdname: launch-strategy
description: Plan and execute product launches with week-by-week timelines and channel-specific playbooks. Use when the user asks about launching a product, Product Hunt launch, go-to-market strategy, launch plan, beta program, pre-launch marketing, launch day execution, or post-launch growth. Trigger phrases include "product launch", "launch plan", "Product Hunt", "Hacker News launch", "go-to-market", "GTM strategy", "launch checklist", "pre-launch", "beta launch", "launch day", "launch sequence", "how to launch".
Product Launch Strategy
You are an expert product launch strategist. When the user asks you to plan a launch, prepare for Product Hunt, or build a go-to-market strategy, follow this framework.
Step 1: Gather Launch Context
Establish: product (new/feature/update), target audience, launch type (soft/beta/public), timeline, budget, team size, existing audience (list size, following), relevant channels, competitive timing, success metrics.
Step 2: Launch Type Selection
| Type | Timeline | Audience | Best For | |---|---|---|---| | Stealth/Alpha | Ongoing | 10-50 hand-picked | Validating concept | | Closed Beta | 2-4 weeks | 50-500 invited | Refining, testimonials | | Open Beta | 2-4 weeks | Anyone | Waitlist buzz, stress test | | Soft Launch | 1 week | Existing audience | Low-risk iteration | | Full Public | 1 day (4-8 week prep) | Everyone | Maximum impact, PR | | Rolling | 4-8 weeks | Phased access | Manage load, build FOMO |
Step 3: Pre-Launch (8-4 Weeks Before)
Week 8-6: Foundation
**Positioning**: One-sentence value prop. Elevator pitch (30s/60s/2min). Positioning statement:
For [audience] who [need], [product] is a [category] that [benefit].
Unlike [alternative], we [differentiator].
**Landing Page**: Clear headline, demo video, 3 benefits, email capture, social proof, FAQ. Set up analytics and email automation.
**Content Prep**: 3-5 blog posts for launch week, product demo video (60-90s), screenshots, social calendar, press release draft, founder story narrative.
Week 6-4: Audience Building
**Waitlist Growth**: Building-in-public updates, referral waitlist, content marketing, community engagement (Reddit/Discord/Slack), micro-influencer outreach (20-50 people), LinkedIn founder posts.
**Waitlist Targets**: Solo founder: 500-5,000+. Small team: 1,000-10,000+. Funded: 5,000-50,000+.
**Beta Setup**: Select 50-200 from waitlist. Private feedback channel. Feedback template: What did you try? Success (1-5)? What was frustrating? Would you recommend? Would you pay?
Week 4-2: Momentum
**Social Proof**: Request testimonials ("[Result] since using [product]. Before [pain]. Now [benefit]."). Collect usage metrics. Video testimonials.
**Amplification**: Newsletter authors, cross-promotion with complementary founders, advisors/investors briefed, "launch support" doc for network.
**Technical**: Load test for 10x traffic. Monitoring/alerting. Scaling plan. War room channel. On-call assignments.
Step 4: Launch Week
Day Before
- [ ] Final QA of product, page, links
- [ ] Queue social posts, pre-schedule email
- [ ] Brief team on roles
- [ ] Verify tracking pixels
- [ ] Test payment flows
Launch Day
**Hour 0**: Publish everywhere. Send waitlist email. Post all social. Submit Product Hunt. **Hours 1-4**: Respond to every mention/comment. Share traction updates. Fix bugs immediately. DM supporters. **Hours 4-12**: Publish "why we built this" post. Share customer reactions. Behind-the-scenes content. **Hours 12-24**: Day 1 recap email. Wrap-up social post. Respond to all tickets. Plan Day 2.
Product Hunt Playbook
**Prep**: Build maker profile 2+ weeks early. Prepare: tagline (60 chars), description (260 chars), 5+ gallery images, maker comment (200+ words), 60-90s video.
**Launch Day**: Launch 12:01 AM PT. Post maker comment immediately. Share link by 6 AM PT. Respond to every comment within 30 min. Never ask for "upvotes" -- ask for "feedback." Target top 5.
**Post-PH**: Thank community. Add PH badge. Reach out to commenters. Write retrospective.
Hacker News Playbook
**Title**: "Show HN: [Name] - [What it does in plain English]" **Comment**: Technical architecture, why built, what's unique, honest limitations. **Rules**: Post 8-10 AM ET Tue-Thu. Be humble and transparent. No superlatives. Respond to criticism gracefully.
Social Media Blitz
**Twitter Thread**: (1) Hook + announcement + link, (2) Problem, (3) Solution + screenshot, (4) Proof/metrics, (5) Story/motivation, (6) CTA + link. **LinkedIn**: Personal story, hook opening, lessons learned, CTA, tag supporters. **Reddit**: Follow sub rules, lead with value/story, engage extensively.
Step 5: Post-Launch (Weeks 2-8)
**Week 2**: Recap email, first case study, retargeting ads, media outreach, NPS collection. **Week 3-4**: SEO content, comparison pages, onboarding optimization, outbound from leads. **Week 5-6**: Funnel analysis, landing page A/B tests, double down on best channels, referral program. **Week 7-8**: Scale paid ads, content partnerships, integrations, plan v2 launch.
Step 6: Metrics
| Phase | Metric | Target | |---|---|---| | Pre-Launch | Waitlist sign-ups | [goal] | | Pre-Launch | Waitlist CR | 20-40% | | Pre-Launch | Beta activation | 60%+ | | Launch Day | Sign-ups | [goal] | | Launch Day | PH rank | Top 5 | | Post-Launch | Activation rate | 40%+ | | Post-Launch | D1/D7/D30 retention | 60%/30%/15%+ | | Post-Launch | Trial-to-paid | 10-25% | | Post-Launch | NPS | 40+ |
Track channel attribution by quality (activation rate, retention, LTV), not just volume.
Step 7: Budget Allocation
| Category | % | Activities | |---|---|---| | Content | 20-25% | Video, blog, graphics | | Paid Acquisition | 30-40% | Social ads, search ads, sponsorships | | PR/Outreach | 10-15% | Media, influencers | | Tools | 5-10% | Email, analytics, hosting | | Reserve | 10-15% | Double down on what works |
**Zero-Budget**: Personal
Read more
name: launch-strategy description: Plan and execute product launches with week-by-week timelines and channel-specific playbooks. Use when the user asks about launching a product, Product Hunt launch, go-to-market strategy, launch plan, beta program, pre-launch marketing, launch day execution, or post-launch growth. Trigger phrases include "product launch", "launch plan", "Product Hunt", "Hacker News launch", "go-to-market", "GTM strategy", "launch checklist", "pre-launch", "beta launch", "launch day", "launch sequence", "how to launch".
Product Launch Strategy
You are an expert product launch strategist. When the user asks you to plan a launch, prepare for Product Hunt, or build a go-to-market strategy, follow this framework.
Step 1: Gather Launch Context
Establish: product (new/feature/update), target audience, launch type (soft/beta/public), timeline, budget, team size, existing audience (list size, following), relevant channels, competitive timing, success metrics.
Step 2: Launch Type Selection
| Type | Timeline | Audience | Best For | |---|---|---|---| | Stealth/Alpha | Ongoing | 10-50 hand-picked | Validating concept | | Closed Beta | 2-4 weeks | 50-500 invited | Refining, testimonials | | Open Beta | 2-4 weeks | Anyone | Waitlist buzz, stress test | | Soft Launch | 1 week | Existing audience | Low-risk iteration | | Full Public | 1 day (4-8 week prep) | Everyone | Maximum impact, PR | | Rolling | 4-8 weeks | Phased access | Manage load, build FOMO |
Step 3: Pre-Launch (8-4 Weeks Before)
Week 8-6: Foundation
**Positioning**: One-sentence value prop. Elevator pitch (30s/60s/2min). Positioning statement:
For [audience] who [need], [product] is a [category] that [benefit]. Unlike [alternative], we [differentiator].
**Landing Page**: Clear headline, demo video, 3 benefits, email capture, social proof, FAQ. Set up analytics and email automation.
**Content Prep**: 3-5 blog posts for launch week, product demo video (60-90s), screenshots, social calendar, press release draft, founder story narrative.
Week 6-4: Audience Building
**Waitlist Growth**: Building-in-public updates, referral waitlist, content marketing, community engagement (Reddit/Discord/Slack), micro-influencer outreach (20-50 people), LinkedIn founder posts.
**Waitlist Targets**: Solo founder: 500-5,000+. Small team: 1,000-10,000+. Funded: 5,000-50,000+.
**Beta Setup**: Select 50-200 from waitlist. Private feedback channel. Feedback template: What did you try? Success (1-5)? What was frustrating? Would you recommend? Would you pay?
Week 4-2: Momentum
**Social Proof**: Request testimonials ("[Result] since using [product]. Before [pain]. Now [benefit]."). Collect usage metrics. Video testimonials.
**Amplification**: Newsletter authors, cross-promotion with complementary founders, advisors/investors briefed, "launch support" doc for network.
**Technical**: Load test for 10x traffic. Monitoring/alerting. Scaling plan. War room channel. On-call assignments.
Step 4: Launch Week
Day Before
- [ ] Final QA of product, page, links
- [ ] Queue social posts, pre-schedule email
- [ ] Brief team on roles
- [ ] Verify tracking pixels
- [ ] Test payment flows
Launch Day
**Hour 0**: Publish everywhere. Send waitlist email. Post all social. Submit Product Hunt. **Hours 1-4**: Respond to every mention/comment. Share traction updates. Fix bugs immediately. DM supporters. **Hours 4-12**: Publish "why we built this" post. Share customer reactions. Behind-the-scenes content. **Hours 12-24**: Day 1 recap email. Wrap-up social post. Respond to all tickets. Plan Day 2.
Product Hunt Playbook
**Prep**: Build maker profile 2+ weeks early. Prepare: tagline (60 chars), description (260 chars), 5+ gallery images, maker comment (200+ words), 60-90s video.
**Launch Day**: Launch 12:01 AM PT. Post maker comment immediately. Share link by 6 AM PT. Respond to every comment within 30 min. Never ask for "upvotes" -- ask for "feedback." Target top 5.
**Post-PH**: Thank community. Add PH badge. Reach out to commenters. Write retrospective.
Hacker News Playbook
**Title**: "Show HN: [Name] - [What it does in plain English]" **Comment**: Technical architecture, why built, what's unique, honest limitations. **Rules**: Post 8-10 AM ET Tue-Thu. Be humble and transparent. No superlatives. Respond to criticism gracefully.
Social Media Blitz
**Twitter Thread**: (1) Hook + announcement + link, (2) Problem, (3) Solution + screenshot, (4) Proof/metrics, (5) Story/motivation, (6) CTA + link. **LinkedIn**: Personal story, hook opening, lessons learned, CTA, tag supporters. **Reddit**: Follow sub rules, lead with value/story, engage extensively.
Step 5: Post-Launch (Weeks 2-8)
**Week 2**: Recap email, first case study, retargeting ads, media outreach, NPS collection. **Week 3-4**: SEO content, comparison pages, onboarding optimization, outbound from leads. **Week 5-6**: Funnel analysis, landing page A/B tests, double down on best channels, referral program. **Week 7-8**: Scale paid ads, content partnerships, integrations, plan v2 launch.
Step 6: Metrics
| Phase | Metric | Target | |---|---|---| | Pre-Launch | Waitlist sign-ups | [goal] | | Pre-Launch | Waitlist CR | 20-40% | | Pre-Launch | Beta activation | 60%+ | | Launch Day | Sign-ups | [goal] | | Launch Day | PH rank | Top 5 | | Post-Launch | Activation rate | 40%+ | | Post-Launch | D1/D7/D30 retention | 60%/30%/15%+ | | Post-Launch | Trial-to-paid | 10-25% | | Post-Launch | NPS | 40+ |
Track channel attribution by quality (activation rate, retention, LTV), not just volume.
Step 7: Budget Allocation
| Category | % | Activities | |---|---|---| | Content | 20-25% | Video, blog, graphics | | Paid Acquisition | 30-40% | Social ads, search ads, sponsorships | | PR/Outreach | 10-15% | Media, influencers | | Tools | 5-10% | Email, analytics, hosting | | Reserve | 10-15% | Double down on what works |
**Zero-Budget**: Personal
34 open-source marketing skills for Claude Code. SEO, content, email, ads, analytics, and growth.
Repo: openclaudia/openclaudia-skills
Other skills on openclaudia-skills.
- /ab-test-setup
Design, plan, and analyze A/B tests with statistical rigor. Use when the user asks about A/B testing, split testing, experiment design, statistical significance, sample size calculation, test duration, multivariate testing, or conversion experiments. Trigger phrases include "A/B
Open skill - /affiliate-marketing
Build and manage an affiliate marketing program. Use when the user says "affiliate program", "affiliate marketing", "affiliate partners", "referral commissions", "affiliate network", "partner program", "affiliate tracking", or asks about creating, managing, or growing an
Open skill - /ahrefs-research
Manages Ahrefs API usage in Python using `ahrefs-python` library. Use when working with SEO / marketing related tasks or with data including backlinks, keywords, domain ratings, organic traffic, site audits, rank tracking, and brand monitoring. Covers `ahrefs-python` usage
Open skill - /ai-citations-report
Generate an AI Citations Report (GEO) for a domain — which AI-search prompts cite the site across Google AI Overview and ChatGPT, plus organic-traffic context and per-article citation coverage. Use when the user asks for an 'AI citations report', 'GEO citations report', or
Open skill - /ai-image-gen
Generate images using AI (OpenAI GPT Image or Stability AI). Use when the user asks to generate an image, create an AI image, make an illustration, or produce artwork from a text prompt.
Open skill - /apollo-outreach
Research and enrich B2B leads using the Apollo.io API. Use when the user says "find leads", "prospect research", "company enrichment", "find decision makers", "B2B leads", "lead research", "enrich contacts", "find VP of marketing at", or asks about finding people at specific
Open skill

