← ClaudeAtlas

marketing-campaign-brieflisted

Writes a campaign brief that survives review — required fields, a single measurable primary objective, the audience-evidence check, and the named approval gate before any asset is produced. Use when someone asks to brief a campaign, launch, promotion, always-on channel push, or event marketing programme; trigger on 'write a campaign brief', 'brief the agency', 'we need a campaign for X', 'kick off the launch marketing'. Not for reviewing claims already written into copy (use marketing-claim-substantiation), not for organic search briefs (use marketing-seo-content-brief), and not for the product launch decision itself (use product-roadmap-communication).
alihusains/enterprise-skills · ★ 0 · AI & Automation · score 73
Install: claude install-skill alihusains/enterprise-skills
# Campaign Brief Authoring ## Purpose Campaign briefs fail in two predictable ways: they carry three objectives so nothing can be measured, and they reach creative production before anyone with budget or compliance authority has signed. This skill fixes the field list, forces one primary metric, and puts the approval gate before asset production rather than after. ## Prerequisites - **Inputs:** the requesting stakeholder and their authority to spend; a budget figure or a stated range; the offer or product being promoted; the target start and end dates; whoever owns the approval gate in step 6. - **Access:** prior campaign results for the same audience or channel, if any exist, from your analytics or campaign reporting system. - **Runtime:** none. This produces a document, not a build. If the budget owner or the primary metric is unknown, name the gap and stop. A brief written around a guessed objective is re-briefed, not amended. ## Data classification **Internal** by default. A brief containing unreleased pricing, unannounced product, or customer segment lists is **Confidential** — mark it and restrict distribution to named recipients. If a stakeholder pastes customer records, individual contact details, or account identifiers to illustrate a segment, flag it and do not carry them into the brief; describe the segment by its defining attributes instead. ## Required fields Every field below is mandatory. An empty field is a blocker, not a to-do. | Field | What