Launch Strategy

Helps plan product launches, feature announcements, and release strategies using a phased, multi-channel approach. Covers owned, rented, and borrowed channels; pre-launch, launch day, and post-launch phases; and includes readiness scoring to gate launch dates. Use when planning any product release, considering Product Hunt, or building go-to-market momentum.

skills.sh installs: 648
GitHub stars: 29.5K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add alirezarezvani/claude-skills --skill launch-strategy --agent claude-code

Installs into .claude/skills of the current project.

Files

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.

SKILL.md on GitHub