agentleFS
CodeAlive-AICodeAlive-AI/ceo-ai-os/skills/ph-launch-timeline/SKILL.md

ph-launch-timeline

Skill9 starsChanged 6 months agoMITView on GitHub

When the user needs a 30-day Product Hunt preparation timeline, launch readiness checklist, or realistic outcome expectations. Also use when planning PH launch phases, building supporter lists, or assessing launch readiness.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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
  1. Distinctive:

    Follow up with interested users from comments (week 2)

    line 74
  2. Distinctive:

    Check eligibility for "Product of the Week/Month" (month 1)

    line 75
  3. Distinctive:

    Follow output preferences from USER.md (language, format, platform constraints).

    line 88

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Product Hunt Launch Timeline & Preparation

30-day structured preparation plan for Product Hunt launches. Use alongside product-hunt-launch skill for tactical details.

When invoking: On first use, open with 1-2 sentences on what this skill covers. On subsequent use, go directly to output.

Initial Assessment

Identify:

  1. Product type: SaaS, AI tool, app, Chrome extension
  2. Launch readiness: Landing page, screenshots, tagline, first comment
  3. Hunter: Self-hunt or Top Hunter (optional but helps)

30-Day Preparation Plan

PhaseDaysActions
Teaser30-21Build "notify me" page; decide self-hunt vs hunter; engage in community
Supporters20-11Build list of 200+ (makers, industry contacts, followers, users)
Assets10-3Finalize tagline (<=60 chars), gallery images (1270x760), demo video (<2 min), maker comment, 3-5 topic tags; build awareness on X/LinkedIn 2-4 weeks before
Launch day2-1Clear calendar for 16+ hours; Product Hunt runs midnight-midnight Pacific

Product Hunt Fields

FieldSpec
Tagline<=60 chars; no emojis unless part of product name; catchy, benefit-focused
Gallery1270x760 px recommended; readable, show product value
Demo video<2 minutes; optional but recommended
First commentPost immediately; story-driven, not feature list; significantly impacts engagement
Topic tags3-5 relevant; match Product Hunt taxonomy

Launch Day Strategy

PracticeGuideline
TimingTuesday-Thursday; 12:01am Pacific works best
NarrativeCreate story (problem -> solution), not feature list
EngagementReply to every comment; thank supporters; answer questions
AvoidBegging for upvotes (risk of shadowban)

Principle: Product Hunt is a visibility amplifier and credibility boost -- not primarily a customer acquisition channel.

Realistic Expectations

OutcomeUpvotesPlacement
Poor50-100--
Average200-400Top 10
Good500-800Top 5
Great800+Product of the Day

Beyond Listing

OfferingUse When
Product Hunt DailyNewsletter feature; high-intent audience
Social promotionPH shares on X, LinkedIn; launch-day amplification
Featured placementPaid promotion options

Post-Launch

  • Continue engaging with new users
  • Thank-you emails to supporters
  • Ask for feedback
  • Publish "lessons learned" blog post / X thread (week 1)
  • Follow up with interested users from comments (week 2)
  • Check eligibility for "Product of the Week/Month" (month 1)

Output Format

  • Readiness checklist (tagline, gallery, first comment, topic tags)
  • First comment draft (story-driven)
  • Tagline options (<=60 chars)
  • 30-day timeline (if planning ahead)

Related Skills

  • product-hunt-launch: Tactical PH optimization (gallery framework, tagline formulas, maker comment structure, common mistakes)

Follow output preferences from USER.md (language, format, platform constraints).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.