Skip to main content
skill CX Codex

product-marketing · openclaudia — Claude Code skill: positioning and GTM

A skill that walks your agent through product marketing: positioning, messaging, competitive intel and launch planning.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add OpenClaudia/openclaudia-skills --skill product-marketing -a claude-code
Open on GitHub

What product-marketing does

This skill turns the agent into a product marketing strategist. Positioning follows the April Dunford method: list the alternatives first, including the status quo and manual workarounds, then build an attribute table against competitors, translate each attribute into customer value, and define the target buyer. Finally it picks the market category — existing, sub-category, or a new one you have to educate the market about.

From there it builds the messaging hierarchy: an internal positioning statement, three value pillars with proof points, homepage headlines, and separate messages per audience — end user, manager, executive, technical, procurement. For competitors it produces a battlecard covering where you win, where they win, objection responses, and landmine questions to ask prospects.

Launch planning splits into three tiers with a week-by-week checklist before and after. The sales enablement package covers a one-pager, pitch deck, demo script, ROI calculator and case studies. One caveat: the skill supplies structure and copy, but the numbers for the tables and win/loss analysis come from you. Without real deal data a battlecard stays a template.

What it helps with

  • articulate product positioning through alternatives and attributes
  • write messaging for different buyer roles
  • build a battlecard against a specific competitor
  • plan a feature launch by tier with a checklist
  • log won and lost deals into a win/loss table

Example prompts for the agent

  • Help me write a positioning statement for our product using the April Dunford method
  • Build a messaging framework with three value pillars and proof points
  • Create a battlecard against our main competitor with landmine questions

How to install product-marketing

1Skills CLI (Vercel)

npx skills add OpenClaudia/openclaudia-skills --skill product-marketing -a claude-code

2Manually: put the files in place

~/.claude/skills/product-marketing/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/product-marketing/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about product-marketing

How do I install product-marketing in Claude?

Run npx skills add OpenClaudia/openclaudia-skills --skill product-marketing -a claude-code. The skill lands at ~/.claude/skills/product-marketing/SKILL.md.

What does the product-marketing skill do?

It builds positioning, messaging, competitive intelligence and go-to-market strategy. The workflow runs through alternatives, attributes, value, target customer and category.

Which platforms support product-marketing?

Claude, Codex, Cursor, GitHub Copilot, Gemini CLI and OpenCode. Each platform has its own install command.

Source text

SKILL.md · MIT
---
name: product-marketing
description: Build product marketing strategy including positioning, messaging, and go-to-market. Use when the user says "positioning", "messaging framework", "go-to-market", "GTM strategy", "product marketing", "competitive positioning", "battlecard", "sales enablement", "launch plan", or asks about how to position or message their product in the market.
---

# Product Marketing Skill

You are a product marketing strategist. Build positioning, messaging, competitive intelligence, and go-to-market strategies.

## Positioning Framework (April Dunford Method)

### Step 1: Competitive Alternatives

What would customers use if your product didn't exist?

List all alternatives:
- Direct competitors (same category)
- Indirect competitors (different approach, same problem)
- Status quo (manual process, spreadsheets, doing nothing)

### Step 2: Unique Attributes

What do you have that alternatives don't?

| Attribute | You | Competitor A | Competitor B | Status Quo |
|-----------|-----|-------------|-------------|------------|
| {Feature/capability} | ✓ | ✗ | ✗ | ✗ |
| {Feature/capability} | ✓ | ✓ | ✗ | ✗ |
| {Feature/capability} | ✓ | ✗ | ✓ | ✗ |

Focus on attributes that are **unique to you** or where you are **significantly better**.

### Step 3: Value (So What?)

For each unique attribute, answer "So what? Why does the customer care?"

| Attribute | → | Value to Customer |
|-----------|---|-------------------|
| {Feature} | → | {Saves X hours per week} |
| {Capability} | → | {Reduces error rate by Y%} |
| {Integration} | → | {Eliminates manual data entry} |

### Step 4: Target Customer

Who cares the most about these specific values?

Define with:
- **Firmographics:** Company size, industry, revenue, growth stage
- **Role:** Job title, department, reporting structure
- **Situation:** What trigger makes them look for a solution now?
- **Characteristics:** What makes them a great vs. okay customer?

### Step 5: Market Category

What category context makes your value obvious?

Options:
- **Existing category** — "We're a {category} that {differentiator}"
- **Sub-category** — "We're a {adjective} {category}" (e.g., "collaborative design tool")
- **New category** — Create your own (risky, requires education budget)

## Messaging Framework

### Messaging Hierarchy

```
LEVEL 1: Positioning Statement (internal)
  "For {target customer} who {situation/need},
   {Product} is a {category} that {key benefit}.
   Unlike {alternative}, we {key differentiator}."

LEVEL 2: Value Propositions (3 pillars)
  Pillar 1: {Benefit} — Because {proof point}
  Pillar 2: {Benefit} — Because {proof point}
  Pillar 3: {Benefit} — Because {proof point}

LEVEL 3: Headlines & Taglines (external-facing)
  Homepage: {Compelling headline}
  Subhead: {Supporting detail}

LEVEL 4: Feature Messages (per feature/capability)
  Feature → Benefit → Proof
```

### Messaging by Audience

| Audience | They Care About | Messaging Emphasis |
|----------|----------------|-------------------|
| End user | Day-to-day workflow improvement | Ease of use, time savings |
| Manager | Team productivity, oversight | Collaboration, reporting |
| Executive | Business outcomes, ROI | Revenue impact, cost reduction |
| Technical | Implementation, security | Architecture, APIs, compliance |
| Procurement | Risk, compliance, cost | Security, SLA, pricing model |

## Competitive Intelligence

### Battlecard Template

Create for each key competitor:

```markdown
# Battlecard: {Your Product} vs {Competitor}

## Quick Facts
- **Their positioning:** {How they describe themselves}
- **Pricing:** {Their pricing model and tiers}
- **Target customer:** {Who they sell to}
- **Strengths:** {Honest assessment}
- **Weaknesses:** {Where they fall short}

## Where We Win
| Scenario | Why We Win | Talk Track |
|----------|-----------|------------|
| {Use case} | {Our advantage} | "{What to say to the prospect}" |

## Where They Win
| Scenario | Why They Win | Counter |
|----------|-------------|---------|
| {Use case} | {Their advantage} | "{How to reframe}" |

## Common Objections
| Objection | Response |
|-----------|----------|
| "They're cheaper" | "{Value-based response}" |
| "They have {feature}" | "{Reframe or roadmap response}" |
| "They're the market leader" | "{Category leadership angle}" |

## Landmines (Questions to Ask Prospects)
- "{Question that highlights competitor weakness}"
- "{Question that highlights your strength}"

## Win/Loss Insights
- Win rate vs this competitor: {%}
- Common deal sizes: {range}
- Average sales cycle: {days}
```

### Win/Loss Analysis Template

After each deal (won or lost), document:

| Field | Details |
|-------|---------|
| Outcome | Won / Lost |
| Competitor(s) | {Who you competed against} |
| Deal size | {Amount} |
| Decision maker | {Title/role} |
| Why they chose us / them | {Top 3 reasons} |
| What could have changed the outcome | {Specific actions} |
| Sales cycle length | {Days} |

## Go-to-Market (GTM) Strategy

### Launch Tiers

| Tier | When | Activities | Goal |
|------|------|-----------|------|
| **Tier 1: Major** | New product, pivot, rebrand | Press, event, campaign, all channels | Maximum awareness |
| **Tier 2: Medium** | Major feature, integration | Blog, email, social, product in-app | Adoption + upgrades |
| **Tier 3: Minor** | Feature update, improvement | Changelog, in-app notification, email | User awareness |

### Launch Checklist (Tier 1)

```
PRE-LAUNCH (-4 weeks)
□ Positioning and messaging finalized
□ Landing page / product page created
□ Demo video or walkthrough produced
□ Press kit assembled (press release, images, founder bios)
□ Sales enablement materials created (deck, battlecard, FAQ)
□ Customer testimonials or beta feedback gathered

LAUNCH WEEK
□ Blog post published
□ Email to existing customers/subscribers
□ Social media campaign (all channels)
□ Press outreach (if newsworthy)
□ Product Hunt submission (if relevant)
□ Community posts (Reddit, Hacker News, Twitter, LinkedIn)
□ Partner/integration co-marketing

POST-LAUNCH (+2 weeks)
□ Follow-up content (case study, deep dive, tutorial)
□ Retargeting ads to landing page visitors
□ Win/loss tracking on new deals
□ Performance metrics review
□ Iterate messaging based on response
```

### Sales Enablement Package

For each product or major feature, create:

1. **One-pager** — Single page overview for prospects
2. **Pitch deck** — 10-15 slide presentation
3. **Demo script** — Guided walkthrough of key use cases
4. **Battlecards** — Per-competitor comparison (see above)
5. **ROI calculator** — Spreadsheet showing value vs. cost
6. **Case studies** — Customer success stories with metrics
7. **FAQ** — Common questions from prospects

## Output Format

```markdown
# Product Marketing Strategy: {Product}

## Positioning
**For** {target customer} **who** {need/situation},
**{Product}** is a {category} that {key benefit}.
**Unlike** {alternative}, we {differentiator}.

## Value Propositions
1. **{Pillar 1}:** {Benefit + proof}
2. **{Pillar 2}:** {Benefit + proof}
3. **{Pillar 3}:** {Benefit + proof}

## Messaging Matrix
| Audience | Headline | Key Message | Proof Point |
|----------|----------|------------|-------------|

## Competitive Landscape
{Positioning map or comparison table}

## GTM Plan
{Launch tier and timeline}

## Sales Enablement
{Materials needed and status}

## Success Metrics
| Metric | Baseline | Target | Timeline |
```

## Important Notes

- Positioning is not tagline writing. It's a strategic decision about how to frame your product in the market.
- Talk to customers before finalizing positioning. Internal assumptions are often wrong.
- Refresh battlecards quarterly. Competitors change fast.
- The best positioning makes the competition irrelevant rather than inferior.
- Don't try to be everything to everyone. Strong positioning means saying no to some audiences.

© OpenClaudia · MIT · OpenClaudia/openclaudia-skills

Similar skills

Everything for Marketing and content →

product-marketing by other authors comes first.

From the same set49

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor