Plans a comprehensive product launch or feature release strategy using the ORB channel model (Owned, Rented, Borrowed) and a phased timeline (pre-launch, launch day, post-launch). It produces concrete artifacts like launch plans, channel maps, checklists, and Product Hunt briefs to build momentum and convert interest.
Say it in your own words; the assistant finds this recipe by itself. Examples:
Use this skill when the user needs to plan the overall strategy for releasing a new product, a major feature, or a significant update. It is appropriate when the user mentions 'launch,' 'GTM,' 'Product Hunt,' or 'early access' and needs a structured, phased plan covering multiple channels. It is also used when the user wants to ensure they have a post-launch momentum plan to sustain interest after the initial announcement.
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.
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.
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
| 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.
Proactively offer launch planning when:
| 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 |
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.
LICENSESKILL.mdreferences/launch-frameworks-and-checklists.mdscripts/launch_readiness_scorer.pyVendored from alirezarezvani/claude-skills, commit 27cfcd0fb0a4, path marketing-skill/skills/launch-strategy, licence MIT. The upstream licence file ships inside the skill.