Launch
Plan a staged product launch across owned, rented, and borrowed channels with a week-by-week timeline and launch-day checklist.
Overview
Launch is an agent skill most often used in Launch (also Validate, Grow) that plans ORB-based channel mix and a five-phase go-live timeline with launch-day checklists for solo builders.
Install
npx skills add https://github.com/coreyhaines31/marketingskills --skill launchWhat is this skill?
- Checks for product-marketing.md before planning so positioning stays consistent
- ORB Framework: Owned, Rented, and Borrowed channel allocation
- Five-phase launch path: internal prep, alpha, beta, early access, full launch
- Maps tactics and timeline to your actual list sizes and follower counts
- Includes launch-day checklist and audience-building guidance before go-live
- ORB Framework with three channel classes: Owned, Rented, Borrowed
- Five-phase launch approach from internal prep through full launch
- Launch day checklist included in expected workflow
Adoption & trust: 15.1k installs on skills.sh; 32.4k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are ready to ship but only have a vague “post on social” plan and no phased channel strategy matched to your real audience size.
Who is it for?
Indie SaaS or tool founders with a small email list or social following who want a structured multi-week launch instead of a one-day spike.
Skip if: Teams that already have an approved enterprise GTM calendar, paid media agency ownership, or no product-marketing.md-style positioning to anchor recommendations.
When should I use this skill?
You need to plan a product launch with realistic channels, phased rollouts, or Product Hunt-style distribution and should align with product-marketing.md first.
What do I get? / Deliverables
You get an ORB-mapped, time-boxed launch plan with per-phase tactics and a launch-day checklist grounded in your product-marketing context.
- ORB-based channel plan mapped to your assets
- Time-boxed multi-phase launch timeline with per-phase tactics
- Launch-day checklist
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Launch is the canonical shelf because the skill outputs distribution tactics, channel mix, and go-live sequencing—not core product build. Distribution subphase fits ORB channel planning, phased rollouts (alpha through full launch), and platforms like Product Hunt.
Where it fits
Bound a six-week window into alpha, beta, and full-launch milestones before committing engineering freeze dates.
Allocate Twitter, email, and community effort using ORB given 500 subscribers and 2k followers.
Draft a first Product Hunt runbook with prep steps instead of improvising on launch morning.
Plan audience warm-up posts and partner outreach between beta and early access to avoid a cold full launch.
How it compares
Use instead of generic “marketing plan” chat when you need ORB channels plus a fixed multi-phase launch structure tied to product-marketing.md.
Common Questions / FAQ
Who is launch for?
Solo and indie builders shipping a B2B or prosumer product who need distribution planning with realistic channel sizes—not a corporate brand campaign.
When should I use launch?
Use it in Validate when scoping go-live timing; in Launch for distribution and Product Hunt-style plays; and in Grow when sequencing early-access expansion before full public launch.
Is launch safe to install?
Treat it like any third-party agent skill: review the Security Audits panel on this Prism page and inspect the repo SKILL.md before letting an agent read local marketing files.
SKILL.md
READMESKILL.md - Launch
{ "skill_name": "launch", "evals": [ { "id": 1, "prompt": "We're launching a new B2B SaaS product for design teams in 6 weeks. It's a design review tool. We have a small audience (500 email subscribers, 2k Twitter followers). Help us plan the launch.", "expected_output": "Should check for product-marketing.md first. Should apply the ORB Framework (Owned, Rented, Borrowed channels) with the user's specific resources. Owned: email list (500 subscribers), website. Rented: Twitter (2k followers). Borrowed: partnerships, communities, Product Hunt. Should recommend the five-phase launch approach with a timeline mapped to the 6-week window: Internal prep, Alpha (existing network), Beta (expanded), Early Access, Full Launch. Should provide specific tactics for each phase. Should recommend building up the audience before launch day. Should include a launch day checklist.", "assertions": [ "Checks for product-marketing.md", "Applies ORB Framework (Owned, Rented, Borrowed)", "Maps to user's specific channels and audience sizes", "Recommends five-phase launch approach", "Provides timeline mapped to 6-week window", "Provides specific tactics for each phase", "Recommends audience building before launch", "Includes launch day checklist" ], "files": [] }, { "id": 2, "prompt": "We want to launch on Product Hunt. Any tips? We've never done it before.", "expected_output": "Should apply the Product Hunt strategy section. Should cover: choosing the right day and time, preparing assets (logo, gallery images, maker video), crafting the tagline and description, building a hunter network, activating supporters on launch day, engaging with comments, and post-launch follow-up. Should recommend preparation timeline (start 2-4 weeks before). Should mention common mistakes to avoid. Should set realistic expectations about outcomes.", "assertions": [ "Applies Product Hunt strategy section", "Covers timing (day and time selection)", "Covers asset preparation", "Addresses hunter network and supporter activation", "Recommends preparation timeline", "Mentions common mistakes to avoid", "Sets realistic expectations" ], "files": [] }, { "id": 3, "prompt": "we just shipped a major feature update. how should we announce it? it's not a full product launch, just a big new feature.", "expected_output": "Should trigger on casual phrasing. Should apply the ongoing launch strategy section, specifically the major/medium/minor update matrix. Should identify this as a major feature update. Should recommend appropriate channels and tactics for a feature launch (less than a full product launch but more than a changelog entry). Should include: announcement email, blog post, social media push, in-app notification, and possibly a mini Product Hunt launch. Should provide a feature announcement framework.", "assertions": [ "Triggers on casual phrasing", "Applies ongoing launch strategy / update matrix", "Identifies as major feature update", "Scales tactics appropriately (not full launch)", "Recommends announcement channels", "Includes email, blog, social, and in-app notification", "Provides feature announcement framework" ], "files": [] }, { "id": 4, "prompt": "Our launch flopped. We launched 3 weeks ago and only got 50 signups. We expected at least 500. What went wrong and what can we do now?", "expected_output": "Should apply the post-launch product marketing section. Should diagnose potential failure causes: insufficient audience building pre-launch, wrong channels, weak value proposition messaging, poor launch execution, targeting the wrong audience. Should recommend post-launch recovery tactics: iterate on messaging, identify which channels produce