Startup Launch Day Playbook — Hour-by-Hour Checklist
Startup Launch Day Playbook — Hour-by-hour execution checklist for your big launch day.
How to use it
Claude Code
- Run the line below. It pulls the whole folder into
~/.claude/skills/startup-launch. - Describe your job in plain words. Claude Code follows the skill from there.
Claude Code — installs the whole folder, not just SKILL.md
npx degit Gingiris-1031/gingiris-skills/skills/startup-launch#main ~/.claude/skills/startup-launchFor one project only, change the path to .claude/skills/startup-launch.
Claude (web or desktop app)
- On this page open ⋯ → Download .md.
- Save it as SKILL.md in a folder, zip the folder, then Customize → Skills → + → Create skill → Upload a skill.
- Pick the file and Save. Claude shows the name and description and runs a security scan.
- Check the skill is switched on.
- Start a new chat and describe your job in plain words. The AI follows the skill from there.
ChatGPT or another app
- ChatGPT: make a Project and paste it into Instructions.
- Neither? Paste it at the top of a new chat — it works for that chat.
Not working?
- Check which app you pasted it into — the steps above name the right one.
- Some skills need the paid tier of Claude or ChatGPT.
Paste into Claude, ChatGPT or Cursor.
Source of Startup Launch Day Playbook — Hour-by-Hour Checklist
Show the full text84 lines
| name | description | source | tags |
|---|---|---|---|
| startup-launch | | Startup Launch Day Playbook — Hour-by-hour execution checklist for your big launch day. Covers timezone timing, channel sequencing, real-time crisis management, and post-launch momentum. By @WeiYipei. | https://github.com/Gingiris-1031/gingiris-skills/tree/main/skills/startup-launch | - startup-launch - launch-strategy - go-to-market - gtm - product-launch - mvp - traction - first-users - early-stage - distribution - claude-code - ai-agent-skill - agent-skill - latest |
⚠️ 区分 B2B 与 2C
本 skill 默认偏 dev / 开源 / B2B SaaS。若产品是 2C 消费品 / 教育 / 应用 / 游戏：核心指标换成 D1/D7/D30 留存、激活率、病毒系数 K（非 MRR/CAC/LTV）；冷启动渠道换成垂类社区 / 短视频 / 垂直 KOL（非 PH/HN/LinkedIn）。完整 2C 适配指南 + 各国渠道公开数据见 → gingiris-seo-geo/references/2c-adaptation.md。
Startup Launch Day Playbook — Hour-by-Hour Checklist
📦 Install
clawhub install startup-launch
What you get after installing:
- Hour-by-hour execution plan from T-12h to 72h post-launch
- Coordinated multi-channel activation sequence
- Crisis management playbook (site down, negative feedback, competitor attacks)
Your launch day is ONE shot. This playbook gives you an hour-by-hour execution plan so nothing falls through the cracks. From T-minus-12-hours prep to the 72-hour post-launch sprint.
What You'll Learn
- T-12h: Final checks (servers, links, payment, copy)
- Hour 0: Coordinated channel activation sequence
- Hours 1-6: Real-time monitoring and engagement tactics
- Hours 6-24: Second-wave amplification
- 72-hour post-launch momentum playbook
- Crisis management (site down, negative feedback, competitor attacks)
Who This Is For
- Founders with a launch date already set
- Teams who have the product ready but need execution confidence
- Anyone who's been burned by a disorganized launch before
Traffic Engineering for Launch Day (2026 field addendum)
Plan the day as arithmetic, not vibes
Fix a total-visits target, then reverse-engineer per-channel quotas — each with its own UTM short link and a named owner. Anonymized reference (an AI Agent product, late 2025): a 500K-visit launch day was assembled as ~400K from 40 creator quote-tweets, plus ~20K each from Reddit threads, geo-targeted YouTube ads, and messaging-group distribution. Final tally: ~800 signups at $6.25 per registration. The lesson cuts both ways — traffic is buildable to spec; conversion is the bottleneck you can't buy.
Sequencing patterns worth stealing
- Split objectives across two days: half your amplifiers push the website on day one, the other half push the leaderboard (PH, etc.) on day two. One day, one goal — otherwise the streams dilute each other.
- Burst window: get 50–100 creators publishing inside the same 24–48h. Algorithms reward density, not totals.
- Platform relay (from the Manus/Devin post-mortems): days 0–3, X/Twitter builds the conversation → days 3–10, YouTube and newsletters consolidate it → day 10+, Reddit/HN carry the long tail. For a big launch, concentrate ~80% of spend on the same day.
Hacker News: the 30-minute verdict
The front page is decided in the first half hour — roughly 30 points and 10 comments, posted during the US morning window. Flat at minute 40 = done. Bring 2–3 prepared angles (a "Show" post, an open-source-alternative link, a how-it-works writeup) rather than one perfect post, and translate the winner for regional dev forums — one text, two communities.
Readiness gate
Don't set the date until at least 10 external developers are satisfied and still actively using the product. Pre-launch time split: 60% talking to users, 40% preparing the launch — start asset prep once the product hits "60 points," copy first, visuals later.
Built by Gingiris — orchestrated 30+ launches with combined 100k+ first-day visitors.
| 1 | |
| 2 | name startup-launch |
| 3 | description | |
| 4 | Startup Launch Day Playbook — Hour-by-hour execution checklist for your big launch day. Covers timezone timing, channel sequencing, real-time crisis management, and post-launch momentum. By @WeiYipei. |
| 5 | source https://github.com/Gingiris-1031/gingiris-skills/tree/main/skills/startup-launch |
| 6 | tags |
| 7 | - startup-launch |
| 8 | - launch-strategy |
| 9 | - go-to-market |
| 10 | - gtm |
| 11 | - product-launch |
| 12 | - mvp |
| 13 | - traction |
| 14 | - first-users |
| 15 | - early-stage |
| 16 | - distribution |
| 17 | - claude-code |
| 18 | - ai-agent-skill |
| 19 | - agent-skill |
| 20 | - latest |
| 21 | |
| 22 | |
| 23 | ## ⚠️ 区分 B2B 与 2C |
| 24 | |
| 25 | 本 skill 默认偏 dev / 开源 / B2B SaaS。若产品是 **2C 消费品 / 教育 / 应用 / 游戏**：核心指标换成 D1/D7/D30 留存、激活率、病毒系数 K（非 MRR/CAC/LTV）；冷启动渠道换成垂类社区 / 短视频 / 垂直 KOL（非 PH/HN/LinkedIn）。完整 2C 适配指南 + 各国渠道公开数据见 → `gingiris-seo-geo/references/2c-adaptation.md`。 |
| 26 | |
| 27 | |
| 28 | |
| 29 | # Startup Launch Day Playbook — Hour-by-Hour Checklist |
| 30 | |
| 31 | > 🌍 **Language / 语言**: [中文] | [English] | [日本語] | [한국어] |
| 32 | |
| 33 | ## 📦 Install |
| 34 | |
| 35 | |
| 36 | clawhub install startup-launch |
| 37 | |
| 38 | |
| 39 | **What you get after installing:** |
| 40 | Hour-by-hour execution plan from T-12h to 72h post-launch |
| 41 | Coordinated multi-channel activation sequence |
| 42 | Crisis management playbook (site down, negative feedback, competitor attacks) |
| 43 | |
| 44 | |
| 45 | |
| 46 | Your launch day is ONE shot. This playbook gives you an hour-by-hour execution plan so nothing falls through the cracks. From T-minus-12-hours prep to the 72-hour post-launch sprint. |
| 47 | |
| 48 | ## What You'll Learn |
| 49 | T-12h: Final checks (servers, links, payment, copy) |
| 50 | Hour 0: Coordinated channel activation sequence |
| 51 | Hours 1-6: Real-time monitoring and engagement tactics |
| 52 | Hours 6-24: Second-wave amplification |
| 53 | 72-hour post-launch momentum playbook |
| 54 | Crisis management (site down, negative feedback, competitor attacks) |
| 55 | |
| 56 | ## Who This Is For |
| 57 | Founders with a launch date already set |
| 58 | Teams who have the product ready but need execution confidence |
| 59 | Anyone who's been burned by a disorganized launch before |
| 60 | |
| 61 | ## Traffic Engineering for Launch Day (2026 field addendum) |
| 62 | |
| 63 | ### Plan the day as arithmetic, not vibes |
| 64 | |
| 65 | Fix a total-visits target, then reverse-engineer per-channel quotas — each with its own UTM short link and a named owner. Anonymized reference (an AI Agent product, late 2025): a 500K-visit launch day was assembled as ~400K from 40 creator quote-tweets, plus ~20K each from Reddit threads, geo-targeted YouTube ads, and messaging-group distribution. Final tally: ~800 signups at $6.25 per registration. The lesson cuts both ways — traffic is buildable to spec; conversion is the bottleneck you can't buy. |
| 66 | |
| 67 | ### Sequencing patterns worth stealing |
| 68 | |
| 69 | **Split objectives across two days**: half your amplifiers push the website on day one, the other half push the leaderboard (PH, etc.) on day two. One day, one goal — otherwise the streams dilute each other. |
| 70 | **Burst window**: get 50–100 creators publishing inside the same 24–48h. Algorithms reward density, not totals. |
| 71 | **Platform relay** (from the Manus/Devin post-mortems): days 0–3, X/Twitter builds the conversation → days 3–10, YouTube and newsletters consolidate it → day 10+, Reddit/HN carry the long tail. For a big launch, concentrate ~80% of spend on the same day. |
| 72 | |
| 73 | ### Hacker News: the 30-minute verdict |
| 74 | |
| 75 | The front page is decided in the first half hour — roughly 30 points and 10 comments, posted during the US morning window. Flat at minute 40 = done. Bring 2–3 prepared angles (a "Show" post, an open-source-alternative link, a how-it-works writeup) rather than one perfect post, and translate the winner for regional dev forums — one text, two communities. |
| 76 | |
| 77 | ### Readiness gate |
| 78 | |
| 79 | Don't set the date until **at least 10 external developers are satisfied and still actively using the product**. Pre-launch time split: 60% talking to users, 40% preparing the launch — start asset prep once the product hits "60 points," copy first, visuals later. |
| 80 | |
| 81 | |
| 82 | |
| 83 | Built by Gingiris — orchestrated 30+ launches with combined 100k+ first-day visitors. |
| 84 |
Discussion
AI Product Launch PlaybookLaunch your AI product to global attention — the playbook behind Manus, Devin, and AFFiNE's breakout launches. Covers AI-specific GTM strategy, hype cycle management, waitlist tactics, and multi-market rollout for maximum day-one impact.Shipping and launchPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Launch StrategyWhen the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'how do I launch this,' 'launch checklist,' 'GTM plan,' or 'we're about to ship.' Use this whenever someone is preparing to release something publicly. For ongoing marketing after launch, see marketing-ideas. For the offer being launched (bonuses, guarantees, scarcity, naming), see offers.PacsomaticOperator toolkit for nf-core/pacsomatic matched tumor-normal workflows from BAM inputs. Use this skill when the user needs to validate run inputs, generate pacsomatic-compliant samplesheets, prepare reproducible Nextflow launch artifacts, run locally or submit to schedulers (LSF/Slurm/PBS/SGE), and triage execution failures. Triggers on requests to run pacsomatic, prepare launch commands/scripts, perform dry-run checks, or troubleshoot pipeline startup and scheduler submission errors.
Browse more free Claude skills or everything in Product.