launch-strategy

Q: How do I install launch-strategy?

Run npx skills add https://github.com/openclaudia/openclaudia-skills --skill launch-strategy in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/launch-strategy/ (personal) or .claude/skills/launch-strategy/ (project).

by openclaudiaMarketing & SEO

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

Installs: 447
Last 24h: —
Trending rank: —
Security: Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/openclaudia/openclaudia-skills --skill launch-strategy

01
Install
Run the command in your project. The CLI asks which agents to install for.
02
Describe the task
Ask your agent for something this skill covers. It loads launch-strategy automatically when relevant.
03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

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

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.

FAQ

What does the launch-strategy skill do?

How do I install launch-strategy?

Run npx skills add https://github.com/openclaudia/openclaudia-skills --skill launch-strategy in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/launch-strategy/ (personal) or .claude/skills/launch-strategy/ (project).

Which AI agents can use launch-strategy?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is launch-strategy safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains launch-strategy?

It is published by openclaudia in openclaudia/openclaudia-skills. It has 447 recorded installs.