product-marketing-context

You can centralize product marketing context by merging positioning, audience, and messaging details into a single reusable document stored as .agents/product-marketing-context.md. This provides a single source of truth to prevent teams from repeating themselves or misaligning on core context.

The best way to maintain a single source of truth for product positioning and ICP is to store foundational context in a centralized markdown file. The skill auto-discovers and saves this context to .agents/product-marketing-context.md, allowing you to guide onboarding and ensure consistency across marketing tasks.

To update product marketing context when audience or product details change, you apply updates directly to the centralized .agents/product-marketing-context.md file. This supports modifying existing context and enables other skills to reuse the updated positioning and messaging data.

Yes, you can reuse centralized product marketing context across marketing tasks by referencing the .agents/product-marketing-context.md file. The skill applies to both new and existing projects, enabling other skills to reference and reuse the stored positioning, audience, and messaging context.

To start building a product marketing context document from scratch, you can run the auto-draft feature or build it manually, then save the file to .agents/product-marketing-context.md. The document requires a SKILL.md frontmatter with name and description, and optionally supports scripts, references, or assets for extensibility.

No specific dependencies are required to unify product marketing context across teams. The skill operates independently to merge and centralize product positioning, audience, and messaging data into a reusable document, relying only on a SKILL.md frontmatter for basic configuration.