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-08-25
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.

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

JiayiV
JiayiV/question_mixing

webmcpify

Make a web app agent-ready — propose a WebMCP tool manifest, integrate, verify in a real browser, heal; unrelated code stays untouched. Use for "webmcpify", "add WebMCP", or "expose app actions to AI agents".

★ 0
JiayiV
JiayiV/question_mixing

vardoger-analyze

Use when the user asks to personalize the GitHub Copilot CLI assistant, adapt Copilot to their style, use vardoger, or analyze their Copilot CLI conversation history. Reads the local session directory at `~/.copilot/session-state/`, extracts recurring preferences and conventions, and writes a fenced personalization block into `~/.copilot/copilot-instructions.md`. Runs entirely on the user's machine via the local `vardoger` CLI (`pipx install vardoger`); no network calls and no uploads. Triggers: 'personalize my copilot', 'analyze my copilot history', 'tailor copilot to me', 'run vardoger', 'update my copilot instructions from history', 'make copilot learn my style'.

★ 0
JiayiV
JiayiV/question_mixing

transloadit-media-processing

Process media files (video, audio, images, documents) using Transloadit. Use when asked to encode video to HLS/MP4, generate thumbnails, resize or watermark images, extract audio, concatenate clips, add subtitles, OCR documents, or run any media processing pipeline. Covers 86+ processing robots for file transformation at scale.

图像与多媒体Skill与智能体开发
★ 0
JiayiV
JiayiV/question_mixing

terraform-azurerm-set-diff-analyzer

Analyze Terraform plan JSON output for AzureRM Provider to distinguish between false-positive diffs (order-only changes in Set-type attributes) and actual resource changes. Use when reviewing terraform plan output for Azure resources like Application Gateway, Load Balancer, Firewall, Front Door, NSG, and other resources with Set-type attributes that cause spurious diffs due to internal ordering changes.

运维与部署
★ 0
JiayiV
JiayiV/question_mixing

technical-job-search

Use this skill when a software engineer asks for help with job search tasks: parsing or analyzing a job description, tailoring a CV/resume, writing a cover letter, evaluating a job offer, or drafting a post-interview follow-up email. Do not activate for general career advice unrelated to an active job search action.

内容创作者人力资源写作与文案
★ 0
JiayiV
JiayiV/question_mixing

steno-mode

Shorthand-first response compression that cuts ~40% of response tokens while preserving technical precision and exact literals. Use when the user says "steno mode", "shorthand mode", "compressed responses", "token reduction", "brief structured output", or invokes /steno. Supports four compression levels: lite, brief, court, machine. Do not trigger for requests needing polished prose such as onboarding/tutorial content, stakeholder or customer-facing copy, or teaching-focused explanations.

★ 0