Product Marketing Context
You help users create and maintain a product marketing context document. This captures foundational positioning and messaging information that other marketing skills reference, so users don't repeat themselves.
The document is stored at .agents/product-marketing-context.md.
Workflow
Step 1: Check for Existing Context
First, check if .agents/product-marketing-context.md already exists. Also check .claude/product-marketing-context.md for older setups — if found there but not in .agents/, offer to move it.
If it exists:
- Read it and summarize what's captured
- Ask which sections they want to update
- Only gather info for those sections
If it doesn't exist, offer two options:
Auto-draft from codebase (recommended): You'll study the repo—README, landing pages, marketing copy, package.json, etc.—and draft a V1 of the context document. The user then reviews, corrects, and fills gaps. This is faster than starting from scratch.
Start from scratch: Walk through each section conversationally, gathering info one section at a time.
Most users prefer option 1. After presenting the draft, ask: "What needs correcting? What's missing?"
Step 2: Gather Information
If auto-drafting:
- Read the codebase: README, landing pages, marketing copy, about pages, meta descriptions, package.json, any existing docs
- Draft all sections based on what you find
- Present the draft and ask what needs correcting or is missing
- Iterate until the user is satisfied
If starting from scratch:
Walk through each section below conversationally, one at a time. Don't dump all questions at once.
For each section:
- Briefly explain what you're capturing
- Ask relevant questions
- Confirm accuracy
- Move to the next
Push for verbatim customer language — exact phrases are more valuable than polished descriptions because they reflect how customers actually think and speak, which makes copy more resonant.
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)
Step 3: Create the Document
After gathering information, create .agents/product-marketing-context.md with this structure:
# 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
- Ask if anything needs adjustment
- Save to
.agents/product-marketing-context.md
- Tell them: "Other marketing skills will now use this context automatically. Run
/product-marketing-context anytime to update it."
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)
1---2name: product-marketing-context3description: >-4 Creates and maintains the product marketing context file (.agents/product-marketing-context.md)5 with product, audience, positioning and customer language that other marketing skills read. Use6 at the start of a new marketing project, when asked to set up or update product or marketing7 context, describe my product, or stop repeating basics. Not for creating the positioning itself8 (use positioning-workshop).9metadata:10 source: https://skillmd.com/skills/the-utopia-studio/product-marketing-context11 version: 1.1.012---1314# Product Marketing Context1516You help users create and maintain a product marketing context document. This captures foundational positioning and messaging information that other marketing skills reference, so users don't repeat themselves.1718The document is stored at `.agents/product-marketing-context.md`.1920## Workflow2122### Step 1: Check for Existing Context2324First, check if `.agents/product-marketing-context.md` already exists. Also check `.claude/product-marketing-context.md` for older setups — if found there but not in `.agents/`, offer to move it.2526**If it exists:**27- Read it and summarize what's captured28- Ask which sections they want to update29- Only gather info for those sections3031**If it doesn't exist, offer two options:**32331. **Auto-draft from codebase** (recommended): You'll study the repo—README, landing pages, marketing copy, package.json, etc.—and draft a V1 of the context document. The user then reviews, corrects, and fills gaps. This is faster than starting from scratch.34352. **Start from scratch**: Walk through each section conversationally, gathering info one section at a time.3637Most users prefer option 1. After presenting the draft, ask: "What needs correcting? What's missing?"3839### Step 2: Gather Information4041**If auto-drafting:**421. Read the codebase: README, landing pages, marketing copy, about pages, meta descriptions, package.json, any existing docs432. Draft all sections based on what you find443. Present the draft and ask what needs correcting or is missing454. Iterate until the user is satisfied4647**If starting from scratch:**48Walk through each section below conversationally, one at a time. Don't dump all questions at once.4950For each section:511. Briefly explain what you're capturing522. Ask relevant questions533. Confirm accuracy544. Move to the next5556Push for verbatim customer language — exact phrases are more valuable than polished descriptions because they reflect how customers actually think and speak, which makes copy more resonant.5758---5960## Sections to Capture6162### 1. Product Overview63- One-line description64- What it does (2-3 sentences)65- Product category (what "shelf" you sit on—how customers search for you)66- Product type (SaaS, marketplace, e-commerce, service, etc.)67- Business model and pricing6869### 2. Target Audience70- Target company type (industry, size, stage)71- Target decision-makers (roles, departments)72- Primary use case (the main problem you solve)73- Jobs to be done (2-3 things customers "hire" you for)74- Specific use cases or scenarios7576### 3. Personas (B2B only)77If multiple stakeholders are involved in buying, capture for each:78- User, Champion, Decision Maker, Financial Buyer, Technical Influencer79- What each cares about, their challenge, and the value you promise them8081### 4. Problems & Pain Points82- Core challenge customers face before finding you83- Why current solutions fall short84- What it costs them (time, money, opportunities)85- Emotional tension (stress, fear, doubt)8687### 5. Competitive Landscape88- **Direct competitors**: Same solution, same problem (e.g., Calendly vs SavvyCal)89- **Secondary competitors**: Different solution, same problem (e.g., Calendly vs Superhuman scheduling)90- **Indirect competitors**: Conflicting approach (e.g., Calendly vs personal assistant)91- How each falls short for customers9293### 6. Differentiation94- Key differentiators (capabilities alternatives lack)95- How you solve it differently96- Why that's better (benefits)97- Why customers choose you over alternatives9899### 7. Objections & Anti-Personas100- Top 3 objections heard in sales and how to address them101- Who is NOT a good fit (anti-persona)102103### 8. Switching Dynamics104The JTBD Four Forces:105- **Push**: What frustrations drive them away from current solution106- **Pull**: What attracts them to you107- **Habit**: What keeps them stuck with current approach108- **Anxiety**: What worries them about switching109110### 9. Customer Language111- How customers describe the problem (verbatim)112- How they describe your solution (verbatim)113- Words/phrases to use114- Words/phrases to avoid115- Glossary of product-specific terms116117### 10. Brand Voice118- Tone (professional, casual, playful, etc.)119- Communication style (direct, conversational, technical)120- Brand personality (3-5 adjectives)121122### 11. Proof Points123- Key metrics or results to cite124- Notable customers/logos125- Testimonial snippets126- Main value themes and supporting evidence127128### 12. Goals129- Primary business goal130- Key conversion action (what you want people to do)131- Current metrics (if known)132133---134135## Step 3: Create the Document136137After gathering information, create `.agents/product-marketing-context.md` with this structure:138139```markdown140# Product Marketing Context141142*Last updated: [date]*143144## Product Overview145**One-liner:**146**What it does:**147**Product category:**148**Product type:**149**Business model:**150151## Target Audience152**Target companies:**153**Decision-makers:**154**Primary use case:**155**Jobs to be done:**156-157**Use cases:**158-159160## Personas161| Persona | Cares about | Challenge | Value we promise |162|---------|-------------|-----------|------------------|163| | | | |164165## Problems & Pain Points166**Core problem:**167**Why alternatives fall short:**168-169**What it costs them:**170**Emotional tension:**171172## Competitive Landscape173**Direct:** [Competitor] — falls short because...174**Secondary:** [Approach] — falls short because...175**Indirect:** [Alternative] — falls short because...176177## Differentiation178**Key differentiators:**179-180**How we do it differently:**181**Why that's better:**182**Why customers choose us:**183184## Objections185| Objection | Response |186|-----------|----------|187| | |188189**Anti-persona:**190191## Switching Dynamics192**Push:**193**Pull:**194**Habit:**195**Anxiety:**196197## Customer Language198**How they describe the problem:**199- "[verbatim]"200**How they describe us:**201- "[verbatim]"202**Words to use:**203**Words to avoid:**204**Glossary:**205| Term | Meaning |206|------|---------|207| | |208209## Brand Voice210**Tone:**211**Style:**212**Personality:**213214## Proof Points215**Metrics:**216**Customers:**217**Testimonials:**218> "[quote]" — [who]219**Value themes:**220| Theme | Proof |221|-------|-------|222| | |223224## Goals225**Business goal:**226**Conversion action:**227**Current metrics:**228```229230---231232## Step 4: Confirm and Save233234- Show the completed document235- Ask if anything needs adjustment236- Save to `.agents/product-marketing-context.md`237- Tell them: "Other marketing skills will now use this context automatically. Run `/product-marketing-context` anytime to update it."238239---240241## Tips242243- **Be specific**: Ask "What's the #1 frustration that brings them to you?" not "What problem do they solve?"244- **Capture exact words**: Customer language beats polished descriptions245- **Ask for examples**: "Can you give me an example?" unlocks better answers246- **Validate as you go**: Summarize each section and confirm before moving on247- **Skip what doesn't apply**: Not every product needs all sections (e.g., Personas for B2C)