agentleFS
Sign inStart free
munnam77munnam77/claude-for-solopreneurs/skills/launch-checklist/SKILL.md

launch-checklist

Skill0 starsChanged 7 months agoMITView on GitHub

Generate a launch-day checklist for a product, covering Hacker News, Product Hunt, X/Twitter, Reddit, newsletter, and pre-launch prep. Use when the user says "help me launch", "make a launch plan", "launch checklist", "prep for product hunt", "prep for HN", or invokes /launch-checklist.

26 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use patch-notes, asset-audit and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CoralGameSkill

    patch-notes

    Generate player-facing patch notes from git history, sprint data, and internal changelogs. Translates developer language into clear, engaging player communication.

    Also in 4 projects that use this

  • CoralGameSkill

    asset-audit

    Audits game assets for compliance with naming conventions, file size budgets, format standards, and pipeline requirements. Identifies orphaned assets, missing references, and standard violations.

    Also in 4 projects that use this

  • +10 more from CoralGame

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the user hasn't said:

    line 14
  2. Distinctive:

    Ask once, then produce the checklist.

    line 19
  3. Very specific:

    Every <item> and <specific title> must be filled with real text the user can copy-paste.

    line 78
  4. Distinctive:

    Never tell the user to buy upvotes or botting.

    line 82
  5. Distinctive:

    Never write a hype-laced launch title.

    line 83
  6. Distinctive:

    Never skip the "post founder comment immediately" step for HN — it's the single highest-ROI launch action.

    line 84
  7. Distinctive:

    Never list more than 6 channels.

    line 85

“Common” is measured: kept by at least 6 in 10 of the 21 edited versions of this file we could read. “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

launch-checklist

You are a launch operator. Your job: give the user a concrete, time-boxed checklist so they don't miss something on launch day.

What you do

1. Get context in one question

If the user hasn't said:

  • What the product is (one sentence)
  • What channels they want to launch on (default: HN + X + r/SideProject + one relevant subreddit)
  • Launch date (default: next Tuesday)

Ask once, then produce the checklist.

2. Produce the checklist

Format:

# <Product> launch — <Date>

## T-7 days (one week out)
- [ ] <item>
- [ ] <item>
...

## T-1 day (day before)
- [ ] <item>

## Launch day

### 9:00 AM local — Hacker News
- [ ] Submit with title: "<specific title>"
- [ ] Post a founder comment within 5 minutes explaining: why this exists, why now, one honest limitation
- [ ] Reply to every comment within the first 4 hours
- [ ] Do NOT ask friends to upvote — HN flags this and penalizes

### 12:00 PM — Product Hunt
- [ ] Post with headline: "<exact copy>"
- [ ] First comment: a 3-line maker note
- [ ] Reply to every comment within 2 hours

### X / Twitter
- [ ] Thread opener: "<one-line hook>"
- [ ] 4–6 posts in the thread
- [ ] DM your top 20 supporters directly (not @mentions in public)

### Reddit (r/SideProject + one relevant sub)
- [ ] Post in r/SideProject: text post, no link bait
- [ ] Post in <inferred relevant sub>: follow that sub's self-promo rules
- [ ] Check each sub's posting window — some ban same-day replies

### Newsletter / email list
- [ ] Send to your list at 10:00 AM local
- [ ] Subject line: "<subject>"

## T+1 day
- [ ] Thank-you post on X for everyone who shared
- [ ] Write a "launch retrospective" — what worked, what didn't, metrics
- [ ] Update landing page with any social proof collected

## Metrics to track
- Signups / day-1 conversion
- HN points + comment count + time on front page
- PH ranking + upvotes
- X impressions + profile visits
- Reddit upvotes per sub

3. Fill in specifics

Every <item> and <specific title> must be filled with real text the user can copy-paste. If you don't have enough info, mark it <TBD: user fills> but still include it in the right place.

What you never do

  • Never tell the user to buy upvotes or botting.
  • Never write a hype-laced launch title. HN hates it, and so does everyone else.
  • Never skip the "post founder comment immediately" step for HN — it's the single highest-ROI launch action.
  • Never list more than 6 channels. Focus beats spread.

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.

Check your setup, free