campaign-and-launch-planning v1.0.0A

Immutable. This exact content is served forever at /api/v1/blob/bdc9152fea9427dd.

---
name: campaign-and-launch-planning
description: >-
  The campaign/launch orchestration skill. Use when someone wants to plan a launch, product drop, campaign,
  big announcement, waitlist/pre-launch push, or coordinated multi-platform moment. Plans a time-boxed
  campaign as ONE story across three phases (tease -> launch -> sustain) toward a single goal, and schedules
  the coordinated social posts via WoopSocial. Uses the STORY framework. Reads brand-profile + goals-and-kpis
  first. Pre-launch builds anticipation (waitlist/referral/hub/BTS); launch day concentrates a coordinated
  cross-platform push behind one CTA with credible urgency; post-launch reinforces with proof and measures.
  WoopSocial schedules + publishes the social posts on the timeline; the waitlist/landing-page/hub, email
  sequence (an ESP), checkout/sale, paid ads, press/creator outreach, and livestream are external/native, and
  conversion/ROI come from native analytics + the store (never fabricated). Urgency must be credible (no fake
  countdowns/scarcity). Distinct from content-calendar (the ongoing always-on cadence) and goals-and-kpis
  (the targets a campaign serves).
version: 1.0.0
---

# campaign-and-launch-planning

A **strategy/orchestration skill** — plan the time-boxed campaign (goal, phases, week-by-week map, the brief,
the posts) and let **WoopSocial schedule + publish the coordinated social posts** on the timeline. The agent
**plans + writes + schedules the social side**; the **waitlist/hub, email, ads, checkout, press, and
livestream are external/native.**

## The POV: the spotlight event, told as one story
Your content calendar **keeps the lights on**; a **campaign is the spotlight event** — time-boxed, toward
**one goal**, across **three phases (tease → launch → sustain)** told as **ONE story**, not three
disconnected campaigns. Three forces win it: **anticipation** (a waitlist/emotional investment turns launch
day into a confirmation, ~30% higher day-one conversions), **velocity** (a concentrated coordinated push
beats a slow drip — algorithms reward it), and **proof** (post-launch is where you compound trust or confirm
it was noise). WoopSocial's role is the thing a launch needs most: **coordinated multi-platform publishing**
on the timeline.

## Read these first
1. **brand-profile** — audience/voice.
2. **goals-and-kpis** — the one primary goal + success metric.

## The framework: STORY
(Depth: `references/the-story-framework.md`.)
- **S — Set one goal + the brief:** one goal/metric; launch type (soft/hard/phased); 1–3 platforms; the
  one-page launch brief; discipline over speed.
- **T — Tease to build demand:** waitlist (specific promise, ~30% day-one) + referral; one campaign hub;
  BTS/teasers/proof drops; beta group; personalized press/creator outreach (not a mass release).
- **O — One coordinated launch:** concentrated cross-platform push (velocity rewarded); one CTA + remove
  friction; **credible urgency** (real scarcity/bonus/deadline — never fake/resetting timers); drop/
  countdown/live.
- **R — Reinforce with proof:** testimonials/UGC/demos/objection-answers; sustain (don't go quiet); close
  the signed-up → used gap.
- **Y — Yield: measure + debrief:** numbers vs targets per channel; debrief; feed the next campaign; never
  fabricate.

## The reality (verify-quarterly)
Campaign-as-spotlight + the three-phase funnel as one story; pre-launch (anticipation/emotional investment,
waitlist +30% day-one + referral, one hub, BTS/proof drops, beta, personalized press/creator outreach);
launch (velocity rewarded, one CTA, credible urgency — no fake timers, drop/countdown/live); post-launch
(proof, sustain, signed-up→used gap); launch types (soft/hard/phased); orchestration (1–3 platforms,
repurpose-not-copy, hero posts/phase, parallel email sequence); planning discipline (one-page brief,
readiness, week-by-week map): `references/launch-2026-reality.md`. The brief + week-by-week map + phase×
platform grid + urgency mechanics + worked examples: `references/launch-plan-and-recipes.md`.

## Honest scope (never violate)
- **The agent** plans the campaign + writes the **brief**, the **week-by-week map**, and the **posts**, and
  designs the phases/urgency/hero moments.
- **WoopSocial schedules + publishes the coordinated social posts** on the timeline (`SCHEDULE_FOR_LATER` +
  per-platform fields; validate via `platform-specs-and-validation`). It does **not** host the **waitlist/
  landing-page/hub**, send the **email sequence** (an ESP does), process **checkout/the sale**, run **paid
  ads**, do **press/creator outreach** (human/DM), run the **livestream** (native), or measure **conversions/
  ROI** (native analytics + the store).
- **Credible urgency only** (no fake/resetting countdowns or invented scarcity/signup counts); **never
  fabricate** anticipation or results; **coordinate, don't spam.** (Scope, distinctions + connections:
  `references/scope-and-connections.md`.)

## Distinct from its siblings (route correctly)
**campaign-and-launch-planning (this)** = the time-boxed spotlight campaign (phases toward one goal) ·
**content-calendar** = the ongoing always-on cadence · **goals-and-kpis** = the targets a campaign serves ·
**collabs-and-cross-promotion** / **lead-magnets-and-funnels** / **email-and-newsletter** /
**link-in-bio-and-traffic** / **livestream-and-realtime** / **ugc-and-influencer** = the pieces a launch
orchestrates.

## Where this connects
Reads first: **brand-profile**, **goals-and-kpis**, **competitor-analysis**. Orchestrates:
**lead-magnets-and-funnels**/**link-in-bio-and-traffic** (the hub/waitlist), **email-and-newsletter** (the
parallel sequence), **collabs-and-cross-promotion**/**ugc-and-influencer** (press/creator/partner moments),
**livestream-and-realtime** (the live), the **format skills** + **thumbnail-design** (assets),
**cross-platform-repurposing** (one asset → many cuts). Publishes via: **scheduling-and-queue → WoopSocial**
(the coordinated timeline) + **platform-specs-and-validation**; **content-calendar** reserves the slots.
Measures with: **analytics-and-reporting** + the store. Hub, email, ads, checkout, press, live + conversion
measurement stay external/native.

## Definition of done
One primary goal + metric set and a one-page launch brief written; a launch type chosen and 1–3 platforms
picked; the three-phase arc designed as one story with a week-by-week map and 1–2 hero moments per phase; a
waitlist/hub + referral and BTS/proof/press in pre-launch; a coordinated launch-day push behind one CTA with
credible urgency; a post-launch proof + sustain plan that closes the signed-up→used gap; per-channel numbers
read against targets; the social posts scheduled/published via WoopSocial while the hub, email, ads, checkout,
press, live, and conversion measurement stay external/native; nothing fabricated and no fake urgency;
correctly distinguished from content-calendar and goals-and-kpis.