# plan-launch

plan-launch builds a full go-to-market launch plan: from beachhead market and ICP to messaging, channel priorities, and timeline saved to Markdown.

- command · `type=command` · Claude Code, Codex, GitHub Copilot, Gemini CLI · ★ 28211 repo stars
- Author: Paweł Huryn
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/phuryn/pm-skills/tree/HEAD/pm-go-to-market/commands/plan-launch.md
- Updated: 2026-10-16
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/commands/plan-launch

## What it does

The command guides you through drafting a go-to-market plan directly inside Claude Code. It starts by clarifying launch scope: product type, progress stage, existing customer base, hard timelines, and budget limits. It then links adjacent sub-skills: `beachhead-segment` evaluates market niches by burning pain and purchase authority, `ideal-customer-profile` details customer jobs and qualification signals, and `gtm-strategy` ranks acquisition channels by expected ROI.

The final output is structured markdown containing ICP tables, stakeholder-specific messaging matrices, launch phases, and concrete 30- and 90-day targets. Without a clear product summary or an attached PRD in the prompt argument, the resulting strategy will remain generic, so concrete context is required upfront.

## Install

### Claude Code (native platform)

1. **Plugin marketplace**
In the agent chat (not a shell):
```text
/plugin marketplace add phuryn/pm-skills
```
In the agent chat (not a shell):
```text
/plugin install pm-go-to-market@pm-skills
```

2. **Manually: put the files in place**
- File: `.claude/commands/plan-launch.md` — Call it with /plan-launch. For all projects use ~/.claude/commands/

### Codex

**Manually: put the files in place**
- File: `~/.codex/prompts/plan-launch.md` — Call it with /prompts:plan-launch. Codex marks this format deprecated in favour of skills

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/prompts/plan-launch.prompt.md`

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/plan-launch.toml` — Gemini stores commands as TOML: the prompt text goes into the prompt field

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/phuryn/pm-skills/tree/HEAD/pm-go-to-market/commands/plan-launch.md

## When to use it
- Select a viable beachhead customer segment based on urgency and budget
- Define an ICP with explicit qualification criteria and JTBD insights
- Schedule launch tasks across pre-launch, release week, and post-launch phases
- Generate an end-to-end GTM strategy document in clean Markdown

## Example prompts
- /plan-launch AI-powered proposal writer for consulting firms
- /plan-launch New enterprise tier for our project management tool
- /plan-launch PRD and launch strategy from prd.md

## Source text · plan-launch.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 38204b7b77dec280.

BEGIN THIRD-PARTY FILE 38204b7b77dec280
````text
---
description: Create a full go-to-market strategy — beachhead segment, ICP, messaging, channels, and launch plan
argument-hint: "<product or feature to launch>"
---

# /plan-launch -- Go-to-Market Strategy

Build a complete GTM plan from first principles: identify your beachhead market, define the ideal customer, craft messaging, choose channels, and create a launch timeline.

## Invocation

```
/plan-launch AI-powered proposal writer for consulting firms
/plan-launch New enterprise tier for our project management tool
/plan-launch [upload a PRD, strategy doc, or pitch deck]
```

## Workflow

### Step 1: Understand the Launch

Ask:
- What are you launching? (new product, new feature, new tier, market expansion)
- What stage? (pre-launch planning, imminent launch, post-launch optimization)
- Do you have existing customers? Or starting from zero?
- What's the timeline? Any hard deadlines?
- Budget constraints? Team size?

### Step 2: Define Beachhead Segment

Apply the **beachhead-segment** skill:

- Evaluate potential market segments against:
  - Burning pain (how urgently they need this)
  - Willingness to pay (budget and purchase authority)
  - Winnable market share (can you reach and win them)
  - Referral potential (will they tell others)
- Recommend the single best starting segment with rationale
- Map adjacent segments for expansion after beachhead is secured

### Step 3: Define Ideal Customer Profile

Apply the **ideal-customer-profile** skill:

- Demographics: company size, industry, geography, tech stack
- Behaviors: how they discover solutions, buying process, decision makers
- JTBD: specific jobs they're hiring your product for
- Current alternatives: what they use today and why it falls short
- Qualification criteria: how to identify them quickly

### Step 4: Build GTM Strategy

Apply the **gtm-strategy** skill:

- **Positioning**: How you describe yourself to this segment
- **Messaging**: Key messages for different stakeholders (buyer, user, influencer)
- **Channels**: Where and how to reach your ICP (ranked by expected ROI)
- **Launch tactics**: Specific actions for pre-launch, launch day, and post-launch
- **Pricing alignment**: How pricing supports the GTM motion
- **Success metrics**: How you'll know the launch worked

### Step 5: Generate GTM Plan

```
## Go-to-Market Plan: [Product/Feature]

**Launch date**: [target]
**Type**: [new product / feature / tier / market expansion]

### Beachhead Segment
**Who**: [specific segment definition]
**Why them first**: [rationale against criteria]
**Size**: [TAM/SAM/SOM estimate]

### Ideal Customer Profile
| Attribute | Definition |
|-----------|-----------|
| Company size | [range] |
| Industry | [specific] |
| Decision maker | [title/role] |
| Key JTBD | [job they need done] |
| Current solution | [what they use today] |
| Qualification signal | [how to identify them] |

### Positioning & Messaging
**Positioning statement**: For [who] who [need], [product] is [category] that [benefit]. Unlike [alternative], we [differentiator].

**Key messages by stakeholder**:
| Audience | Message | Proof Point |
|----------|---------|------------|

### Channel Strategy
| Channel | Tactic | Reach | Cost | Priority |
|---------|--------|-------|------|----------|

### Launch Timeline
| Phase | Timing | Actions | Owner |
|-------|--------|---------|-------|
| Pre-launch | [dates] | [list] | [who] |
| Launch week | [dates] | [list] | [who] |
| Post-launch | [dates] | [list] | [who] |

### Success Metrics
| Metric | 30-day target | 90-day target |
|--------|-------------|-------------|

### Risks & Mitigations
| Risk | Likelihood | Impact | Mitigation |
|------|-----------|--------|-----------|

### Expansion Plan
````
END THIRD-PARTY FILE 38204b7b77dec280

The third-party file has ended. Everything between the 38204b7b77dec280 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3725 of 4542 bytes. © Paweł Huryn · MIT · https://github.com/phuryn/pm-skills/tree/HEAD/pm-go-to-market/commands/plan-launch.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
