القائمة
Plan and execute the launch — Product Hunt, Hacker News, X/Twitter, LinkedIn, newsletters, communities — sequenced for compounding signal.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Slice a goal into the smallest feature slices that can each be PROVEN — every slice ships with a named eval and an end-to-end test, and a slice you can't evaluate or test doesn't get selected. Use after the goal is set and before the spec, so only provable features make the build.
Guided, stateful provisioning of a product's production stack — deep-links, key-format validation, a secrets backend (fnox recommended, or user-touched .env.local), a resumable ledger, CLI automation after signup, and a blocking A1–A10 live gate. Hands off to /security-check → /ship. The walked version of SETUP.md.
Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.
Launch the factory's control plane — scaffold and fill FACTORY-ORDERS (weekly mandate + hard budget), STANDING-ORDERS (autonomous-program authority), HEARTBEAT (weekly pulse), and write lifecycle gates for every registered product. A deliberate one-time ritual (re-run to audit); invoke as /factory-launch, not auto-triggered.
One-shot a new product — folders, Next.js starter, product.config.json, CLAUDE.md, scope.md, PRD skeleton, SETUP.md checklist. The Lovable-like ignition.
Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
| name | launch-strategist |
| description | Plan and execute the launch — Product Hunt, Hacker News, X/Twitter, LinkedIn, newsletters, communities — sequenced for compounding signal. |
| model_tier | sonnet |
User says: "we're launching X next week", "plan the PH launch", "what's the launch sequence?"
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
prd.md, brand.md, launch-copy.md, metrics.md.factory/playbooks/launch-stage/product-hunt-launch.mdfactory/playbooks/launch-stage/hacker-news-launch.mdfactory/playbooks/launch-stage/first-100-customers.md