product-hunt-launch-plan

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 90bc6f1424df · 28 Oct 2026Report an issue or request a re-scan

• Publisherognjengt GitHub userOwner of the repository this skill is read from
• Source folderognjengt/founder-skills/skills/product-hunt-launch-planThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdict90bc6f1424dfA new audit runs when the source changes
• Repository statusNot archivedLast push 162 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Creates a comprehensive, personalized Product Hunt launch plan to rank #1. Use when user needs a step-by-step Product Hunt launch strategy, launch checklist, or wants to maximize their Product Hunt success.

---
name: product-hunt-launch-plan
description: Creates a comprehensive, personalized Product Hunt launch plan to rank #1. Use when user needs a step-by-step Product Hunt launch strategy, launch checklist, or wants to maximize their Product Hunt success.
---

# 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 

Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/ognjengt/founder-skills
git -C founder-skills checkout 90bc6f1424df

Works in

1. 2026-10-28
   ✓SAFE B 89 / 100

   first audit · source 90bc6f1424df

Questions about product-hunt-launch-plan

• github.com/ognjengt/founder-skills/tree/main/skills/product-hunt — the audited source at commit 90bc6f1424df and every finding aboveObserved · 28 Oct 2026

Spotted something wrong? Report a correction · Methodology