Product Marketing Context
This skill creates and maintains a foundational product marketing context document at .agents/product-marketing.md. Other marketing skills (competitors, marketing-plan, pricing-strategy) reference this document so the user never repeats positioning, audience, or messaging details.
When to Use
- Starting any new marketing project or campaign — run this first before other marketing skills
- User says "set up context," "product context," "marketing context," "positioning," "who is my target audience," "describe my product," "ICP," "ideal customer profile"
- User wants a single source of truth for product, audience, and competitive positioning
- Before writing ads, emails, landing pages, or sales collateral that need consistent messaging
- Refreshing stale context after product, pricing, or positioning changes
Prerequisites
- A project repository with at least a README or basic product documentation (for auto-draft mode)
- PowerShell on Windows as the primary host environment
- Write access to the project root (the skill creates
.agents/product-marketing.md)
Procedure
Step 1 — Check for Existing Context
Check if .agents/product-marketing.md already exists:
Test-Path .agents\product-marketing.md
Also check legacy locations that older setups may have used:
Test-Path .claude\product-marketing.md
Test-Path .agents\product-marketing-context.md
Test-Path .claude\product-marketing-context.md
If the canonical file exists at .agents/product-marketing.md:
- Read it and summarize what's captured
- Ask which sections the user wants to update
- Only gather info for those affected sections
- Jump to Step 3 to update
If a legacy file exists anywhere other than .agents/product-marketing.md:
Offer to move it to the canonical location:
Move-Item .claude\product-marketing.md .agents\product-marketing.md -Force
Confirm the move, then read and summarize
If no file exists anywhere, offer two options:
- Option A — Auto-draft from codebase (recommended): Study the repo and draft a V1. The user reviews, corrects, and fills gaps. Faster than starting from scratch.
- Option B — Start from scratch: Walk through each section conversationally, one at a time.
Most users prefer Option A. After presenting the draft, ask: "What needs correcting? What's missing?"
Step 2 — Gather Information
If Auto-Drafting (Option A)
Read the codebase for source material:
README.md, README.*, or readme.*
- Landing pages, marketing copy, about pages, pricing pages (HTML, MDX, JSX, etc.)
- Meta descriptions and
<title> tags
package.json (description, keywords, homepage fields)
CHANGELOG.md or changelog entries
- Any existing docs (
docs/, *.md files)
Draft every section listed in "Sections to Capture" below based on what you find.
Present the full draft and ask what needs correcting or is missing.
Iterate until the user is satisfied.
HARD RULE — Never invent facts while auto-drafting. Metrics, customer names, testimonials, competitor shortcomings, and verbatim quotes must come from the repo or the user. If a section has no source, write [TBD — needs input] and ask. A wrong "fact" here propagates into every ad, email, and page the other skills produce.
If Starting from Scratch (Option B)
Walk through each section in "Sections to Capture" conversationally, one at a time. Do not dump all questions at once.
For each section:
- Briefly explain what you're capturing and why
- Ask relevant, specific questions (see Tips below)
- Confirm accuracy by summarizing back
- Move to the next section
Push for verbatim customer language — exact phrases are more valuable than polished descriptions because they reflect how customers actually think and speak, which makes downstream copy more resonant.
Step 3 — Create or Update the Document
After gathering information, create or update .agents/product-marketing.md using this exact structure. Keep section names stable — other marketing skills parse the document by section heading.
# Product Marketing Context
*Last updated: [date]*
## Product Overview
**One-liner:**
**What it does:**
**Product category:**
**Product type:**
**Business model:**
## Target Audience
**Target companies:**
**Decision-makers:**
**Primary use case:**
**Jobs to be done:**
-
**Use cases:**
-
## Personas
| Persona | Cares about | Challenge | Value we promise |
|---------|-------------|-----------|------------------|
| | | | |
## Problems & Pain Points
**Core problem:**
**Why alternatives fall short:**
-
**What it costs them:**
**Emotional tension:**
## Competitive Landscape
**Direct:** [Competitor] — falls short because...
**Secondary:** [Approach] — falls short because...
**Indirect:** [Alternative] — falls short because...
## Differentiation
**Key differentiators:**
-
**How we do it differently:**
**Why that's better:**
**Why customers choose us:**
## Objections
| Objection | Response |
|-----------|----------|
| | |
**Anti-persona:**
## Switching Dynamics
**Push:**
**Pull:**
**Habit:**
**Anxiety:**
## Customer Language
**How they describe the problem:**
- "[verbatim]"
**How they describe us:**
- "[verbatim]"
**Words to use:**
**Words to avoid:**
**Glossary:**
| Term | Meaning |
|------|---------|
| | |
## Brand Voice
**Tone:**
**Style:**
**Personality:**
## Proof Points
**Metrics:**
**Customers:**
**Testimonials:**
> "[quote]" — [who]
**Value themes:**
| Theme | Proof |
|-------|-------|
| | |
## Goals
**Business goal:**
**Conversion action:**
**Current metrics:**
Step 4 — Confirm and Save
Show the completed document to the user.
Ask if anything needs adjustment.
Save to .agents/product-marketing.md:
# Ensure .agents directory exists
if (-not (Test-Path .agents)) { New-Item -ItemType Directory -Path .agents }
# Document is written by the agent directly to .agents\product-marketing.md
Set the *Last updated:* date to today.
Tell the user: "Other marketing skills will now use this context automatically. Run /product-marketing anytime to update it."
Sections to Capture
1. Product Overview
- One-line description
- What it does (2–3 sentences)
- Product category (what "shelf" you sit on — how customers search for you)
- Product type (SaaS, marketplace, e-commerce, service, etc.)
- Business model and pricing
2. Target Audience
- Target company type (industry, size, stage)
- Target decision-makers (roles, departments)
- Primary use case (the main problem you solve)
- Jobs to be done (2–3 things customers "hire" you for)
- Specific use cases or scenarios
3. Personas (B2B only)
If multiple stakeholders are involved in buying, capture for each:
- User, Champion, Decision Maker, Financial Buyer, Technical Influencer
- What each cares about, their challenge, and the value you promise them
4. Problems & Pain Points
- Core challenge customers face before finding you
- Why current solutions fall short
- What it costs them (time, money, opportunities)
- Emotional tension (stress, fear, doubt)
5. Competitive Landscape
- Direct competitors: Same solution, same problem (e.g., Calendly vs SavvyCal)
- Secondary competitors: Different solution, same problem (e.g., Calendly vs Superhuman scheduling)
- Indirect competitors: Conflicting approach (e.g., Calendly vs personal assistant)
- How each falls short for customers
6. Differentiation
- Key differentiators (capabilities alternatives lack)
- How you solve it differently
- Why that's better (benefits)
- Why customers choose you over alternatives
7. Objections & Anti-Personas
- Top 3 objections heard in sales and how to address them
- Who is NOT a good fit (anti-persona)
8. Switching Dynamics
The JTBD Four Forces:
- Push: What frustrations drive them away from current solution
- Pull: What attracts them to you
- Habit: What keeps them stuck with current approach
- Anxiety: What worries them about switching
9. Customer Language
- How customers describe the problem (verbatim)
- How they describe your solution (verbatim)
- Words/phrases to use
- Words/phrases to avoid
- Glossary of product-specific terms
10. Brand Voice
- Tone (professional, casual, playful, etc.)
- Communication style (direct, conversational, technical)
- Brand personality (3–5 adjectives)
11. Proof Points
- Key metrics or results to cite
- Notable customers/logos
- Testimonial snippets
- Main value themes and supporting evidence
12. Goals
- Primary business goal
- Key conversion action (what you want people to do)
- Current metrics (if known)
Keeping It Current
The document decays as the product evolves. Prompt the user to refresh it when any of these happen:
- Pricing or business model changes
- Repositioning, rebrand, or new product category
- A new ICP, segment, or persona becomes the focus
- A major launch adds capabilities that change differentiation
- Sales or support surfaces new objections or customer language
When updating, only re-gather the affected sections, and always bump the *Last updated* date. If the date is more than ~6 months old when another task reads it, suggest a review.
Pitfalls
- Inventing facts during auto-draft. This is the #1 risk. A fabricated metric or misattributed quote propagates into every ad, email, and landing page downstream skills produce. Always use
[TBD — needs input] when no source exists.
- Renaming section headings. Other marketing skills parse
.agents/product-marketing.md by section name. If you rename ## Differentiation to ## Why We're Better, downstream skills will fail to find the context they need.
- Dumping all questions at once. Overwhelms the user and produces shallow answers. Go one section at a time, confirm, then move on.
- Polishing customer language. Verbatim phrases — even grammatically imperfect ones — are more valuable than rewritten descriptions. They reflect how customers actually think and speak.
- Skipping the
*Last updated* date. Other skills check this date to decide whether to suggest a refresh. A missing or stale date breaks that signal.
- Forgetting legacy file locations. Older setups used
.claude/product-marketing.md or product-marketing-context.md. Always check all four paths before concluding no context exists.
- Writing all sections when only some changed. When updating, only re-gather affected sections. Rewriting the entire document wastes time and risks introducing errors in stable sections.
Verification
Confirm the file exists at the canonical path:
Test-Path .agents\product-marketing.md
Expected output: True
Verify all required section headings are present:
Select-String -Path .agents\product-marketing.md -Pattern "^## " | ForEach-Object { $_.Line }
Expected sections (at minimum):
## Product Overview
## Target Audience
## Problems & Pain Points
## Competitive Landscape
## Differentiation
## Objections
## Switching Dynamics
## Customer Language
## Brand Voice
## Proof Points
## Goals
Confirm the *Last updated* date is set and current:
Select-String -Path .agents\product-marketing.md -Pattern "Last updated:"
Check for unfilled placeholders that need user input:
Select-String -Path .agents\product-marketing.md -Pattern "\[TBD"
If matches are found, remind the user which sections still need input.
Confirm no legacy duplicates remain:
Test-Path .claude\product-marketing.md
Test-Path .agents\product-marketing-context.md
Test-Path .claude\product-marketing-context.md
All should return False after migration.
Tips
- Be specific: Ask "What's the #1 frustration that brings them to you?" not "What problem do they solve?"
- Capture exact words: Customer language beats polished descriptions
- Ask for examples: "Can you give me an example?" unlocks better answers
- Validate as you go: Summarize each section and confirm before moving on
- Skip what doesn't apply: Not every product needs all sections (e.g., Personas for B2C)
- Mark gaps honestly:
[TBD — needs input] beats a plausible guess
Related Skills
- competitors — For competitive deep dives and battlecard creation
- marketing-plan — For turning this context into a full marketing strategy
- pricing-strategy — For pricing and packaging decisions
1---
2name: product-marketing
3description: "Creates or updates .agents/product-marketing.md as the positioning source of truth (ICP, personas, differentiation, customer language) for downstream marketing skills. Use when the user mentions product or marketing context, ICP, positioning, or before writing ads and landing copy. Not for writing the ads, competitor battlecards, or a full marketing plan (those sibling skills). Do not invent metrics or testimonials."
4version: 2.1.1
5metadata:
6 source: https://skillmd.com/skills/kayforkind/product-marketing
7---
8
9# Product Marketing Context
10
11This skill creates and maintains a foundational product marketing context document at `.agents/product-marketing.md`. Other marketing skills (competitors, marketing-plan, pricing-strategy) reference this document so the user never repeats positioning, audience, or messaging details.
12
13## When to Use
14
15- Starting any new marketing project or campaign — run this **first** before other marketing skills
16- User says "set up context," "product context," "marketing context," "positioning," "who is my target audience," "describe my product," "ICP," "ideal customer profile"
17- User wants a single source of truth for product, audience, and competitive positioning
18- Before writing ads, emails, landing pages, or sales collateral that need consistent messaging
19- Refreshing stale context after product, pricing, or positioning changes
20
21## Prerequisites
22
23- A project repository with at least a README or basic product documentation (for auto-draft mode)
24- PowerShell on Windows as the primary host environment
25- Write access to the project root (the skill creates `.agents/product-marketing.md`)
26
27## Procedure
28
29### Step 1 — Check for Existing Context
30
311. Check if `.agents/product-marketing.md` already exists:
32
33 ```powershell
34 Test-Path .agents\product-marketing.md
35 ```
36
372. Also check legacy locations that older setups may have used:
38
39 ```powershell
40 Test-Path .claude\product-marketing.md
41 Test-Path .agents\product-marketing-context.md
42 Test-Path .claude\product-marketing-context.md
43 ```
44
453. **If the canonical file exists** at `.agents/product-marketing.md`:
46 - Read it and summarize what's captured
47 - Ask which sections the user wants to update
48 - Only gather info for those affected sections
49 - Jump to Step 3 to update
50
514. **If a legacy file exists** anywhere other than `.agents/product-marketing.md`:
52 - Offer to move it to the canonical location:
53
54 ```powershell
55 Move-Item .claude\product-marketing.md .agents\product-marketing.md -Force
56 ```
57
58 - Confirm the move, then read and summarize
59
605. **If no file exists anywhere**, offer two options:
61
62 - **Option A — Auto-draft from codebase (recommended):** Study the repo and draft a V1. The user reviews, corrects, and fills gaps. Faster than starting from scratch.
63 - **Option B — Start from scratch:** Walk through each section conversationally, one at a time.
64
65 Most users prefer Option A. After presenting the draft, ask: "What needs correcting? What's missing?"
66
67### Step 2 — Gather Information
68
69#### If Auto-Drafting (Option A)
70
711. Read the codebase for source material:
72 - `README.md`, `README.*`, or `readme.*`
73 - Landing pages, marketing copy, about pages, pricing pages (HTML, MDX, JSX, etc.)
74 - Meta descriptions and `<title>` tags
75 - `package.json` (description, keywords, homepage fields)
76 - `CHANGELOG.md` or changelog entries
77 - Any existing docs (`docs/`, `*.md` files)
78
792. Draft every section listed in "Sections to Capture" below based on what you find.
80
813. Present the full draft and ask what needs correcting or is missing.
82
834. Iterate until the user is satisfied.
84
85**HARD RULE — Never invent facts while auto-drafting.** Metrics, customer names, testimonials, competitor shortcomings, and verbatim quotes must come from the repo or the user. If a section has no source, write `[TBD — needs input]` and ask. A wrong "fact" here propagates into every ad, email, and page the other skills produce.
86
87#### If Starting from Scratch (Option B)
88
89Walk through each section in "Sections to Capture" conversationally, one at a time. Do not dump all questions at once.
90
91For each section:
921. Briefly explain what you're capturing and why
932. Ask relevant, specific questions (see Tips below)
943. Confirm accuracy by summarizing back
954. Move to the next section
96
97Push for **verbatim customer language** — exact phrases are more valuable than polished descriptions because they reflect how customers actually think and speak, which makes downstream copy more resonant.
98
99### Step 3 — Create or Update the Document
100
101After gathering information, create or update `.agents/product-marketing.md` using this exact structure. Keep section names stable — other marketing skills parse the document by section heading.
102
103```markdown
104# Product Marketing Context
105
106*Last updated: [date]*
107
108## Product Overview
109**One-liner:**
110**What it does:**
111**Product category:**
112**Product type:**
113**Business model:**
114
115## Target Audience
116**Target companies:**
117**Decision-makers:**
118**Primary use case:**
119**Jobs to be done:**
120-
121**Use cases:**
122-
123
124## Personas
125| Persona | Cares about | Challenge | Value we promise |
126|---------|-------------|-----------|------------------|
127| | | | |
128
129## Problems & Pain Points
130**Core problem:**
131**Why alternatives fall short:**
132-
133**What it costs them:**
134**Emotional tension:**
135
136## Competitive Landscape
137**Direct:** [Competitor] — falls short because...
138**Secondary:** [Approach] — falls short because...
139**Indirect:** [Alternative] — falls short because...
140
141## Differentiation
142**Key differentiators:**
143-
144**How we do it differently:**
145**Why that's better:**
146**Why customers choose us:**
147
148## Objections
149| Objection | Response |
150|-----------|----------|
151| | |
152
153**Anti-persona:**
154
155## Switching Dynamics
156**Push:**
157**Pull:**
158**Habit:**
159**Anxiety:**
160
161## Customer Language
162**How they describe the problem:**
163- "[verbatim]"
164**How they describe us:**
165- "[verbatim]"
166**Words to use:**
167**Words to avoid:**
168**Glossary:**
169| Term | Meaning |
170|------|---------|
171| | |
172
173## Brand Voice
174**Tone:**
175**Style:**
176**Personality:**
177
178## Proof Points
179**Metrics:**
180**Customers:**
181**Testimonials:**
182> "[quote]" — [who]
183**Value themes:**
184| Theme | Proof |
185|-------|-------|
186| | |
187
188## Goals
189**Business goal:**
190**Conversion action:**
191**Current metrics:**
192```
193
194### Step 4 — Confirm and Save
195
1961. Show the completed document to the user.
1972. Ask if anything needs adjustment.
1983. Save to `.agents/product-marketing.md`:
199
200 ```powershell
201 # Ensure .agents directory exists
202 if (-not (Test-Path .agents)) { New-Item -ItemType Directory -Path .agents }
203 # Document is written by the agent directly to .agents\product-marketing.md
204 ```
205
2064. Set the `*Last updated:*` date to today.
2075. Tell the user: "Other marketing skills will now use this context automatically. Run `/product-marketing` anytime to update it."
208
209---
210
211## Sections to Capture
212
213### 1. Product Overview
214- One-line description
215- What it does (2–3 sentences)
216- Product category (what "shelf" you sit on — how customers search for you)
217- Product type (SaaS, marketplace, e-commerce, service, etc.)
218- Business model and pricing
219
220### 2. Target Audience
221- Target company type (industry, size, stage)
222- Target decision-makers (roles, departments)
223- Primary use case (the main problem you solve)
224- Jobs to be done (2–3 things customers "hire" you for)
225- Specific use cases or scenarios
226
227### 3. Personas (B2B only)
228If multiple stakeholders are involved in buying, capture for each:
229- User, Champion, Decision Maker, Financial Buyer, Technical Influencer
230- What each cares about, their challenge, and the value you promise them
231
232### 4. Problems & Pain Points
233- Core challenge customers face before finding you
234- Why current solutions fall short
235- What it costs them (time, money, opportunities)
236- Emotional tension (stress, fear, doubt)
237
238### 5. Competitive Landscape
239- **Direct competitors**: Same solution, same problem (e.g., Calendly vs SavvyCal)
240- **Secondary competitors**: Different solution, same problem (e.g., Calendly vs Superhuman scheduling)
241- **Indirect competitors**: Conflicting approach (e.g., Calendly vs personal assistant)
242- How each falls short for customers
243
244### 6. Differentiation
245- Key differentiators (capabilities alternatives lack)
246- How you solve it differently
247- Why that's better (benefits)
248- Why customers choose you over alternatives
249
250### 7. Objections & Anti-Personas
251- Top 3 objections heard in sales and how to address them
252- Who is NOT a good fit (anti-persona)
253
254### 8. Switching Dynamics
255The JTBD Four Forces:
256- **Push**: What frustrations drive them away from current solution
257- **Pull**: What attracts them to you
258- **Habit**: What keeps them stuck with current approach
259- **Anxiety**: What worries them about switching
260
261### 9. Customer Language
262- How customers describe the problem (verbatim)
263- How they describe your solution (verbatim)
264- Words/phrases to use
265- Words/phrases to avoid
266- Glossary of product-specific terms
267
268### 10. Brand Voice
269- Tone (professional, casual, playful, etc.)
270- Communication style (direct, conversational, technical)
271- Brand personality (3–5 adjectives)
272
273### 11. Proof Points
274- Key metrics or results to cite
275- Notable customers/logos
276- Testimonial snippets
277- Main value themes and supporting evidence
278
279### 12. Goals
280- Primary business goal
281- Key conversion action (what you want people to do)
282- Current metrics (if known)
283
284---
285
286## Keeping It Current
287
288The document decays as the product evolves. Prompt the user to refresh it when any of these happen:
289
290- Pricing or business model changes
291- Repositioning, rebrand, or new product category
292- A new ICP, segment, or persona becomes the focus
293- A major launch adds capabilities that change differentiation
294- Sales or support surfaces new objections or customer language
295
296When updating, only re-gather the affected sections, and always bump the `*Last updated*` date. If the date is more than ~6 months old when another task reads it, suggest a review.
297
298## Pitfalls
299
300- **Inventing facts during auto-draft.** This is the #1 risk. A fabricated metric or misattributed quote propagates into every ad, email, and landing page downstream skills produce. Always use `[TBD — needs input]` when no source exists.
301- **Renaming section headings.** Other marketing skills parse `.agents/product-marketing.md` by section name. If you rename `## Differentiation` to `## Why We're Better`, downstream skills will fail to find the context they need.
302- **Dumping all questions at once.** Overwhelms the user and produces shallow answers. Go one section at a time, confirm, then move on.
303- **Polishing customer language.** Verbatim phrases — even grammatically imperfect ones — are more valuable than rewritten descriptions. They reflect how customers actually think and speak.
304- **Skipping the `*Last updated*` date.** Other skills check this date to decide whether to suggest a refresh. A missing or stale date breaks that signal.
305- **Forgetting legacy file locations.** Older setups used `.claude/product-marketing.md` or `product-marketing-context.md`. Always check all four paths before concluding no context exists.
306- **Writing all sections when only some changed.** When updating, only re-gather affected sections. Rewriting the entire document wastes time and risks introducing errors in stable sections.
307
308## Verification
309
3101. Confirm the file exists at the canonical path:
311
312 ```powershell
313 Test-Path .agents\product-marketing.md
314 ```
315
316 Expected output: `True`
317
3182. Verify all required section headings are present:
319
320 ```powershell
321 Select-String -Path .agents\product-marketing.md -Pattern "^## " | ForEach-Object { $_.Line }
322 ```
323
324 Expected sections (at minimum):
325 - `## Product Overview`
326 - `## Target Audience`
327 - `## Problems & Pain Points`
328 - `## Competitive Landscape`
329 - `## Differentiation`
330 - `## Objections`
331 - `## Switching Dynamics`
332 - `## Customer Language`
333 - `## Brand Voice`
334 - `## Proof Points`
335 - `## Goals`
336
3373. Confirm the `*Last updated*` date is set and current:
338
339 ```powershell
340 Select-String -Path .agents\product-marketing.md -Pattern "Last updated:"
341 ```
342
3434. Check for unfilled placeholders that need user input:
344
345 ```powershell
346 Select-String -Path .agents\product-marketing.md -Pattern "\[TBD"
347 ```
348
349 If matches are found, remind the user which sections still need input.
350
3515. Confirm no legacy duplicates remain:
352
353 ```powershell
354 Test-Path .claude\product-marketing.md
355 Test-Path .agents\product-marketing-context.md
356 Test-Path .claude\product-marketing-context.md
357 ```
358
359 All should return `False` after migration.
360
361## Tips
362
363- **Be specific**: Ask "What's the #1 frustration that brings them to you?" not "What problem do they solve?"
364- **Capture exact words**: Customer language beats polished descriptions
365- **Ask for examples**: "Can you give me an example?" unlocks better answers
366- **Validate as you go**: Summarize each section and confirm before moving on
367- **Skip what doesn't apply**: Not every product needs all sections (e.g., Personas for B2C)
368- **Mark gaps honestly**: `[TBD — needs input]` beats a plausible guess
369
370## Related Skills
371
372- **competitors** — For competitive deep dives and battlecard creation
373- **marketing-plan** — For turning this context into a full marketing strategy
374- **pricing-strategy** — For pricing and packaging decisions