---
name: product-launch-messaging-pack
description: Creates a product or feature launch messaging pack with audience-specific value propositions, objections, FAQs, channel copy, and enablement points grounded in approved product facts. Use for launch planning, release communications, go-to-market messaging, sales enablement, or feature announcement preparation.
license: Apache-2.0
metadata:
  adlass.categories: "marketing-content/product-marketing, marketing-content/content-production"
  adlass.industries: ""
  adlass.tags: "product-launch, go-to-market, positioning, faq, enablement, channel-copy"
  adlass.adaptation: "reference-doc"
  adlass.source: "original"
  adlass.version: "1"
---

# Product launch messaging pack

## Purpose

Prepare consistent launch language for priority audiences and channels from a product change, positioning, and approved proof.

## Scope

The skill covers value propositions, differentiation, objections, FAQs, enablement, copy matrix, and claim controls.

**Excluded:** product strategy decisions, pricing approval, creative production, and publishing.

## Data basis

- Product or feature description and launch context supplied as inputs.
- Positioning, audience profiles, pricing and proof in scope.
- Brand guide and prior launch materials in scope.

## Result

A launch messaging document, internal/external FAQ, and channel copy matrix.

## Quality criteria

- Every benefit is traceable to a product capability or approved evidence.
- Audiences receive distinct reasons to care and next actions.
- Open product, pricing or legal questions are visible.
- Copy is consistent across outputs.

## Instructions

Describe outcomes before features, distinguish the new capability from existing alternatives, and never imply availability or performance not supported by the source material. Use plain language for external copy and operational detail for internal enablement. Maintain a do-not-say list for unresolved or restricted claims.

## Adapt before use

- Add product facts, roadmap status, pricing and approved proof.
- Add positioning, audience and brand documents.
- Define launch stages, channels and approval owners.
- Add restricted claims and required disclosures.
- Keep source facts, analysis, recommendations, and unresolved questions visibly separate.
- Preserve stable document, section, page, sentence, URL, or row identifiers in every finding.
- Record assumptions about audience, channel, period, approval status, and data coverage.
- Treat missing guidance as an adaptation gap rather than inventing a company rule.
- Prefer a precise, bounded recommendation over a broad generic rewrite.
- Use supplied terminology consistently across the document, sheet, and any derivative copy.
- Do not infer performance, customer behavior, product capability, or market response from wording alone.
- Make every unresolved issue actionable by naming the missing decision, evidence, owner, or source.
- Keep factual claims traceable even when the final copy is concise.
- Recheck that counts, names, dates, and identifiers match across all outputs.
- Mark hypotheses as hypotheses and preserve competing explanations when evidence is mixed.
- Use the stated acceptance criteria as the final completeness check.