Product Marketing (Every Ship)

What it does

Product Marketing (Every Ship) is a Cursor agent playbook named product-marketer. AgenticKit installs it so a session can adopt this role instead of acting as a generic coding assistant.

The product-marketer agent runs after /ship or /release. launch-coordinator owns the public launch week. This role owns the weekly 'we shipped this, here's why it matters' pack from product truth only.

After every ship: why the customer should care. Turns a git/ship into customer-language changelog, one email, one social, and an in-app blurb. Not a once-a-year launch.

Why it exists

A pile of agent files is not a team. product-marketer exists so one job, product marketing (every ship), has a written brief, required skills, and a stop condition.

It ships in the Marketing Kit. Skills it must read: Ship-to-Customer Feature Narrative; Brand Voice Guidelines & Jargon Elimination; Marketing Deliverable Auto-Save & Repo Sync. Commands that adopt this role: /whats-new: Ship-to-Customer Narrative; /release: Release Notes & Changelog Generator; /linkedin-post: LinkedIn Thought Leadership & Growth Post.

When to use it

• You shipped and told nobody
• Changelog that reads like git log
• Need one story for email, social, and the app

When not to use it

• Do not ask product-marketer to do a different role's job. If you need a migration, switch agents.
• Do not keep the same chat after this agent has finished its artifact. Start a reviewer in a new thread.
• Do not invoke every agent in the kit for a small change.

Example workflow

1. Install the Marketing Kit so .cursor/agents/product-marketer is on disk.
2. Run /whats-new: Ship-to-Customer Narrative, or start a chat and tell Cursor to adopt the product-marketer role.
3. The agent should read: Ship-to-Customer Feature Narrative; Brand Voice Guidelines & Jargon Elimination; Marketing Deliverable Auto-Save & Repo Sync.
4. It produces the artifact for this role only, then stops.
5. A different agent or you review. Same-chat self-review is not a review.

Example usage

Example: "You are product-marketer. You shipped and told nobody. Read feature-narrative before you edit."

Or let the pipeline invoke it: /whats-new: Ship-to-Customer Narrative.

Capabilities you should actually see: Customer-language changelog from a real diff

Example output

• product-marketer should leave files or a written verdict, not a vibe check. Customer-language changelog from a real diff Email + social + in-app blurbs from one narrative
• Marketing agents write markdown under docs/marketing/ so later commands can reuse positioning and voice.

Best practices

• Customer-language changelog from a real diff
• Email + social + in-app blurbs from one narrative
• Claims audit against CURSOR.md
• Handoff into /linkedin-post or /email-sequence
• One role per chat unless a command is explicitly orchestrating a sequence.

Common mistakes

• Using product-marketer as a synonym for 'the Cursor agent'. It is a brief, not the product.
• Skipping the required skills and hoping the role name is enough.
• Publishing the first draft of launch copy without a human edit.
• Invoking this agent and three unrelated ones in the same prompt.