Weekly Launch Playbook

Launch strategy

by OpenClaudia · MIT license · ★ 705 on GitHub

Launch strategy cover

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,…

---
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 |

Overview

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.

Manual install (npx, ZIP)
Claude Codenpx skills add OpenClaudia/openclaudia-skills --skill launch-strategy -g -a claude-code
Claude Code (degit)npx degit OpenClaudia/openclaudia-skills/skills/launch-strategy#main ~/.claude/skills/launch-strategy-openclaudia
Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md6.4 KB
Read SKILL.md here
OpenClaudia/main1 file shown
SKILL.md
Show the full text143 lines

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 network, Product Hunt, Show HN, Reddit, Twitter thread, cold email journalists, cross-promotion, free email tools.

Output Format

LAUNCH PLAN: [Product]
=======================
TYPE: [type] | DATE: [date] | TARGET: [metric]

TIMELINE: Week-by-week activities
CHANNEL PLAYBOOKS: Detailed per-channel plans
CONTENT CALENDAR: Pieces with publish dates
LAUNCH DAY CHECKLIST: Hour-by-hour execution
BUDGET: Category allocation
METRICS: KPIs with targets
RISK MITIGATION: Contingency plans

Tailor to the user's resources. A solo founder needs a different plan than a funded startup.

1---
2name: launch-strategy
3description: 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".
4---
5 
6# Product Launch Strategy
7 
8You 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.
9 
10## Step 1: Gather Launch Context
11 
12Establish: 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.
13 
14## Step 2: Launch Type Selection
15 
16| Type | Timeline | Audience | Best For |
17|---|---|---|---|
18| Stealth/Alpha | Ongoing | 10-50 hand-picked | Validating concept |
19| Closed Beta | 2-4 weeks | 50-500 invited | Refining, testimonials |
20| Open Beta | 2-4 weeks | Anyone | Waitlist buzz, stress test |
21| Soft Launch | 1 week | Existing audience | Low-risk iteration |
22| Full Public | 1 day (4-8 week prep) | Everyone | Maximum impact, PR |
23| Rolling | 4-8 weeks | Phased access | Manage load, build FOMO |
24 
25## Step 3: Pre-Launch (8-4 Weeks Before)
26 
27### Week 8-6: Foundation
28 
29**Positioning**: One-sentence value prop. Elevator pitch (30s/60s/2min). Positioning statement:
30```
31For [audience] who [need], [product] is a [category] that [benefit].
32Unlike [alternative], we [differentiator].
33```
34 
35**Landing Page**: Clear headline, demo video, 3 benefits, email capture, social proof, FAQ. Set up analytics and email automation.
36 
37**Content Prep**: 3-5 blog posts for launch week, product demo video (60-90s), screenshots, social calendar, press release draft, founder story narrative.
38 
39### Week 6-4: Audience Building
40 
41**Waitlist Growth**: Building-in-public updates, referral waitlist, content marketing, community engagement (Reddit/Discord/Slack), micro-influencer outreach (20-50 people), LinkedIn founder posts.
42 
43**Waitlist Targets**: Solo founder: 500-5,000+. Small team: 1,000-10,000+. Funded: 5,000-50,000+.
44 
45**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?
46 
47### Week 4-2: Momentum
48 
49**Social Proof**: Request testimonials ("[Result] since using [product]. Before [pain]. Now [benefit]."). Collect usage metrics. Video testimonials.
50 
51**Amplification**: Newsletter authors, cross-promotion with complementary founders, advisors/investors briefed, "launch support" doc for network.
52 
53**Technical**: Load test for 10x traffic. Monitoring/alerting. Scaling plan. War room channel. On-call assignments.
54 
55## Step 4: Launch Week
56 
57### Day Before
58- [ ] Final QA of product, page, links
59- [ ] Queue social posts, pre-schedule email
60- [ ] Brief team on roles
61- [ ] Verify tracking pixels
62- [ ] Test payment flows
63 
64### Launch Day
65 
66**Hour 0**: Publish everywhere. Send waitlist email. Post all social. Submit Product Hunt.
67**Hours 1-4**: Respond to every mention/comment. Share traction updates. Fix bugs immediately. DM supporters.
68**Hours 4-12**: Publish "why we built this" post. Share customer reactions. Behind-the-scenes content.
69**Hours 12-24**: Day 1 recap email. Wrap-up social post. Respond to all tickets. Plan Day 2.
70 
71### Product Hunt Playbook
72 
73**Prep**: Build maker profile 2+ weeks early. Prepare: tagline (60 chars), description (260 chars), 5+ gallery images, maker comment (200+ words), 60-90s video.
74 
75**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.
76 
77**Post-PH**: Thank community. Add PH badge. Reach out to commenters. Write retrospective.
78 
79### Hacker News Playbook
80 
81**Title**: "Show HN: [Name] - [What it does in plain English]"
82**Comment**: Technical architecture, why built, what's unique, honest limitations.
83**Rules**: Post 8-10 AM ET Tue-Thu. Be humble and transparent. No superlatives. Respond to criticism gracefully.
84 
85### Social Media Blitz
86 
87**Twitter Thread**: (1) Hook + announcement + link, (2) Problem, (3) Solution + screenshot, (4) Proof/metrics, (5) Story/motivation, (6) CTA + link.
88**LinkedIn**: Personal story, hook opening, lessons learned, CTA, tag supporters.
89**Reddit**: Follow sub rules, lead with value/story, engage extensively.
90 
91## Step 5: Post-Launch (Weeks 2-8)
92 
93**Week 2**: Recap email, first case study, retargeting ads, media outreach, NPS collection.
94**Week 3-4**: SEO content, comparison pages, onboarding optimization, outbound from leads.
95**Week 5-6**: Funnel analysis, landing page A/B tests, double down on best channels, referral program.
96**Week 7-8**: Scale paid ads, content partnerships, integrations, plan v2 launch.
97 
98## Step 6: Metrics
99 
100| Phase | Metric | Target |
101|---|---|---|
102| Pre-Launch | Waitlist sign-ups | [goal] |
103| Pre-Launch | Waitlist CR | 20-40% |
104| Pre-Launch | Beta activation | 60%+ |
105| Launch Day | Sign-ups | [goal] |
106| Launch Day | PH rank | Top 5 |
107| Post-Launch | Activation rate | 40%+ |
108| Post-Launch | D1/D7/D30 retention | 60%/30%/15%+ |
109| Post-Launch | Trial-to-paid | 10-25% |
110| Post-Launch | NPS | 40+ |
111 
112Track channel attribution by quality (activation rate, retention, LTV), not just volume.
113 
114## Step 7: Budget Allocation
115 
116| Category | % | Activities |
117|---|---|---|
118| Content | 20-25% | Video, blog, graphics |
119| Paid Acquisition | 30-40% | Social ads, search ads, sponsorships |
120| PR/Outreach | 10-15% | Media, influencers |
121| Tools | 5-10% | Email, analytics, hosting |
122| Reserve | 10-15% | Double down on what works |
123 
124**Zero-Budget**: Personal network, Product Hunt, Show HN, Reddit, Twitter thread, cold email journalists, cross-promotion, free email tools.
125 
126## Output Format
127 
128```
129LAUNCH PLAN: [Product]
130=======================
131TYPE: [type] | DATE: [date] | TARGET: [metric]
132 
133TIMELINE: Week-by-week activities
134CHANNEL PLAYBOOKS: Detailed per-channel plans
135CONTENT CALENDAR: Pieces with publish dates
136LAUNCH DAY CHECKLIST: Hour-by-hour execution
137BUDGET: Category allocation
138METRICS: KPIs with targets
139RISK MITIGATION: Contingency plans
140```
141 
142Tailor to the user's resources. A solo founder needs a different plan than a funded startup.
143 
View all files on GitHub →

Details

License
MIT
Stars on the repo
★ 705
Checked
Source
OpenClaudia/openclaudia-skills ↗
Creator
OpenClaudia · 78 listings
View creator

Similar skills

See all →
SkillLaunch Video Composerlatent-spaces/brag · by latent-spacesTurn the current project website into a short, polished, shareable launch video using Hyperframes. Use when someone says "/brag", "let's brag about this", "make a launch video", "turn this into a video", or wants to share what they built. Reads the project code directly — no live URL or screenshots needed.★ 12.5k GitHub starsSkillQuick Launch Videolatent-spaces/brag · by latent-spacesTurn a project directory or a website URL into a short, shareable launch video with music, motion, and share copy. One file, no bundled assets — built entirely by the model with the tools already on the machine. Use when someone says "/brag-slim", "let's /brag about this", "brag about <url>", "make a launch video", or wants to show off what they built. If the /brag skill is also installed, let /brag handle those phrases; it hands off here on Opus 5.5.★ 12.5k GitHub starsSkillCommercial Motion Filmechris6/motion-video-kit · by echris6Plan, build and quality-check a premium short commercial for a real business (roofing, property, ecommerce, B2B software) using AI-generated footage, code-built motion (HTML/GSAP), selective Three.js and an independent-critic "Gauntlet" loop. Use when asked to make a launch-style / SaaS-style video, business ad, explainer, sample reel or pitch video, or to review and improve one. Encodes motion principles distilled from 28 professional launch films, a quality bar, audio rules and a business-offer playbook.★ 665 GitHub starsSkillAI Product Launch PlaybookGingiris-1031/gingiris-skills · by Gingiris-1031Launch your AI product to global attention — the playbook behind Manus, Devin, and AFFiNE's breakout launches. Covers AI-specific GTM strategy, hype cycle management, waitlist tactics, and multi-market rollout for maximum day-one impact.★ 82 GitHub starsSkillMotion OS Studiojasonlee-breadcrumb/motion-os · by jasonlee-breadcrumbBuild motion graphics and launch videos in code, then open them in Motion OS, a local scene-by-scene review player where the user edits copy, pins notes on the frame, and sends one prompt back. Use when the user asks for a motion graphic, launch video, explainer, product video or animated ad, says "motion os", or pastes feedback that starts with "Motion OS feedback for".★ 61 GitHub starsSkillLaunch Video Creatortimscheuerai/content-vault · by timscheueraiBuild a 30-60s motion-graphics launch video for a <YOUR_BRAND> product or feature. Remotion 4 React composition + ElevenLabs AI narration + sound effects + background music, beat-anchored timing, brand-aligned design system. Use when asked to "create a launch video", "make a product video", "video for X feature", "launch a new feature", or "/launch-video".★ 37 GitHub stars

More from OpenClaudia

SkillA/B Testing FrameworkOpenClaudia/openclaudia-skills · by OpenClaudiaDesign, 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 test", "split test", "experiment", "statistical significance", "sample size", "test duration", "which version wins", "conversion experiment", "hypothesis test", "variant testing".★ 705 GitHub starsSkillAffiliate Marketing ProgramOpenClaudia/openclaudia-skills · by OpenClaudiaBuild 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 affiliate or partner program.★ 705 GitHub starsSkillAhrefs API ManagerOpenClaudia/openclaudia-skills · by OpenClaudiaManages 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 including AhrefsClient / AsyncAhrefsClient, typed request/response models, error handling, and all API sections.★ 705 GitHub starsSkillAI Citations Report GeneratorOpenClaudia/openclaudia-skills · by OpenClaudiaGenerate 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 'which AI prompts cite <domain>'.★ 705 GitHub starsSkillB2B Lead EnricherOpenClaudia/openclaudia-skills · by OpenClaudiaResearch 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 companies or in specific roles.★ 705 GitHub starsSkillBacklink Health CheckerOpenClaudia/openclaudia-skills · by OpenClaudiaAudit a domain's backlink profile using the SemRush API. Use when the user says "audit backlinks", "check my backlinks", "backlink analysis", "link profile", "toxic links", "disavow", "link building opportunities", "referring domains", "anchor text", or asks about a site's link authority.★ 705 GitHub stars