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.
When to Use
- Use when creating a reusable product, audience, and positioning context file.
- Use at the start of a marketing project before more specialized marketing skills.
- Use when the user wants to avoid re-explaining ICP, messaging, and product basics.
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)
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
1---2name: product-marketing-context3description: Create or update a reusable product marketing context document with positioning, audience, ICP, use cases, and messaging. Use at the start of a project to avoid repeating core marketing context across tasks.4metadata:5 source: https://skillmd.com/skills/iradoweck/product-marketing-context6 version: 1.1.07 aas-risk: critical8 aas-source: https://github.com/coreyhaines31/marketingskills9 aas-date-added: '2026-03-21'10---1112# Product Marketing Context1314You 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.1516## When to Use17- Use when creating a reusable product, audience, and positioning context file.18- Use at the start of a marketing project before more specialized marketing skills.19- Use when the user wants to avoid re-explaining ICP, messaging, and product basics.2021The document is stored at `.agents/product-marketing-context.md`.2223## Workflow2425### Step 1: Check for Existing Context2627First, 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.2829**If it exists:**30- Read it and summarize what's captured31- Ask which sections they want to update32- Only gather info for those sections3334**If it doesn't exist, offer two options:**35361. **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.37382. **Start from scratch**: Walk through each section conversationally, gathering info one section at a time.3940Most users prefer option 1. After presenting the draft, ask: "What needs correcting? What's missing?"4142### Step 2: Gather Information4344**If auto-drafting:**451. Read the codebase: README, landing pages, marketing copy, about pages, meta descriptions, package.json, any existing docs462. Draft all sections based on what you find473. Present the draft and ask what needs correcting or is missing484. Iterate until the user is satisfied4950**If starting from scratch:**51Walk through each section below conversationally, one at a time. Don't dump all questions at once.5253For each section:541. Briefly explain what you're capturing552. Ask relevant questions563. Confirm accuracy574. Move to the next5859Push 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.6061---6263## Sections to Capture6465### 1. Product Overview66- One-line description67- What it does (2-3 sentences)68- Product category (what "shelf" you sit on—how customers search for you)69- Product type (SaaS, marketplace, e-commerce, service, etc.)70- Business model and pricing7172### 2. Target Audience73- Target company type (industry, size, stage)74- Target decision-makers (roles, departments)75- Primary use case (the main problem you solve)76- Jobs to be done (2-3 things customers "hire" you for)77- Specific use cases or scenarios7879### 3. Personas (B2B only)80If multiple stakeholders are involved in buying, capture for each:81- User, Champion, Decision Maker, Financial Buyer, Technical Influencer82- What each cares about, their challenge, and the value you promise them8384### 4. Problems & Pain Points85- Core challenge customers face before finding you86- Why current solutions fall short87- What it costs them (time, money, opportunities)88- Emotional tension (stress, fear, doubt)8990### 5. Competitive Landscape91- **Direct competitors**: Same solution, same problem (e.g., Calendly vs SavvyCal)92- **Secondary competitors**: Different solution, same problem (e.g., Calendly vs Superhuman scheduling)93- **Indirect competitors**: Conflicting approach (e.g., Calendly vs personal assistant)94- How each falls short for customers9596### 6. Differentiation97- Key differentiators (capabilities alternatives lack)98- How you solve it differently99- Why that's better (benefits)100- Why customers choose you over alternatives101102### 7. Objections & Anti-Personas103- Top 3 objections heard in sales and how to address them104- Who is NOT a good fit (anti-persona)105106### 8. Switching Dynamics107The JTBD Four Forces:108- **Push**: What frustrations drive them away from current solution109- **Pull**: What attracts them to you110- **Habit**: What keeps them stuck with current approach111- **Anxiety**: What worries them about switching112113### 9. Customer Language114- How customers describe the problem (verbatim)115- How they describe your solution (verbatim)116- Words/phrases to use117- Words/phrases to avoid118- Glossary of product-specific terms119120### 10. Brand Voice121- Tone (professional, casual, playful, etc.)122- Communication style (direct, conversational, technical)123- Brand personality (3-5 adjectives)124125### 11. Proof Points126- Key metrics or results to cite127- Notable customers/logos128- Testimonial snippets129- Main value themes and supporting evidence130131### 12. Goals132- Primary business goal133- Key conversion action (what you want people to do)134- Current metrics (if known)135136---137138## Step 3: Create the Document139140After gathering information, create `.agents/product-marketing-context.md` with this structure:141142```markdown143# Product Marketing Context144145*Last updated: [date]*146147## Product Overview148**One-liner:**149**What it does:**150**Product category:**151**Product type:**152**Business model:**153154## Target Audience155**Target companies:**156**Decision-makers:**157**Primary use case:**158**Jobs to be done:**159-160**Use cases:**161-162163## Personas164| Persona | Cares about | Challenge | Value we promise |165|---------|-------------|-----------|------------------|166| | | | |167168## Problems & Pain Points169**Core problem:**170**Why alternatives fall short:**171-172**What it costs them:**173**Emotional tension:**174175## Competitive Landscape176**Direct:** [Competitor] — falls short because...177**Secondary:** [Approach] — falls short because...178**Indirect:** [Alternative] — falls short because...179180## Differentiation181**Key differentiators:**182-183**How we do it differently:**184**Why that's better:**185**Why customers choose us:**186187## Objections188| Objection | Response |189|-----------|----------|190| | |191192**Anti-persona:**193194## Switching Dynamics195**Push:**196**Pull:**197**Habit:**198**Anxiety:**199200## Customer Language201**How they describe the problem:**202- "[verbatim]"203**How they describe us:**204- "[verbatim]"205**Words to use:**206**Words to avoid:**207**Glossary:**208| Term | Meaning |209|------|---------|210| | |211212## Brand Voice213**Tone:**214**Style:**215**Personality:**216217## Proof Points218**Metrics:**219**Customers:**220**Testimonials:**221> "[quote]" — [who]222**Value themes:**223| Theme | Proof |224|-------|-------|225| | |226227## Goals228**Business goal:**229**Conversion action:**230**Current metrics:**231```232233---234235## Step 4: Confirm and Save236237- Show the completed document238- Ask if anything needs adjustment239- Save to `.agents/product-marketing-context.md`240- Tell them: "Other marketing skills will now use this context automatically. Run `/product-marketing-context` anytime to update it."241242---243244## Tips245246- **Be specific**: Ask "What's the #1 frustration that brings them to you?" not "What problem do they solve?"247- **Capture exact words**: Customer language beats polished descriptions248- **Ask for examples**: "Can you give me an example?" unlocks better answers249- **Validate as you go**: Summarize each section and confirm before moving on250- **Skip what doesn't apply**: Not every product needs all sections (e.g., Personas for B2C)251252## Limitations253- Use this skill only when the task clearly matches the scope described above.254- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.255- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.