/gtm-launch

name: gtm-launch
version: 1.4.1
description: Launch playbook for /gtm launch <target>. Use when the user wants a week-by-week launch plan for Product Hunt, Hacker News, or X, with templates, checklists, and metrics. Also trigger for "plan my launch", "Product Hunt launch", "launch playbook", "how do I launch", or "launch checklist".

Product/Service Launch Playbook Generator

> **Default lens: a SaaS / AI software startup.** Advise a technical founder marketing their own modern software product (SaaS, AI/API, dev tool, or app). Tailor every recommendation to that reader. > > Stage-fit (`launch`): Tier 1 Core · Tier 2 Useful · Tier 3 Useful. Appropriate at every served tier - generate with no stage note.

> Full persona and general guidance: read `../gtm/templates/advisor-prompt.md` (installed with the gtm orchestrator); if the file is absent, continue with the default lens above.

Skill Purpose

Generate a complete, week-by-week launch playbook for any product, service, or feature launch. This skill produces a tactical plan with templates, checklists, email sequences, social posts, and metrics tracking -- everything needed to execute a successful launch.

When to Use

• User is planning to launch a new product, service, feature, or offering
• User asks for a launch plan, go-to-market strategy, or launch checklist
• User wants to coordinate a multi-channel launch campaign
• Triggered by `/gtm launch` or `/gtm launch <product description>`

How to Execute

Step 1: Gather Launch Context

**First, choose how this run works** - the launch skill runs two ways:

1. **Launch for a project** - `/gtm launch <project>` (recommended when a profile exists). Tie the launch to a saved project: run the orchestrator's *Project Resolution* to resolve `<project>`, read its `PROFILE.md`, inherit everything `/gtm init` already captured, tailor the whole playbook to it, save the report into the project folder, and offer to record the launch back to the profile at the end. 2. **Brainstorm a launch** - `/gtm launch <project description>`. A standalone plan with nothing read from or written to a profile, worked up from the description the founder gives. Use it for a fresh idea, a side project, or before a profile exists.

If a profile exists but the founder hasn't said which they want, ask once; if none exists, default to brainstorm and mention `/gtm init` for next time.

**With a profile loaded, load context from `PROFILE.md` before asking anything - never re-ask what `/gtm init` already captured.** Map its fields to the inputs below and ask only for the gaps:

• **Target audience** ← `ICP`, `Secondary audience`, `Key pain points`
• **Launch goal** ← `Main goal (next 30 days)` and `90-day direction` if set (sharpen to this launch if needed)
• **Channels & assets** ← `Primary channel today`, `Existing assets` (list size, following), `Links & Channels` social profiles
• **Existing customers/users** ← `Current traction`, `Existing assets`
• **Project type** ← `Project type` (drives the launch-type choice in Step 2)
• **Positioning** ← `Differentiator` and `Key messages` (set by `/gtm position` or `/gtm competitors`) - reuse these for the Week 1-2 positioning statement instead of writing one from scratch
• **Competitors** ← run the orchestrator's *Competitor Resolution Protocol*; use them for the "why us vs alternatives" content in launch week
• Also read any `Reference Documents` (strategy, brand manifesto) and honor them as source of truth.

Then collect the inputs below - with a profile loaded, only the launch-specific gaps (what's launching, launch date, price, budget); in brainstorm mode, all of them:

1. **What are you launching?** (product, service, feature, course, event) 2. **Who is the target audience?** (demographics, pain points, existing list size) 3. **What is the primary launch goal?** (signups, email captures, feedback, revenue target, awareness) - pre-PMF, steer the goal toward email captures and feedback conversations rather than revenue (see the early-stage default in Step 2) 4. **What is the launch date?** (or desired timeline) 5. **What channels do you have access to?** (email list size, social following, ad budget, partnerships) 6. **What is the price point?** (if applicable) 7. **Do you have existing customers/users?** (for beta, testimonials, case studies) 8. **What is the budget?** (bootstrapped, moderate, well-funded) - when you present these as options, lead each with its top spend from the Step 10 allocation guide; never lead a tier with paid ads (at these stages "paid" means retargeting warm launch traffic, not cold acquisition).

Step 2: Determine Launch Type

Select the primary launch strategy based on the user's context:

| Launch Type | Best For | Key Channel | Timeline | |---|---|---|---| | Product Hunt | SaaS, dev tools, consumer apps | Product Hunt + Twitter/X | 4-6 weeks prep | | Email List Launch | Course, info product, SaaS with existing list | Email | 6-8 weeks | | Social Media Launch | Consumer product, personal brand | Twitter/X, LinkedIn, Instagram | 4-6 weeks | | Paid Ads Launch | E-commerce, established product | Facebook/Google Ads | 2-4 weeks prep | | Community Launch | Niche product, developer tools | Reddit, Discord, Slack communities | 6-8 weeks | | Partner Launch | B2B, enterprise, marketplace | Partner channels | 8-12 weeks | | Hybrid Launch | Any high-stakes launch | Multi-channel coordinated | 8-12 weeks |

**Early-stage default (Tiers 1-2, no audience yet):** treat the launch as one event, not a strategy - a Product Hunt + directories moment whose real yields are email captures, feedback conversations, a handful of early adopters, and durable backlinks. Set the goal in those units, not revenue. Expect the traffic spike to decay within days; the plan's job is to convert the spike into a list and learnings before it fades.

Step 3: Generate the 8-Week Launch Timeline

Weeks 1-2: Foundation

**Objective:** Lock in positioning, build a