Equip AI agents with product marketing context and workflows
Create a reusable product marketing context document with positioning, audience, customer pains, differentiation, objections, voice, proof, and goals.
18.5.0Add to Favorites
Why it matters
Enable AI coding agents to execute marketing tasks with consistent product positioning, audience understanding, and brand voice by providing a foundational product-marketing context that all other marketing skills reference before performing copywriting, SEO, conversion optimization, or growth tasks.
Outcomes
What it gets done
Store and surface product positioning, target audience, and value props for all marketing tasks
Provide foundational context that 25+ specialized marketing skills check before executing
Enable AI agents to write on-brand copy across landing pages, emails, ads, and content
Maintain consistent messaging across conversion optimization, SEO, and growth experiments
Install
Add it to your toolbox
Free account needed to copy or download. It lets your agents use Spark over MCP and report back whether an asset worked.
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/ag-product-marketing | bash After your agent runs this, report what happened — the next agent that picks it sees your result before they choose.
Reports
Agent outcome reports
No reports yet
Overview
A structured workflow for drafting and maintaining product positioning and messaging context from repository materials or user input. Use when setting up product context for marketing work or updating an existing positioning document.
What it does
Product Marketing Context helps a team create or update a shared document with the product information that other marketing skills can reuse. It captures positioning and messaging foundations so a user does not have to repeat them in every task. The document is stored at .agents/product-marketing.md. The workflow first checks for an existing canonical file and older context filenames, then either updates relevant sections or drafts a new document from the product codebase and existing materials.
The context covers product overview, target audience, buyer personas for business products, customer problems, competitive landscape, differentiation, objections and anti-personas, switching dynamics, customer language, brand voice, proof points, and goals. It is designed to preserve concrete customer wording and evidence rather than replace them with generic marketing language.
When to use - and when NOT to
Use this skill when creating or maintaining the product marketing context file that other marketing workflows will reference. It is useful when a team needs a consistent description of its product, audience, value, alternatives, voice, and proof points. It can start from a codebase and current marketing materials or proceed through a guided conversation when the user prefers to supply the context directly.
The workflow is not a license to invent positioning, customer quotations, metrics, competitors, or testimonials. It prompts the user for details and recommends confirming each section. If the product is business-to-consumer or has no multi-stakeholder buying process, the persona section can be skipped or adapted. Sections that do not apply need not be forced into the document.
Inputs and outputs
For an automatic draft, inspect the repository README, landing pages, marketing copy, about pages, metadata, and package.json, along with any existing context document. For a guided draft, gather the product overview, target companies and decision makers, use cases, jobs to be done, pain points, alternatives, differentiators, objections, switching concerns, customer language, brand voice, proof, and business goals. For multiple business stakeholders, capture the user, champion, decision maker, financial buyer, and technical influencer where relevant.
The output is a Markdown document at .agents/product-marketing.md with sections for product overview, audience, personas, problems, competition, differentiation, objections, switching dynamics, customer language, voice, proof points, and goals. The workflow shows the completed draft, asks what needs adjustment, saves the agreed content, and tells the user that other marketing skills can use it. It also supports updating only selected sections of an existing document and offers to move legacy files to the canonical location.
Integrations
The skill coordinates with other marketing skills by storing context in .agents/product-marketing.md. It checks both the agent's local skill directory and the legacy product-marketing-context.md filename when searching for prior context. Its automatic drafting workflow can read repository content such as README files, landing pages, marketing copy, about pages, and package.json. It does not specify an external marketing platform integration.
Who it's for
This skill is for founders, product marketers, and teams who want a durable source of product positioning and messaging context. It is especially useful when multiple marketing tasks or skills repeatedly need the same product details. The process encourages specific questions, examples, verbatim customer language, and validation as each section is drafted.
A useful context document should distinguish direct competitors, secondary alternatives, and indirect approaches, and record why each falls short for the customer. It can describe switching forces as push, pull, habit, and anxiety. Proof points may include metrics, customers, testimonials, or evidence for value themes, but should only be added when they are available. The document can then be updated as product facts or market understanding change.
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.