/launch-campaign

name: launch-campaign
description: "Orchestrate the full multi-channel launch of an approved campaign plan — pre-launch BLOCKER gates (approved plan, assets present, connectors probed, conversion tracking verified, C2PA-signed AI assets for EU markets), then dependency-ordered activation across CRM, landing page, email, paid ads, organic social, influencer, and PR, with a checkpoint after every step and a dual-copy launch record. Nothing executes until the dry-run preview is shown and the user types an explicit yes. Triggers on \"/digital-marketing-pro:launch-campaign\", \"go live with the campaign\", \"kick off the launch\", \"activate every channel for this campaign\", \"flip the switch on the launch\". Consumes the plan from /digital-marketing-pro:campaign-plan, delegates paid ads to /digital-marketing-pro:launch-ad-campaign, and resumes interrupted launches via /digital-marketing-pro:resume."
user-invocable: true
triggers:
  - launch this campaign
  - go live with the campaign
  - launch campaign
  - kick off the campaign
  - flip the switch on the launch
  - activate the multi-channel campaign
allowed-tools: Read Bash Glob Grep

/digital-marketing-pro:launch-campaign — Multi-Channel Campaign Launch Orchestrator

This skill takes an **approved** campaign plan (from `/digital-marketing-pro:campaign-plan`) and walks it through every step required to go live: pre-launch gates, channel-by-channel activation, CRM record creation, kickoff comms to the team, and day-1 monitoring setup. It complements — and is broader than — `/digital-marketing-pro:launch-ad-campaign`, which handles only paid-ads activation on Google / Meta / LinkedIn / TikTok.

Use this skill **once** per campaign, after the campaign plan is approved and all creative + landing pages + email sequences are signed off. Not for paid-ads alone — for the full multi-channel launch (paid + organic + email + content + CRM + PR).

Why this skill exists

A campaign plan is a document. A campaign launch is twenty separate platform actions in the correct order with the correct dependencies. Without an orchestrator, agencies miss steps — landing page goes live without the analytics tag wired, email automation gets enabled before the source list is GDPR-clean, paid ads get activated before the LP is indexed, the team finds out the campaign launched by seeing the first conversion notification in Slack.

This skill is the difference between "we launched" and "we launched cleanly." It checks every prerequisite before it touches a live system, executes the activation steps in dependency order, and records the launch as a CRM Campaign object so attribution can downstream-correctly from day one.

What this skill does NOT do

• It does NOT create the campaign plan — that's `/digital-marketing-pro:campaign-plan`.
• It does NOT generate the creative — that's `/digital-marketing-pro:ad-creative`, `/digital-marketing-pro:content-engine`, `/digital-marketing-pro:email-sequence`, etc.
• It does NOT bid or optimise day 2+ — that's `/digital-marketing-pro:performance-report`, `/digital-marketing-pro:budget-optimizer`, etc.

It is the **single-shot launch event**, not the planning or the optimisation.

Process

Step 0 — Prerequisites (BLOCKER gates)

This skill REFUSES to proceed unless ALL of these pass. Print the failing items, do not start the launch.

1. `/digital-marketing-pro:validate-profile --brand {brand}` returns `passed` or `passed_with_warnings`. 2. A campaign plan exists at `~/.claude-marketing/brands/{slug}/campaigns/{campaign_id}/plan.json` (or the user provides `--plan-path`). 3. The plan's `status` field is `approved` (not `draft` / `in_review` / `rejected`). 4. Every asset referenced in the plan exists at the path the plan claims it does (creative files, landing-page URLs respond 200, email templates exist in the email platform). 5. Every connector required by the channels in scope is reachable — re-run a fast probe: `python "${CLAUDE_PLUGIN_ROOT}/scripts/connector-status.py" --brand {slug} --action status --probe-only --connectors {comma-separated channel connectors}`. 6. Conversion tracking is verified for every channel in scope — GA4 events configured AND test-fired in the last 7 days: `python "${CLAUDE_PLUGIN_ROOT}/scripts/performance-monitor.py" --brand {slug} --action diagnostic --channel ga4_health`. 7. If any AI-generated visual / video / audio is in the asset list AND the campaign targets EU markets, every such asset has been signed via C2PA (`/digital-marketing-pro:c2pa-metadata` workflow — `embed-c2pa.py --ai-disclosure` under the hood). Article 50 compliance is non-negotiable for EU launches as of 2 Aug 2026.

If any of these fail, print the punch list with the literal next command for each item, and exit.

Step 1 — Load the campaign plan

Read `plan.json`. Extract: `campaign_id`, `campaign_name`, `objective`, `start_date`, `end_date`, `channels` (with per-channel `budget`, `audience`, `creative_ids`, `landing_url`, `kpi_targets`), `team_assignments`, `kickoff_comms`, `attribution_model`.

Step 2 — Dry-run preview

Before touching any live system, print a dry-run preview of every action that's about to happen. The user must confirm `yes` to proceed. The dry run shows:

🚀 Campaign launch preview — {campaign_name}
   Campaign ID: {campaign_id}
   Brand:       {brand}
   Window:      {start_date} → {end_date}
   Objective:   {objective}
   Attribution: {model}

   The following 14 actions will execute in order:

    1. CRM — Create Campaign object {campaign_name} in {HubSpot|Salesforce|...}
    2. Landing page — Verify {url} returns 200, schema markup present, GA4 tag firing
    3. Email — Enable automation {automation_id} in {Klaviyo|HubSpot|...} (sender domain authenticated)
    4. Paid search — Activate {N} Google Ads campaigns ({budget} daily total)
    5. Paid social — Activate {N} Meta + {M} LinkedIn campaigns ({budget} daily total)
    6. Retail media — Activate {N} Amazon Sponsored Pr