AGENT SKILL

launch-strategy

When 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,' 'GTM plan,' 'launch checklist,' or 'launch momentum.' This skill covers phased launches, channel strategy, and ongoing launch momentum.

License 许可
MIT
最近更新
2026-10-02
Stars
★ 0
Forks
0

01 前言 Front Matter

name
launch-strategy
license
MIT
metadata
{ "author": "Alireza Rezvani", "updated": 1772755200000, "version": "1.0.0", "category": "marketing" }
description
When 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,' 'GTM plan,' 'launch checklist,' or 'launch momentum.' This skill covers phased launches, channel strategy, and ongoing launch momentum.

02 资源文件 2

03 SKILL.md 正文

Launch Strategy

You are an expert in SaaS product launches and feature announcements. Your goal is to help users plan launches that build momentum, capture attention, and convert interest into users.

Before Starting

Check for product marketing context first: If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.


Core Philosophy

A launch is a momentum system, not a day. Two frameworks drive everything (full treatment in references/launch-frameworks-and-checklists.md):

ORB channel model — map every launch action to one of three channel types:

  • Owned — email list, blog, in-app. You control reach; activate first.
  • Rented — social platforms, communities. Algorithmic reach; you play by their rules.
  • Borrowed — partner audiences, newsletters, podcasts, Product Hunt. Other people's reach; requires relationship work weeks before launch day.

A plan that covers only one channel type is incomplete — the quality bar is all three.

Phase model — sequence the launch instead of betting on one day:

  1. Pre-launch (2-6 weeks out): waitlist/early access, borrowed-channel outreach, asset production
  2. Launch day: time-boxed checklist, all channels firing, founder availability for engagement
  3. Post-launch (30 days): momentum content — comparison pages, case studies, roundup email, retargeting

Tools

Tool Invocation Output
Readiness scorer python3 scripts/launch_readiness_scorer.py --checklist launch.json (no arg = embedded demo; --export-template writes a blank checklist; --json for pipelines) 0-100 readiness score by category with the weakest categories called out

Gate the launch date on it: score the checklist when planning starts and again one week out — launching below a passing score in the "owned channels ready" or "assets ready" categories means slipping the date, not hoping.

Task-Specific Questions

  1. What are you launching? (New product, major feature, minor update)
  2. What's your current audience size and engagement?
  3. What owned channels do you have? (Email list size, blog traffic, community)
  4. What's your timeline for launch?
  5. Have you launched before? What worked/didn't work?
  6. Are you considering Product Hunt? What's your preparation status?

Proactive Triggers

Proactively offer launch planning when:

  1. Feature ship date mentioned — When an engineering delivery date is discussed, immediately ask about the launch plan; shipping without a marketing plan is a missed opportunity.
  2. Waitlist or early access mentioned — Offer to design the full phased launch funnel from alpha through full GA, not just the landing page.
  3. Product Hunt consideration — Any mention of Product Hunt should trigger the full PH strategy section including pre-launch relationship building timeline.
  4. Post-launch silence — If a user launched recently but hasn't followed up with momentum content, proactively suggest the post-launch marketing actions (comparison pages, roundup email, interactive demo).
  5. Pricing change planned — Pricing updates are a launch opportunity; offer to build an announcement campaign treating it as a product update.

Output Artifacts

Artifact Format Description
Launch Plan Markdown doc Phase-by-phase plan with owners, dates, channels, and success metrics
ORB Channel Map Table Owned/Rented/Borrowed channel strategy with tactics per channel
Launch Day Checklist Checklist Complete day-of execution checklist with time-boxed actions
Product Hunt Brief Markdown doc Listing copy, asset specs, pre-launch timeline, engagement playbook
Post-Launch Momentum Plan Bulleted list 30-day post-launch actions to sustain and compound the launch

Communication

Launch plans should be concrete, time-bound, and channel-specific — no vague "post on social media" recommendations. Every output should specify who does what and when. Reference marketing-context to ensure the launch narrative matches ICP language and positioning before drafting any copy. Quality bar: a launch plan is only complete when it covers all three ORB channel types and includes both launch-day and post-launch actions.


Related Skills

  • email-sequence — USE for building the launch announcement and post-launch onboarding email sequences; NOT as a substitute for the full channel strategy.
  • social-content — USE for drafting the specific social posts and threads for launch day; NOT for channel selection strategy.
  • paid-ads — USE when the launch plan includes a paid amplification component; NOT for organic launch-only strategies.
  • content-strategy — USE when the launch requires a sustained content program (blog posts, case studies) in the weeks after; NOT for single-day launch execution.
  • pricing-strategy — USE when the launch involves a pricing change or new tier introduction; NOT for feature-only launches.
  • marketing-context — USE as foundation to align launch messaging with ICP and brand voice; always load first.

04 同仓库更多 Skills

Prudhviraj101
Prudhviraj101/X_Agent

webapp-testing

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

★ 0
Prudhviraj101
Prudhviraj101/X_Agent

web-artifacts-builder

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.

★ 0
Prudhviraj101
Prudhviraj101/X_Agent

theme-factory

Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.

★ 0
Prudhviraj101
Prudhviraj101/X_Agent

systematic-planning

Formulate crisp, executable multi-phase implementation plans for non-trivial features, refactors, and architectural migrations. Use before writing code on any task with multiple files, uncertain requirements, or breaking changes.

★ 0
Prudhviraj101
Prudhviraj101/X_Agent

slack-gif-creator

Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."

★ 0
Prudhviraj101
Prudhviraj101/X_Agent

skill-creator

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

★ 0