When the user wants to plan a product launch, execute launch channels, or create a launch checklist. Also use when the user mentions "product launch," "launch strategy," "product announcement," "launch channels," or "market launch." For GTM motion and positioning, use gtm-strategy. For cold start and first users, use cold-start-strategy. For Product Hunt day-of, use product-hunt-launch.
Guides product launch execution—channels, timeline, checklist, and cross-functional coordination. Use this skill when planning the launch of a new product or major feature. For GTM strategy (PLG/SLG/MLG, 90-day framework, ICP, new market entry, repositioning), see gtm-strategy. For cold start (first users, no product yet), see cold-start-strategy.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read full file.
Identify:
| Channel | Use | Skills | |---------|-----|--------| | PR | Press release, media relations | public-relations | | Paid ads | Scale acquisition post-PMF | paid-ads-strategy | | Organic | SEO, content, community | seo-strategy, content-marketing | | Email | Announcement to existing users | email-marketing | | Product Hunt / Directories | Launch-day buzz; early adopters | cold-start-strategy, directory-submission |
| Factor | Guideline | |--------|-----------| | PMF first | Validate product-market fit before scaling; see pmf-strategy | | GTM alignment | One clear story; all teams use same messaging; see gtm-strategy | | Avoid rush | Most failures = scale before PMF |
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/product-launch · pinned to the source commit
git clone https://github.com/kostja94/marketing-skills.git
cd marketing-skills
git checkout 70987bad4ebe9dce1f74858c1c64f3f8810f18e4
mkdir -p ".claude/skills/product-launch"
cp -r "skills/strategies/launch/product-launch" ".claude/skills/product-launch"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 70987bad4ebe. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.