Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From craft-workspace-webconsulting-skills
Creates and updates a product marketing context document (.agents/product-marketing.md) capturing product positioning, audience, and messaging. Use before other marketing skills to establish reusable foundational context.
npx claudepluginhub dirnbauer/webconsulting-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/craft-workspace-webconsulting-skills:product-marketingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
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.
Creates and updates product marketing context MD file with overview, target audience, ICP, and positioning. Auto-drafts from repo README/package.json or gathers interactively.
Creates or updates reusable product marketing context document with positioning, audience, ICP, use cases, and messaging. Auto-drafts from repo or builds from scratch; use at project start.
Creates and maintains a product marketing context document capturing positioning, audience, and messaging. Use at project start to avoid repeating foundational info.
Share bugs, ideas, or general feedback.
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.md.
First, check if .agents/product-marketing.md already exists. Also check .claude/product-marketing.md and the legacy filename product-marketing-context.md (in either .agents/ or .claude/) for older setups — if found anywhere other than .agents/product-marketing.md, offer to move it to the canonical location.
If it exists:
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?"
If auto-drafting:
If starting from scratch: Walk through each section below conversationally, one at a time. Don't dump all questions at once.
For each 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 copy more resonant.
If multiple stakeholders are involved in buying, capture for each:
The JTBD Four Forces:
After gathering information, create .agents/product-marketing.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:**
.agents/product-marketing.md/product-marketing anytime to update it."This skill is based on the excellent work by Corey Haines.
Original repository: https://github.com/coreyhaines31/marketingskills
Special thanks to Corey Haines for their generous open-source contributions, which helped shape this skill collection. Adapted by webconsulting.at for this skill collection