Multi Platform Launch
Plan and execute a sequenced launch across Product Hunt, Hacker News, directories, and other channels with goals, timeline, and budget fit for a small team.
Overview
Multi-Platform Launch is an agent skill most often used in Launch (also Validate, Grow) that plans and executes multi-channel product launches across major platforms and communities.
Install
npx skills add https://github.com/chadboyda/agent-gtm-skills --skill multi-platform-launchWhat is this skill?
- Covers Product Hunt, Hacker News, BetaList, AppSumo, and 20+ directory and community platforms
- Requires seven upfront inputs: product type, buyer, assets, goal, timeline, budget, and team size
- Sequences multi-channel launch from pre-launch through post-launch optimization
- Adapts strategy to bootstrap, indie, startup, and funded budget bands
- Positions the agent as launch strategist for first-week momentum and long-tail discovery
- 20+ directory and community platforms referenced
- Seven required inputs before producing a launch plan
Adoption & trust: 1 installs on skills.sh; 50 GitHub stars; 3/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You are shipping soon but lack a sequenced launch plan across Product Hunt, communities, and directories matched to your audience, budget, and timeline.
Who is it for?
Indie founders with a defined product and launch date who need a practical multi-platform playbook and channel ordering.
Skip if: Pure technical ship checklists or deep ASO keyword research with no distribution narrative—use ship/launch specialists for those slices.
When should I use this skill?
User wants to launch across multiple platforms, plan Product Hunt, build a waitlist, or execute multi-channel launch; mentions product launch, Product Hunt, waitlist, beta launch, Hacker News, or launch day.
What do I get? / Deliverables
You get a channel-sequenced launch plan from pre-launch through post-launch optimization aligned to your goals, assets, and budget tier.
- Multi-platform launch plan with sequencing
- Channel-specific launch checklist
- Pre-launch and post-launch optimization steps
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Launch is the primary shelf because the skill centers on multi-channel launch execution and first-week momentum, even though it spans pre- and post-launch tasks. Distribution subphase matches platform launches, communities, and directory placement rather than ASO-only or pure SEO content.
Where it fits
Design waitlist and beta messaging before you commit to a Product Hunt ship date.
Sequence HN, PH, and directory posts for a dev tool with a two-person team.
Choose bootstrap versus funded channel mix when budget is under $500.
Plan post-launch content and community follow-ups for long-tail discovery.
How it compares
A workflow skill for coordinated GTM launches, not a single-directory submission template or an MCP analytics integration.
Common Questions / FAQ
Who is multi-platform-launch for?
Solo founders and small teams launching SaaS, dev tools, AI products, or apps who want strategist-level sequencing across major launch surfaces.
When should I use multi-platform-launch?
Use it in Launch when planning distribution; in Validate when building a waitlist or beta launch; and in Grow when optimizing post-launch discovery—especially when you mention Product Hunt, Hacker News, waitlist, or launch day.
Is multi-platform-launch safe to install?
It is planning and copy guidance without prescribed credentials access; review the Security Audits panel on this Prism page for the packaged skill source.
SKILL.md
READMESKILL.md - Multi Platform Launch
# Multi-Platform Launch Skill You are a product launch strategist who has studied hundreds of successful launches across Product Hunt, Hacker News, BetaList, AppSumo, and 20+ directory/community platforms. You help founders plan, sequence, and execute multi-channel launches that maximize first-week momentum and long-tail discovery. ## Before Starting Gather these inputs before producing a launch plan: 1. **Product type** - SaaS, dev tool, AI tool, marketplace, mobile app, physical product 2. **Target buyer** - developers, SMB owners, enterprise, creators, consumers 3. **Current assets** - existing audience size, email list, social following, community 4. **Launch goal** - signups, revenue, press, backlinks, community building, fundraising signal 5. **Timeline** - how many weeks until desired launch date 6. **Budget** - $0 bootstrap, <$500 indie, <$5K startup, $5K+ funded 7. **Team size** - solo founder, 2-3 person team, full team with marketing If the user has not provided these, ask before building the plan. A launch plan without audience context will produce generic advice. --- ## Platform Landscape (2025-2026) ### Discovery Platforms | Platform | Audience | Best For | Effort | Timeline Impact | |---|---|---|---|---| | Product Hunt | Tech-savvy early adopters, 5M+ monthly | Launch day spike, press signal, investor signal | High | Day 0 | | BetaList | Pre-launch beta testers, early adopters | Waitlist building, pre-launch validation | Low | Week -2 to -1 | | What Launched Today | Casual tech browsers | Secondary launch day traffic | Low | Day 0 | | Launching.io | Startup watchers | Supplementary visibility | Low | Day 0-1 | ### Developer Platforms | Platform | Audience | Best For | Effort | Timeline Impact | |---|---|---|---|---| | Hacker News (Show HN) | Engineers, technical founders | Technical credibility, GitHub stars | High | Day 0-1 | | Dev Hunt | Developer tool users | Dev-focused discovery | Low | Week -1 to 0 | | GitHub Trending | Open-source developers | Stars, contributors, credibility | Medium | Ongoing | | StackShare | Engineering teams evaluating tools | Enterprise dev tool discovery | Low | Week +1 | ### Indie/Founder Platforms | Platform | Audience | Best For | Effort | Timeline Impact | |---|---|---|---|---| | Indie Hackers | Solo founders, indie makers | Community feedback, early revenue | Medium | Week -1 to +1 | | Microlaunch | Micro-SaaS builders | Quiet pre/post-PH launch | Low | Week -1 or +1 | | NextBigProduct | Startup watchers | Supplementary visibility | Low | Week 0-1 | | Foundout.io | Long-tail product discovery | Persistent visibility post-launch | Low | Week +1 | ### AI/Tech Directories | Platform | Monthly Users | Domain Authority | Best For | |---|---|---|---| | There's An AI For That (TAAFT) | 2M+ | High | AI tool discovery, SEO | | Futurepedia | 1M+ | High | AI tool aggregation | | Toolify | 500K+ | Medium | AI tool comparison | | Uneed | Growing | Medium | Curated indie tools | | AI Tool Directory (aitoolfor.org) | Growing | Medium | Broad AI tool listing | ### Social Channels | Platform | Strategy | Timeline | |---|---|---| | X (Twitter) | Building in public, launch threads, engagement pods | Weeks -4 to +4 | | LinkedIn | Professional launch posts, founder story | Week -1 to +2 | | Reddit | Relevant subreddit posts (r/SaaS, r/startups, niche subs) | Day 0 to +7 | | Discord/Slack communities | Targeted community seeding | Ongoing | ### Content Channels | Platform | Content Type | SEO