PMM Campaign Brief
You create campaign briefs that are tight enough for execution and complete enough for stakeholder approval.
Use when
- The user asks for a campaign brief.
- A launch requires a multi-channel campaign.
- A team needs a creative, lifecycle, paid, social, or field marketing brief.
- The user wants a Word-ready or export-ready campaign document.
Workflow
Setup
- Campaign name, campaign type, full or light brief, launch tier.
Strategy
- Background, why now, business objective, audience, competitive context.
- Convert the objective to SMART format.
Messaging
- Key insight, positioning, key messages, single-minded proposition.
- Reject SMPs that contain multiple ideas.
Execution
- Channels, deliverables, timeline, budget, owners.
Governance
- KPIs, RACI, approvals, risks.
Review and export
- Run the quality checklist.
- Hand off to pmm-artifact-factory for
.md, .docx, .pptx, .csv, .json, or .html outputs.
Brief structure
Use skills/product-marketing-os/assets/campaign-brief-template.md.
Full vs light brief
Full brief is for major launches, cross-functional campaigns, competitive responses, or paid campaigns.
Light brief is for smaller feature updates, lifecycle campaigns, or narrow customer communications. It must still include background, objective, audience, key messages, deliverables, owner, and measurement.
Quality checks
Do not mark the brief done if it has:
- More than one primary objective.
- A vague audience.
- No insight.
- An SMP with more than one idea.
- No success metrics.
- No competitive context when competition matters.
- No why now.
- No RACI or approval owner.
Output
Produce a clear markdown brief first. Then, if requested, create the artifact bundle with pmm-artifact-factory.
Hand off to
PMM OS is a chain, not a menu — don't dead-end at advice. Pass the work on:
Depth
Any long-form or prose section here follows the PMM OS depth standard — see ../product-marketing-os/references/output-depth-standard.md (and pmm-content-writer for word budgets): hit the word/structure budget for the format, develop each point with claim → why → concrete evidence → implication, and run the depth rubric before returning. Deliver finished copy, never an outline-as-deliverable or a 250-word stub.
Frameworks & deep references
Read and apply the deep frameworks below before you produce output — they carry the methodology, templates, and worked examples behind this skill (from the PMM OS framework library). Read the ones relevant to the request and apply them; don't paste them verbatim.
1---2name: pmm-campaign-brief3description: When the user needs a campaign brief, marketing campaign plan, launch campaign, creative brief, channel plan, content deliverables, SMART objective, RACI, KPIs, or a .docx-ready stakeholder brief. Produces a 14-section campaign brief, catches common campaign-brief mistakes, and can hand off to pmm-artifact-factory for exportable files.4---56# PMM Campaign Brief78You create campaign briefs that are tight enough for execution and complete enough for stakeholder approval.910## Use when1112- The user asks for a campaign brief.13- A launch requires a multi-channel campaign.14- A team needs a creative, lifecycle, paid, social, or field marketing brief.15- The user wants a Word-ready or export-ready campaign document.1617## Workflow18191. Setup20 - Campaign name, campaign type, full or light brief, launch tier.21222. Strategy23 - Background, why now, business objective, audience, competitive context.24 - Convert the objective to SMART format.25263. Messaging27 - Key insight, positioning, key messages, single-minded proposition.28 - Reject SMPs that contain multiple ideas.29304. Execution31 - Channels, deliverables, timeline, budget, owners.32335. Governance34 - KPIs, RACI, approvals, risks.35366. Review and export37 - Run the quality checklist.38 - Hand off to pmm-artifact-factory for `.md`, `.docx`, `.pptx`, `.csv`, `.json`, or `.html` outputs.3940## Brief structure4142Use `skills/product-marketing-os/assets/campaign-brief-template.md`.4344## Full vs light brief4546Full brief is for major launches, cross-functional campaigns, competitive responses, or paid campaigns.4748Light brief is for smaller feature updates, lifecycle campaigns, or narrow customer communications. It must still include background, objective, audience, key messages, deliverables, owner, and measurement.4950## Quality checks5152Do not mark the brief done if it has:5354- More than one primary objective.55- A vague audience.56- No insight.57- An SMP with more than one idea.58- No success metrics.59- No competitive context when competition matters.60- No why now.61- No RACI or approval owner.6263## Output6465Produce a clear markdown brief first. Then, if requested, create the artifact bundle with pmm-artifact-factory.6667## Hand off to6869PMM OS is a chain, not a menu — don't dead-end at advice. Pass the work on:7071- [`pmm-artifact-factory`](../pmm-artifact-factory/SKILL.md) — produce the campaign assets72- [`pmm-feature-announcement`](../pmm-feature-announcement/SKILL.md) — write the announcement73- [`post-launch-learning-loop`](../post-launch-learning-loop/SKILL.md) — read the results74- [`pmm-coach`](../pmm-coach/SKILL.md) — review before anything customer- or exec-facing.7576## Depth7778Any long-form or prose section here follows the PMM OS depth standard — see `../product-marketing-os/references/output-depth-standard.md` (and `pmm-content-writer` for word budgets): hit the word/structure budget for the format, develop each point with claim → why → concrete evidence → implication, and run the depth rubric before returning. Deliver finished copy, never an outline-as-deliverable or a 250-word stub.7980## Frameworks & deep references8182Read and apply the deep frameworks below before you produce output — they carry the methodology, templates, and worked examples behind this skill (from the PMM OS framework library). Read the ones relevant to the request and *apply* them; don't paste them verbatim.8384- [`product-launch/05-multi-channel-tactics.md`](../product-marketing-os/references/library/product-launch/references/core/05-multi-channel-tactics.md) — channel plan for the campaign85- [`rollout-and-launch/01-message-testing.md`](../product-marketing-os/references/library/rollout-and-launch/references/core/01-message-testing.md) — test the SMP before spending86