← ClaudeAtlas

product-messaging-playbooklisted

Assembles a single Sales/CS-ready playbook for a new product or feature: problem, story, one named competitive comparison, discovery questions and objection handling. Use when you say "build a messaging playbook," "give sales something they can use for this feature," "handoff doc for sales and CS," or "solution guide for this launch."
stefanoskarakasis/Product-Marketing-Skills · ★ 13 · AI & Automation · score 80
Install: claude install-skill stefanoskarakasis/Product-Marketing-Skills
# Product Messaging Playbook The document a PMM hands to Sales and CS so they can talk about a new product or feature the same day it ships — not a strategy deck, not raw brain output, but one assembled artifact: what the problem is, why the product solves it, how it compares to the one alternative buyers actually ask about, and exactly what to say (and not say) on a call. It doesn't derive positioning, pillars, or proof — those already have owners (`positioning-messaging`, `message-house`, `proof-points`). This skill reads their output and the brain, asks only for what's genuinely new (the problem framing and forward-looking targets for *this* feature), and assembles the rest into one document a rep can open cold. --- ## Trigger - **When:** A PMM needs a single Sales/CS-facing document for a specific product or feature — new or existing — that bundles the problem it solves, the pitch, one named competitive comparison, and a discovery/objection script, in a format non-PMMs can use without translation. - **Not for:** Deriving the underlying positioning statement or messaging hierarchy → `positioning-messaging`, run first. Formatting general company-level positioning into a Roof + Pillars table with no feature-specific problem framing or sales script → `message-house` already does that; use this skill instead when the ask specifically includes discovery questions, objection handling, or a named-competitor comparison. Sourcing or auditing the proof points