
Launch Strategy
FreePlan effective product launches and announcements.
Free · Opens the source repo
What Launch Strategy does
The Launch Strategy skill is designed to assist users in planning and executing successful product launches, feature announcements, and release strategies. By leveraging a structured approach, this skill guides users through the complexities of launch planning, ensuring that they build momentum, capture attention, and convert interest into users. It emphasizes that a launch is a momentum system rather than a single event, advocating for a phased approach that includes pre-launch, launch day, and post-launch activities.
Central to the skill's methodology are two key frameworks: the ORB channel model and the phase model. The ORB channel model categorizes launch actions into three types: Owned, Rented, and Borrowed channels. This ensures that users engage with all available resources effectively, rather than relying on a single channel type. The phase model outlines a timeline for launches, detailing activities that should occur weeks in advance, on launch day, and in the weeks following the launch to maintain momentum.
To facilitate planning, the skill includes a readiness scorer tool, which evaluates the user's launch preparedness across various categories. This allows users to gauge their readiness and make necessary adjustments before the launch date. The skill also provides structured output artifacts, including a comprehensive launch plan, channel strategy maps, and checklists tailored to the specific phases of the launch process. These outputs are designed to be actionable and specific, ensuring clarity in roles and timelines.
This skill is ideal for product managers, marketers, and teams looking to optimize their launch processes and maximize the impact of their announcements. By following the structured guidance provided, users can avoid common pitfalls and ensure a well-coordinated launch effort that resonates with their target audience.
When to use it
Use this skill when preparing for a product launch, feature release, or any announcement that requires a strategic approach.
When not to use it
This skill may not be suitable for informal or spontaneous announcements that do not require a structured launch strategy.
What you can build with it
Planning a New Product Launch
When preparing to launch a new SaaS product, use this skill to create a detailed launch plan that covers all necessary channels.
Feature Announcement Strategy
If you're announcing a major feature update, this skill helps ensure that your launch is well-coordinated and impactful.
Post-Launch Engagement
After a recent launch, utilize the skill to develop a post-launch momentum plan to keep user engagement high.
How to install Launch Strategy
View source1. Install with the skills CLI
npx skills add alirezarezvani/claude-skills/launch-strategy --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by alirezarezvaniLaunch 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:
- Pre-launch (2-6 weeks out): waitlist/early access, borrowed-channel outreach, asset production
- Launch day: time-boxed checklist, all channels firing, founder availability for engagement
- 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
- What are you launching? (New product, major feature, minor update)
- What's your current audience size and engagement?
- What owned channels do you have? (Email list size, blog traffic, community)
- What's your timeline for launch?
- Have you launched before? What worked/didn't work?
- Are you considering Product Hunt? What's your preparation status?
Proactive Triggers
Proactively offer launch planning when:
- 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.
- Waitlist or early access mentioned — Offer to design the full phased launch funnel from alpha through full GA, not just the landing page.
- Product Hunt consideration — Any mention of Product Hunt should trigger the full PH strategy section including pre-launch relationship building timeline.
- 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).
- 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.
Frequently asked questions about Launch Strategy
Similar skills
Competitive Analysis
Build detailed competitive landscape decks efficiently.
Brand Discovery
Structured interviews to articulate brand identity.
CrossFrame Org
Facilitates structured organizational analysis and repair.
Technical Product Pricing
Optimize your pricing strategy for technical products.
Product-Led Growth
Optimize your go-to-market strategy with data-driven insights.
Positioning Strategy
Own your market position with clear differentiation.
