Skip to main content
command CX Codex

plan-launch — Claude Code command: what it does, how to install

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

MIT ★ 28,211 updated 2026-10-16

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add phuryn/pm-skills
/plugin install pm-go-to-market@pm-skills
Open on GitHub

What plan-launch 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.

What it helps with

  • 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 for the agent

  • /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

How to install plan-launch

1Plugin marketplace

/plugin marketplace add phuryn/pm-skills
/plugin install pm-go-to-market@pm-skills

2Manually: put the files in place

.claude/commands/plan-launch.md

Call it with /plan-launch. For all projects use ~/.claude/commands/

Questions about plan-launch

How to install plan-launch in Claude Code?

Add the author marketplace via /plugin marketplace add phuryn/pm-skills, then install the package with /plugin install pm-go-to-market@pm-skills.

What does plan-launch do?

It interviews you about the launch context, evaluates market segments, defines customer profiles, and outputs a complete Markdown GTM strategy.

What arguments does plan-launch accept?

Pass the name of your product or feature, or attach an existing PRD, strategy doc, or pitch deck in the invocation command.

Source text

plan-launch.md · MIT
---
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
[After beachhead: which adjacent segments, in what order, with what adaptations]
```

Save as markdown.

### Step 6: Offer Next Steps

- "Want me to **design growth loops** for post-launch traction?"
- "Should I **create competitive battlecards** for sales?"
- "Want me to **draft marketing copy** for the launch?"
- "Should I **build a metrics dashboard** for launch tracking?"

## Notes

- "Everyone" is not a segment — the tighter the beachhead, the faster you learn
- The ICP should be specific enough that sales/marketing can identify prospects in 30 seconds
- Messaging should use the customer's language, not your internal terminology
- Pre-launch activities (waitlist, beta, early access) are as important as launch day
- Plan for post-launch: the first 90 days after launch determine long-term trajectory

© Paweł Huryn · MIT · phuryn/pm-skills

Similar slash commands

All slash commands for Marketing and content →

From the same set120

The whole set →
strategy The /strategy command builds a complete product strategy through a 9-section Canvas: vision, segments, value, trade-offs, metrics, growth, capabilities, and defensibility. CX Codex +1 ★ 28,211repo stars research-users research-users synthesizes research notes, survey exports, and tickets into user personas, behavioral segments, and journey maps. Helpful for PMs evaluating qualitative data. CX Codex +1 ★ 28,211repo stars setup-metrics setup-metrics is a Claude Code command that defines product metrics from a North Star to alert thresholds. It covers feature measurement planning and dashboard reviews. CX Codex +1 ★ 28,211repo stars triage-requests triage-requests takes a batch of feature requests in any format and organizes them into themed groups ranked by priority. Helps clarify what users actually need and where to focus next. CX Codex +1 ★ 28,211repo stars pricing Builds a pricing plan from product value, competitor data, willingness to pay, and pricing tests. Useful when launching or changing a product’s pricing. CX Codex +1 ★ 28,211repo stars market-scan market-scan — a command for strategic analysis of competitive landscape. Runs SWOT, PESTLE, Porter's Five Forces, and Ansoff Matrix together and delivers a unified report with cross-framework synthesis. CX Codex +1 ★ 28,211repo stars discover Runs a structured product discovery cycle from initial ideation to experiment design. Useful for testing product hypotheses before writing code. CX Codex +1 ★ 28,211repo stars brainstorm brainstorm — a Claude Code command that produces product ideas or validation experiments from PM, designer and engineer viewpoints, for either an existing product or a new concept. CX Codex +1 ★ 28,211repo stars

Project sponsors

Companies that keep this analytics open