product-hunt-launch-plan
Creates a comprehensive, personalized Product Hunt launch plan to rank
What this skill does
# Product Hunt Launch Plan ## Purpose Generate a comprehensive, personalized Product Hunt launch plan with actionable steps from A-Z to help the user rank #1 Product of the Day. --- ## Execution Logic **Check $ARGUMENTS first to determine execution mode:** ### If $ARGUMENTS is empty or not provided: Respond with: "product-hunt-launch-plan loaded. I'll create a personalized Product Hunt launch strategy to help you rank #1. Let me gather some information about your product first." Then proceed to the Discovery Questions phase. ### If $ARGUMENTS contains content: Use the provided content as initial context, but still proceed through Discovery Questions to fill any gaps. --- ## Task Execution When user engages with this skill: ### 1. MANDATORY: Read Reference Files FIRST **BLOCKING REQUIREMENT — DO NOT SKIP THIS STEP** Before doing ANYTHING else, you MUST use the Read tool to read the reference file: ``` Read: ./references/ultimate_product_hunt_launch_guide.md ``` **What you will find:** - Complete 3-phase launch strategy (Before, During, After) - Timing and day selection guidance - Asset requirements and examples - Support list building strategies - Launch day timeline hour-by-hour - Hidden gems and pro tips from makers who ranked #1 - 20+ alternative launch platforms **DO NOT PROCEED** to Step 2 until you have read this file and have the complete guide in context. ### 2. Check for Business Context Check if `FOUNDER_CONTEXT.md` exists in the project root. - **If it exists:** Read it and extract all relevant product information (product name, description, target audience, unique value proposition, current traction, audience size). - **If it doesn't exist:** You will gather this information through Discovery Questions. ### 3. Discovery Questions (MANDATORY) **Ask up to 10 targeted questions to personalize the launch plan.** Present questions using the AskUserQuestion tool or conversationally. Gather: 1. **Product Basics** - What is your product name and one-line description? - What problem does it solve and for whom? 2. **Current State** - What's your current launch date (or target timeframe)? - Do you have a Product Hunt account? Is it active/warmed? 3. **Audience & Reach** - How large is your email list? - What's your Twitter/X following size? - Are you active in any communities (Indie Hackers, Discord, Slack)? 4. **Assets Readiness** - Do you have product screenshots/demo video ready? - Do you have a landing page live? 5. **Support Network** - Do you have founder friends who could support the launch? - Have you supported other Product Hunt launches before? 6. **Goals & Constraints** - What's your primary goal? (users, awareness, investors, validation) - Any constraints? (budget, time, team size) **Adapt questions based on FOUNDER_CONTEXT.md if available.** Skip questions already answered there. ### 4. Analyze & Personalize Based on gathered information, assess: - **Support Strength:** Weak (<100 supporters), Moderate (100-300), Strong (300-500+) - **Asset Readiness:** Not ready, Partially ready, Fully ready - **Timeline:** Rushed (<2 weeks), Tight (2-4 weeks), Ideal (4+ weeks) - **Audience Reach:** Limited, Moderate, Strong Use this assessment to customize recommendations. ### 5. Generate Personalized Launch Plan Create a comprehensive plan with: **Section 1: Executive Summary** - Product overview (from their input) - Launch date recommendation - Predicted ranking potential based on their current assets - Key success factors for THEIR specific situation **Section 2: Pre-Launch Phase (customize timeline based on their date)** - Week-by-week action items - Specific community recommendations based on their niche - Asset creation checklist tailored to what they're missing - Support list building strategy based on their current reach **Section 3: Launch Week Preparation** - Day-by-day countdown - Specific outreach templates personalized for their product - Social media post drafts - Email copy suggestions **Section 4: Launch Day Battle Plan** - Hour-by-hour timeline in their timezone - Specific platforms to post on based on their product type - Engagement scripts for comments - Monitoring setup **Section 5: Post-Launch Strategy** - Follow-up actions - How to leverage results (even if not #1) - Badge/social proof implementation **Section 6: Hidden Gems & Pro Tips** Include 5-10 advanced tactics from the reference guide, selected based on relevance to their situation. **Section 7: Alternative Launch Platforms** List the 20+ platforms from the reference guide, prioritized based on their product type (dev tool, SaaS, AI product, etc.). ### 6. Format and Verify - Structure output according to **Output Format** section - Complete **Quality Checklist** self-verification before presenting --- ## Writing Rules Hard constraints. No interpretation. ### Core Rules - Be specific and actionable — no vague advice like "build community" - Include exact timelines, numbers, and examples - Personalize every recommendation to THEIR product - Reference their product name throughout the plan - Include templates they can copy/paste - Prioritize actions by impact ### Personalization Rules - If small audience (<500): Focus on community building and reciprocity tactics - If large audience (5000+): Focus on coordinated launch and momentum strategies - If dev tool: Emphasize Hacker News, DevHunt, GitHub community - If AI product: Include AI-specific directories - If B2B SaaS: Focus on LinkedIn, professional communities - If consumer app: Focus on Twitter/X, visual assets ### Honesty Rules - Be realistic about their chances based on their current situation - If timeline is too tight, say so and suggest rescheduling - If assets are weak, prioritize fixing that first - Don't promise #1 if their support base is too small --- ## Output Format ```markdown # Product Hunt Launch Plan: [Product Name] ## Executive Summary **Product:** [Name] - [One-liner] **Recommended Launch Date:** [Date] ([Day of week]) **Launch Time:** 12:01 AM PST **Ranking Potential:** [Assessment based on their situation] **Critical Success Factor:** [The ONE thing they must nail] --- ## Phase 1: Pre-Launch ([X] weeks out) ### Week [X]: [Focus Area] - [ ] Action item 1 - [ ] Action item 2 ... ### Week [X-1]: [Focus Area] ... --- ## Phase 2: Launch Week ### Day -7 to -1: Final Preparations ... ### Launch Day: Hour-by-Hour Battle Plan **[Time in their timezone] - [Action]** ... --- ## Phase 3: Post-Launch ### Day 1-3: Immediate Actions ... ### Week 1: Capitalize on Results ... --- ## Your Personalized Tips Based on your situation, focus on these advanced tactics: 1. **[Tip Name]:** [Specific advice for their situation] ... --- ## Alternative Launch Platforms (Prioritized for [Product Type]) ### Launch This Week (Alongside Product Hunt) | Platform | Why It Fits You | |----------|-----------------| ... ### Launch Next Week ... --- ## Ready-to-Use Templates ### Supporter DM Template [Personalized template with their product details] ### Launch Day Tweet Thread [Draft thread they can customize] ### Email to Subscribers [Draft email copy] --- ## Your Launch Checklist ### Assets Needed - [ ] Item (Status: Ready/Needed) ... ### Support List Target - [ ] Category: [X] people (Current: [Y]) ... ``` --- ## References **This file MUST be read using the Read tool before creating any launch plan (see Step 1):** | File | Purpose | |------|---------| | `./references/ultimate_product_hunt_launch_guide.md` | Complete Product Hunt strategy from Tibo (Maker of the Year 2022), including 3-phase launch process, hidden gems, pro tips, and 20+ alternative platforms | **Why this matters:** This guide contains battle-tested strategies from someone who has ranked #1 multiple times. The tactics, timing, and templates are proven to work — not theoretical advice. --- ## Quality Checklist (Self-Verification) Before finalizing ou
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.