launch-strategy
Skill723 starsChanged 5 months agoMITView on GitHub
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".
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 62 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 89
Reddit: Follow sub rules, lead with value/story, engage extensively.
“Common” is measured: kept by at least 6 in 10 of the 62 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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 plansTailor to the user's resources. A solo founder needs a different plan than a funded startup.
Other versions62 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 62
- TheCraigHewitt/seomachine★ 7.5ksame name
- LeoYeAI/openclaw-marketing-skills★ 1ksame name
- mysticaltech/marketingskills★ 352same name
- shawnpang/startup-founder-skills★ 331same name
- b1rdmania/ghostclaw★ 91same name
- drvoss/everything-copilot-cli★ 49same name
- Infinite-Labs-AI/infinite-skills★ 43same name
- MoizIbnYousaf/marketing-cli★ 33same name
- robertbstillwell/marketing-skills★ 26same name
- ukunal91app/Marketing-Skills-by-Corey-Haines★ 26same name
52 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use aso-audit, product-marketing-context and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ai-vitaSkillaso-audit
When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my app conversion,' 'keyword optimization for app,' or 'compare my app to competitors.' Use when the user shares an App Store or Google Play URL and wants to improve it.
Also in 9 projects that use this
xfstudioSkillproduct-marketing-context
When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' or wants to avoid repeating foundational information across marketing tasks. Creates `.claude/product-marketing-context.md` that other marketing skills reference.
Also in 23 projects that use this
ukunal91appSkillrevops
When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see email-sequence. For pricing decisions, see pricing-strategy.
Also in 26 projects that use this
VercelSkillsite-architecture
Use when planning or restructuring what pages a site has and how they connect: hierarchy, navigation, URL patterns, breadcrumbs, and internal linking. Not for XML sitemaps, which are in seo-audit.
Also in 25 projects that use this
buildingwithaiSkillsales-enablement
Master world-class sales enablement from foundations to execution. Build comprehensive enablement programs, develop effective training and coaching systems, implement data-driven content strategies, leverage AI and modern technology stacks, establish cross-functional collaboration, measure ROI with precision, and drive revenue growth. Covers sales methodologies (MEDDIC, SPICED, BANT), maturity models (Forrester, Gartner), enablement frameworks, change management, remote enablement, market segment strategies (SMB, Mid-Market, Enterprise), and team building. Based on 2024-2025 industry research from Gartner, Forrester, Product Marketing Alliance, Sales Enablement Collective, and leading practitioners.
Also in 23 projects that use this
ukunal91appSkillad-creative
When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'ad performance optimization,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' or 'I need more ad variations.' Use this whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see paid-ads. For landing page copy, see copywriting.
Also in 26 projects that use this
- +4 more from ukunal91app
In this repository77 other files it gives its agents.
- ab-test-setupSkill
- affiliate-marketingSkill
- ahrefs-pythonSkill
- ai-citations-reportSkill
- generate-imageSkill
- apollo-outreachSkill
- backlink-auditSkill
- blueskySkill
- brand-monitorSkill
- brand-devSkill
- competitor-analysisSkill
- competitor-traffic-reportSkill
- content-calendarSkill
- content-gap-analysisSkill
- content-repurposingSkill
- content-strategySkill
- copy-editingSkill
- copywritingSkill
- demand-genSkill
- discord-botSkill
- domain-researchSkill
- email-sequenceSkill
- email-subject-linesSkill
- facebook-adsSkill
- feishu-larkSkill
- geo-analysisSkill
- geo-difficultySkill
- geo-query-finderSkill
- github-starsSkill
- glasser-researchSkill
- google-ads-reportSkill
- google-adsSkill
- google-analyticsSkill
- google-reviewsSkill
- growth-strategySkill
- gsc-portfolio-auditSkill
- hubspotSkill
- i18nSkill
- icp-builderSkill
- keyword-researchSkill
- lead-magnetSkill
- linkedin-adsSkill
- linkedin-contentSkill
- marketing-ideasSkill
- marketing-slidesSkill
- newsletterSkill
- onboarding-croSkill
- organize-skillsSkill
- page-croSkill
- podcast-editSkill
- podcast-marketingSkill
- pricing-strategySkill
- product-marketingSkill
- programmatic-seoSkill
- publish-articleSkill
- reddit-marketingSkill
- referral-programSkill
- schema-markupSkill
- search-consoleSkill
- semrush-researchSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

