agentleFS
Sign inStart free
MoizIbnYousafMoizIbnYousaf/marketing-cli/skills/launch-strategy/SKILL.md

launch-strategy

Skill33 starsChanged 6 months agoMITView on GitHub

When the user wants to plan a product launch, feature announcement, release strategy, or go-to-market plan. Also use when the user mentions 'launch plan', 'go to market', 'GTM', 'Product Hunt', 'beta launch', 'how do I launch', 'pre-launch', 'launch checklist', 'distribution plan', 'release strategy', 'feature announcement', or is about to ship something and needs a distribution plan. Even vague requests like 'I'm almost done building, what now?' or 'how do I get users?' should trigger this skill. Make sure to use this whenever someone is planning ANY kind of product or feature release, even if they don't say 'launch' explicitly — if they're thinking about getting something in front of users, this is the skill. This is the STRATEGIC planner — for operational platform submissions and directory launches, see /startup-launcher instead.

We split this skill into the rules it gives an agent

23 rules. 11 are common, 8 are distinctive, and 4 are very specific to this project.

  • 11

    Common

    Most of the 62 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check if brand/ directory exists in the project root

    line 29
  2. Very specific:

    If it exists, read brand/voice-profile.md, brand/positioning.md, and brand/audience.md for context

    line 30
  3. Distinctive:

    Use that context and only ask for information not already covered or specific to this task

    line 31
  4. Distinctive:

    Before proceeding, determine which skill is appropriate:

    line 35
  5. Distinctive:

    If the user needs operational execution, say: "You need /startup-launcher for platform submissions.

    line 39
  6. Distinctive:

    Follow these phases in order.

    line 45
  7. Distinctive:

    Ask these questions (skip any already answered by brand/ files):

    line 49
  8. Very specific:

    Write marketing/launch/plan.md using this template:

    line 77
  9. Very specific:

    Write marketing/launch/checklist.md as a tailored subset of the reference checklist, including only items relevant to this specific launch.

    line 116
  10. Distinctive:

    No email sequences? → /email-sequences

    line 123
  11. Common:

    No algorithm changes or pay-to-play

    line 159
  12. Common:

    Use them to drive traffic to owned channels

    line 182
  13. Common:

    Don't rely on them as your only strategy

    line 183
  14. Distinctive:

    Use Exa MCP or firecrawl to find audience overlap

    line 204
  15. Distinctive:

    Ensure prototype is functional enough to demo

    line 227
  16. Common:

    Put the product in front of external users in a controlled way.

    line 232
  17. Common:

    Create landing page with early access signup form

    line 235
  18. Common:

    Start marketing with teasers about problems you solve

    line 247
  19. Common:

    Run user research with engaged users (incentivize with credits)

    line 264
  20. Common:

    Start charging (if not already)

    line 278
  21. Common:

    Treat it as an all-day event

    line 315
  22. Common:

    Follow up with everyone who engaged

    line 322
  23. Common:

    Add dedicated sections about the new feature/product across your site.

    line 342

“Common” is measured: kept by at least 6 in 10 of the 62 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Launch Strategy

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

On Activation

  1. Check if brand/ directory exists in the project root
  2. If it exists, read brand/voice-profile.md, brand/positioning.md, and brand/audience.md for context
  3. Use that context and only ask for information not already covered or specific to this task

Decision Gate

Before proceeding, determine which skill is appropriate:

  • This skill (/launch-strategy): Strategic planning — phased timeline, channel strategy, messaging, positioning. Use when the user needs a PLAN.
  • /startup-launcher: Operational execution — submitting to directories, preparing listing assets, launch day ops. Use when the user needs to DO the launch across platforms.

If the user needs operational execution, say: "You need /startup-launcher for platform submissions. This skill builds the strategic plan. Want the plan first, or jump straight to execution?"

Agent Workflow

Follow these phases in order. Do not skip phases.

Phase 1: Gather Context

Ask these questions (skip any already answered by brand/ files):

  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?

Phase 2: Classify the Launch

Based on context, classify:

Launch TypeSignalsApproach
New product, no audienceNo email list, no social, first launchFocus on Phase 1-3, borrowed channels, community seeding
New product, existing audienceHas email list or social followingFocus on Phase 3-5, owned channels first
Major feature updateExisting product, significant new capabilityAbbreviated timeline, existing user base + expansion
Minor updateBug fixes, small improvementsChangelog + email segment, skip full campaign

Phase 3: Build the Plan

Using the ORB Framework, Five-Phase Approach, and reference files, produce a plan tailored to the classification. Reference:

  • references/launch-timeline.md for week-by-week timeline
  • references/launch-checklist.md for the full pre-flight checklist

Phase 4: Write Deliverables

Write marketing/launch/plan.md using this template:

# Launch Plan: [Product/Feature Name]

## Overview
- **Launch type:** [New product / Major feature / Minor update]
- **Target date:** [Date]
- **Audience size:** [Current size]
- **Primary goal:** [Signups / Revenue / Awareness]

## Positioning
- **One-line value prop:** [From positioning.md or crafted here]
- **Launch angle:** [What makes this newsworthy NOW]
- **Target audience:** [Who, specifically]

## Channel Strategy (ORB)

### Owned Channels
[List with specific actions and dates]

### Rented Channels
[List with specific actions and dates]

### Borrowed Channels
[List with specific targets and outreach plan]

## Timeline
[Phased timeline using launch-timeline.md reference]

## Success Metrics
| Metric | Target | Measurement |
|--------|--------|-------------|
| [e.g., Day-1 signups] | [number] | [tool/method] |

## If Launch Stalls
[Contingency plan with specific triggers and responses]

Write marketing/launch/checklist.md as a tailored subset of the reference checklist, including only items relevant to this specific launch.

Phase 5: Handoff

Tell the user: "Launch plan written to marketing/launch/. Here's the summary: [2-3 sentences]. Suggested next steps: [specific skills]."

Recommend related skills based on gaps:

  • No email sequences? → /email-sequences
  • Landing page needs work? → /page-cro
  • Need comparison pages? → /competitor-alternatives
  • Need psychology for waitlists/exclusivity? → /marketing-psychology
  • Ready to submit to directories? → /startup-launcher

Core Philosophy

The best companies don't just launch once -- they launch again and again. Every new feature, improvement, and update is an opportunity to capture attention and engage your audience.

A strong launch isn't about a single moment. It's about:

  • Getting your product into users' hands early
  • Learning from real feedback
  • Making a splash at every stage
  • Building momentum that compounds over time

The ORB Framework

Structure your launch marketing across three channel types. Everything should ultimately lead back to owned channels.

Owned Channels

You own the channel (though not the audience). Direct access without algorithms or platform rules.

Examples:

  • Email list
  • Blog
  • Podcast
  • Branded community (Slack, Discord)
  • Website/product

Why they matter:

  • Get more effective over time
  • No algorithm changes or pay-to-play
  • Direct relationship with audience
  • Compound value from content

Start with 1-2 based on audience:

  • Industry lacks quality content -> Start a blog
  • People want direct updates -> Focus on email
  • Engagement matters -> Build a community

Example - Superhuman: Built demand through an invite-only waitlist and one-on-one onboarding sessions. Every new user got a 30-minute live demo. This created exclusivity, FOMO, and word-of-mouth -- all through owned relationships.

Rented Channels

Platforms that provide visibility but you don't control. Algorithms shift, rules change, pay-to-play increases.

Examples:

  • Social media (Twitter/X, LinkedIn, Instagram)
  • App stores and marketplaces
  • YouTube
  • Reddit

How to use correctly:

  • Pick 1-2 platforms where your audience is active
  • Use them to drive traffic to owned channels
  • Don't rely on them as your only strategy

Platform-specific tactics:

  • Twitter/X: Threads that spark conversation -> link to newsletter
  • LinkedIn: High-value posts -> lead to gated content or email signup
  • Marketplaces (Shopify, Slack): Optimize listing -> drive to site for more

Rented channels give speed, not stability. Capture momentum by bringing users into your owned ecosystem.

Borrowed Channels

Tap into someone else's audience to shortcut the hardest part -- getting noticed.

Examples:

  • Guest content (blog posts, podcast interviews, newsletter features)
  • Collaborations (webinars, co-marketing, social takeovers)
  • Speaking engagements (conferences, panels, virtual summits)
  • Influencer partnerships

Be proactive, not passive:

  1. List industry leaders your audience follows
  2. Pitch win-win collaborations
  3. Use Exa MCP or firecrawl to find audience overlap
  4. Set up affiliate/referral incentives

Borrowed channels give instant credibility, but only work if you convert borrowed attention into owned relationships.

ORB Prioritization Matrix

Audience SizeFocusWhy
< 1,000Owned channels only (blog, email list)Build foundation before spending on reach
1K - 10KOwned + Rented (social, SEO, ads)Enough audience to test paid channels
10K+All three: Owned + Rented + Borrowed (partnerships, press)Use existing reach for maximum amplification

Five-Phase Launch Approach

Phase 1: Internal Launch

Gather initial feedback and iron out major issues before going public.

Actions:

  • Recruit early users one-on-one to test for free
  • Collect feedback on usability gaps and missing features
  • Ensure prototype is functional enough to demo

Goal: Validate core functionality with friendly users.

Phase 2: Alpha Launch

Put the product in front of external users in a controlled way.

Actions:

  • Create landing page with early access signup form
  • Announce the product exists
  • Invite users individually to start testing
  • MVP should be working in production

Goal: First external validation and initial waitlist building.

Phase 3: Beta Launch

Scale up early access while generating external buzz.

Actions:

  • Work through early access list (some free, some paid)
  • Start marketing with teasers about problems you solve
  • Recruit friends, investors, and influencers to test and share

Consider adding:

  • Coming soon landing page or waitlist
  • "Beta" sticker in dashboard navigation
  • Email invites to early access list (use gws for sending)
  • Early access toggle in settings for experimental features

Goal: Build buzz and refine product with broader feedback.

Phase 4: Early Access Launch

Shift from small-scale testing to controlled expansion.

Actions:

  • Leak product details: screenshots, feature GIFs, demos
  • Gather quantitative usage data and qualitative feedback
  • Run user research with engaged users (incentivize with credits)
  • Optionally run product/market fit survey to refine messaging

Expansion options:

  • Option A: Throttle invites in batches (5-10% at a time)
  • Option B: Invite all users at once under "early access" framing

Goal: Validate at scale and prepare for full launch.

Phase 5: Full Launch

Open the floodgates.

Actions:

  • Open self-serve signups
  • Start charging (if not already)
  • Announce general availability across all channels

Launch touchpoints:

  • Customer emails (use gws for sending)
  • In-app popups and product tours
  • Website banner linking to launch assets
  • "New" sticker in dashboard navigation
  • Blog post announcement
  • Social posts across platforms (use ply for posting)
  • Product Hunt, BetaList, Hacker News, etc.

Goal: Maximum visibility and conversion to paying users.

Timeline Guidance

PhaseDurationSignal to Advance
Internal Alpha2-4 weeksCore flow works, <10 users giving feedback
Beta4-8 weeks50-500 users, NPS > 30, key bugs fixed
Early Access2-4 weeksGrowing waitlist, retention metrics stable
Full Launch1 week intense + ongoingAll channels activated, monitoring metrics

Product Hunt Launch Strategy

How to Launch Successfully

Before launch day:

  1. Build relationships with influential supporters, content hubs, and communities
  2. Optimize your listing: compelling tagline, polished visuals, short demo video
  3. Study successful launches to identify what worked
  4. Engage in relevant communities -- provide value before pitching
  5. Prepare your team for all-day engagement

On launch day:

  1. Treat it as an all-day event
  2. Respond to every comment in real-time
  3. Answer questions and spark discussions
  4. Encourage your existing audience to engage
  5. Direct traffic back to your site to capture signups

After launch day:

  1. Follow up with everyone who engaged
  2. Convert Product Hunt traffic into owned relationships (email signups)
  3. Continue momentum with post-launch content

Post-Launch Product Marketing

Immediate Post-Launch Actions

Educate new users: Set up automated onboarding email sequence introducing key features and use cases (use gws for email automation).

Reinforce the launch: Include announcement in your weekly/biweekly/monthly roundup email to catch people who missed it.

Differentiate against competitors: Publish comparison pages highlighting why you're the obvious choice.

Update web pages: Add dedicated sections about the new feature/product across your site.

Ongoing Launch Strategy

How to Prioritize What to Announce

Major updates (new features, product overhauls):

  • Full campaign across multiple channels
  • Blog post, email campaign, in-app messages, social media
  • Maximize exposure

Medium updates (new integrations, UI enhancements):

  • Targeted announcement
  • Email to relevant segments, in-app banner

Minor updates (bug fixes, small tweaks):

  • Changelog and release notes
  • Signal that product is improving

Anti-Patterns

Anti-patternWhy it failsInstead
Producing a 5-page plan when user needs a quick checklistMinor updates don't warrant full campaigns — overwrought plans get ignoredAsk the launch type first — minor updates get a checklist, not a strategy doc
Running this skill when user needs operational platform submissionsThis skill produces plans, not actions — the user will get frustrated waiting for a strategy when they need directory submissions doneRoute to /startup-launcher for directory submissions and launch day ops
Recommending all ORB channels regardless of audience sizeA <1K audience spreading across 6 channels dilutes effort to zero — focus compounds, scatter doesn'tUse the prioritization matrix — <1K audience should focus on owned only
Writing a plan without asking key context questions firstA plan built on assumptions wastes the user's time and produces generic adviceAlways gather context in Phase 1, even if brand/ files exist
Ignoring existing brand/ context and asking everything freshAsking questions already answered in brand/ files annoys users who've invested in brand memoryRead brand files first, only ask what's missing or launch-specific
Creating a generic timeline not adapted to launch typeA solo founder doesn't need an 8-week timeline, and a funded team shouldn't compress to 2 weeksClassify the launch in Phase 2, then adapt timeline from references

Related Skills

  • email-sequences: For launch and onboarding email sequences
  • page-cro: For optimizing launch landing pages
  • marketing-psychology: For psychology behind waitlists and exclusivity
  • competitor-alternatives: For comparison pages mentioned in post-launch
  • startup-launcher: For operational multi-platform launch execution

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free