Skill detail
campaign-and-launch-planning
Plans and orchestrates a product launch or social campaign end to end across three phases, scheduling coordinated social posts via WoopSocial.
Inspect before use
Read the source instructions and check the requirements before you install this skill.
SKILL.md
The saved excerpt is a snapshot from when this skill was listed. The external source remains the complete and most current version.
--- name: campaign-and-launch-planning description: >- Plan and orchestrate a product launch or social media campaign end to end — the multi-week arc, channel by channel. 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. WoopSocial schedules + publishes the social posts on the timeline; the waitlist/hub, email sequence, checkout, 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 — launches with real pre-launch marketing see ~30% higher day-one sales; Waitlister, vendor-directional), **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; pre-launch ≈ +30% day-one, vendor) + 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 + referral (pre-launch ≈ +30% day-one, vendor), 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-Read the full source on GitHub (opens external page)