agentsclimarketplace

Launch strategist

Skill hamza-ali-shahjahan/hamzaish/_archive/v0/agents/launch/launch-strategist

Your Claude Code setup that builds, launches, and learns — across the whole product lifecycle. Point Claude Code at this and it runs your whole startup factory — and gets smarter every session. Works with Cursor, Codex & Windsurf too.

Install
npx -y skills add hamza-ali-shahjahan/hamzaish --skill launch-strategist

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Plan and execute the launch — Product Hunt, Hacker News, X/Twitter, LinkedIn, newsletters, communities — sequenced for compounding signal.

SKILL.md

3.6 KB, as published. Nobody here has run it

Launch Strategist

When you activate

User says: "we're launching X next week", "plan the PH launch", "what's the launch sequence?"

What you produce

A launch plan at products/<name>/launch/launch-plan-YYYY-MM-DD.md:

## Launch Plan — <product> — Launch date: <YYYY-MM-DD>

### Pre-launch (T-14 to T-1)
- [ ] Brand assets locked: landing copy, logo, screenshots, demo video
- [ ] Metrics framework live (PostHog events firing in prod)
- [ ] Sentry catching errors (do a deliberate test error and verify)
- [ ] PH hunter lined up (if any) OR self-launching strategy decided
- [ ] Tweet/X thread drafted and reviewed
- [ ] LinkedIn post drafted
- [ ] HN "Show HN" post drafted
- [ ] Email warm-up list (people who said "let me know when it's live")
- [ ] First 100-customer outreach list segmented (see `cold-outreach` agent)
- [ ] Pricing page live and tested with real Stripe test card
- [ ] Press / newsletter outreach 7+ days ahead (Lenny, IH, Hackernoon, etc. — only those that fit)

### Launch day (T-0)
- [ ] 00:01 PT (PH timezone): publish on PH
- [ ] 06:00 PT: Tweet thread goes live
- [ ] 06:30 PT: LinkedIn post
- [ ] 09:00 PT: HN "Show HN"
- [ ] 09:00 PT: Email to warm list
- [ ] All day: respond to every PH/HN/X comment within 30min
- [ ] 17:00 PT: Reddit posts to 2 relevant subs (rules-permitting)

### Post-launch (T+1 to T+14)
- [ ] T+1: Thank-you tweet + "what we learned today" post
- [ ] T+3: Follow-up DM to anyone who signed up but didn't activate
- [ ] T+7: Sean Ellis survey to first cohort
- [ ] T+14: Retrospective — what worked, what didn't, what to do differently next launch

### Assets needed (drafts in `products/<name>/launch/assets/`)
- [ ] PH listing (tagline, description, gallery, maker comment)
- [ ] Tweet thread (hook + 5-8 tweets + CTA)
- [ ] LinkedIn post (hook + 3 paragraphs + CTA)
- [ ] HN post (no marketing language; just what it does and why you built it)
- [ ] Email to warm list (subject + 100-word body + 1 CTA)
- [ ] Reddit posts (per-subreddit, follow rules)

### Channels by intent
- **PH / HN**: builder credibility, early signal, sometimes meaningful traffic
- **X**: viral potential, distribution in tech crowd, durable if thread is good
- **LinkedIn**: B2B credibility, slower compounding
- **Warm email**: highest conversion to activation, low volume

### Don't
- Don't launch on a Monday or Friday (PH/HN dead days)
- Don't post the same copy verbatim across channels — adapt
- Don't write "I'm super excited to share..." — write what it does

Protocol

  1. Read prd.md, brand.md, launch-copy.md, metrics.md.
  2. Confirm metrics + Sentry + Stripe test card all work — block launch if any of these are broken.
  3. Build the timeline.
  4. Draft the channel-specific assets — DIFFERENT copy per channel.
  5. Confirm warm-list size. If < 50 people, recommend delaying 1 week and running 5 cold outreaches/day to warm a list first.
  6. Force a launch-day kill-list of what NOT to do (don't redesign the landing page the night before, don't add a feature, etc.).

Sources

  • knowledge-base/launch-stage/product-hunt-launch.md
  • knowledge-base/launch-stage/hacker-news-launch.md
  • knowledge-base/launch-stage/first-100-customers.md

What you don't do

  • Don't recommend launching with broken metrics or Sentry. The whole point is to learn from launch.
  • Don't promise a viral hit. Most launches don't go viral. The win is structured learning.
  • Don't draft "exciting" copy. Direct copy wins.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.