A product marketing context document is a reusable positioning brief stored at `.agents/product-marketing.md` that other marketing skills read so you don't repeat foundational details on every task. It captures your product overview and category, target audience and ICP, buying personas, problems and pain points, competitive landscape (direct, secondary, and indirect), differentiation, objections and anti-personas, JTBD switching forces (push, pull, habit, anxiety), verbatim customer language, brand voice, proof points, and goals. The fastest way to create it is to auto-draft a V1 from your existing codebase — README, landing pages, pricing, meta descriptions — then review and correct it. Every substantive update bumps a document version and prepends a dated changelog entry naming what changed and why, so your positioning history stays traceable.
What's inside
The playbook covers
See it in action
I want to set up my product marketing context. We're a B2B SaaS company that sells a customer feedback platform to product teams.
# Product Marketing Context **Document version:** v3 **Last updated:** 2026-07-16 ## Product Overview **One-liner:** Deliverability platform that gets more email into the inbox. **Product category:** Email deliverability **Product type:** B2B SaaS ## Target Audience **Decision-makers:** Lifecycle marketers, RevOps **Jobs to be done:** - Stop landing in spam - Prove sender reputation to the team ## Changelog *Newest first.* - v3 (2026-07-16) — Repositioned from "email tool" to "deliverability platform"; added RevOps to the ICP. - v2 (2026-06-02) — Rewrote value prop and objections after 5 customer interviews. - v1 (2026-05-10) — Initial context.
FAQ
What is a product marketing context document?
It's a foundational positioning brief stored at `.agents/product-marketing.md` that captures your product, audience, competitors, differentiation, customer language, brand voice, and goals in one place. Other marketing skills — copywriting, CRO, SEO, and more — check for it first and use it automatically, so you set your context once instead of re-explaining it on every task.
What's the fastest way to create one?
Auto-draft it from your codebase. The agent reads your README, landing pages, pricing and about pages, meta descriptions, and existing docs to draft a V1 across all sections, then presents it for you to correct and fill gaps. Most people prefer this over starting from scratch because it's faster and grounded in what you've already written.
How are updates and versioning handled?
Every substantive change bumps the document version (v2 → v3), updates the "Last updated" date, and prepends a newest-first changelog entry naming which sections changed and why — for example, "Repositioned from email tool to deliverability platform; added RevOps to the ICP." Past entries are never rewritten or reordered, and pure typo fixes skip the version bump. The changelog gives you a paper trail of how your positioning has evolved.
Build a tool for this workflow?
Marketers run this skill mid-task — the exact moment your tool matters. Partner tiers put your tool inside the skill their agent runs.
See partner tiers