Use this skill whenever the user wants to launch their product, get first users, write a launch post, promote their project, post on Reddit or Hacker News or Indie Hackers, find their first customers, or prepare for launch day. Also trigger when the user says "I deployed, now what?", "how do I get users?", "nobody knows my product exists", "where should I post this?", "write me a launch post", or "I want to start charging." Use this even if the user only mentions one platform — the skill generates posts for all relevant platforms.
Help the user get their first real users (and ideally first revenue) within 24-48 hours of deploying.
This skill generates a complete launch plan:
The skill automates content generation and planning. The user handles all posting, commenting, and conversations — these must be human.
Read PROJECT.md for:
Check if the user has a feedback log from Issue 06. If yes, read it — tester quotes and validated features make launch posts more credible.
Check for existing payment integration. If none exists, flag it as optional but recommended (see payment spec guidance at the end of this file).
Before generating any platform-specific posts, extract the core message. Ask the user to confirm or edit these four elements:
One-line description — What it does in under 15 words. Not what it is. What it does for the user.
The problem — One sentence about the pain. Use language from tester feedback if available.
The hook — What makes this different from existing solutions. Be specific.
The ask — What do you want people to do? Be explicit.
Present these to the user for confirmation before generating posts.
Read references/platform-guides.md for each platform's rules, norms, and formatting.
Generate posts for each relevant platform. Save all posts to /launch/posts/. Each post is a separate markdown file the user can copy from.
Identify 2-3 subreddits based on the product's domain. Read references/platform-guides.md → Reddit section for subreddit-specific rules.
For each subreddit, generate a post that:
Save to /launch/posts/reddit-[subreddit].md
Generate a Show HN post:
Save to /launch/posts/hackernews.md
Generate an Indie Hackers post:
Save to /launch/posts/indiehackers.md
Generate a launch thread (5-7 tweets):
Save to /launch/posts/twitter-thread.md
Flag: Product Hunt launches benefit from preparation (hunter, maker profile, assets). If the user wants PH, suggest scheduling it for a future date and focusing on Reddit/HN/IH for immediate launch.
Create outreach messages for three scenarios:
For Issue 06 testers (warm — they already know the product):
Hey [name] — remember when you tested [product] and said [specific feedback]?
I fixed that and it's live now: [URL]. Would love for you to check out
the final version. If it solves your problem, I'd be grateful for a
mention/upvote when I post the launch [on reddit/HN/etc] later today.
For new contacts found via community research:
Hey — saw your [post/comment] about [their specific problem]. I just
launched something that might help: [one-sentence description].
It's free to try: [URL]. Would love your take on it.
For follow-up after someone engages with a launch post:
Thanks for [commenting/upvoting/checking it out]! If you have
2 minutes, I'd love to know: did it actually solve the problem,
or is something missing? Building this based on real feedback.
Save to /launch/posts/dm-templates.md
Copy assets/launch-tracker.md to /launch/launch-tracker.md.
This file tracks:
The user fills this in throughout launch day. It becomes the data source for deciding what worked and where to focus ongoing promotion.
Based on the platforms selected and the user's timezone, generate a launch day schedule:
LAUNCH DAY TIMELINE
[Morning — preparation]