Purpose
Turn a campaign brief into an executable, owner-assigned project plan — breaking the work into functional workstreams, mapping the dependencies between them, sequencing milestones backward from the launch date, and surfacing the risks most likely to slip the timeline before they do. Eliminates the "who's doing what by when" scramble that stalls large multi-team campaigns.
When to Use
Invoke this skill when the user asks to:
- Plan a product launch or multi-team marketing campaign
- Break a campaign brief into workstreams and assign owners
- Map dependencies between design, content, web, sales enablement, and demand gen
- Build a milestone timeline working backward from a launch date
- Identify what could slip or block a campaign before kickoff
- Turn a vague campaign goal into a structured, trackable project plan
Inputs Required
Before starting, collect:
- Campaign objective: What the campaign is trying to achieve (launch, awareness, pipeline, adoption)
- Launch date: Target go-live date (drives the backward-planned timeline)
- Scope of deliverables: Known assets, channels, and outputs expected
- Teams involved: Which functions/teams are available (design, content, web, PMM, demand gen, sales, PR, etc.)
- Named owners: Specific people or roles who lead each function, if known
- Known constraints: Fixed dates, budget caps, approval gates, holidays, freeze windows
- Success metrics: How the campaign will be measured
If named owners are missing, assign by function role and flag them for confirmation. If launch date is missing, ask for it before proceeding — the backward-planned timeline depends on it.
Instructions
Step 1: Decompose the Brief into 6 Workstreams
Break the campaign into functional tracks. For each active workstream, define scope, deliverables, and the owning function.
Workstream 1 — Messaging & Content Positioning, core narrative, blog posts, whitepapers, landing page copy, email sequences, social copy.
- Owner: Product Marketing / Content
- Gating deliverable: approved core messaging (blocks nearly everything downstream)
Workstream 2 — Creative & Design Visual identity, ad creative, landing page design, social graphics, video, decks.
- Owner: Design / Brand
- Depends on: approved messaging and copy
Workstream 3 — Web & Technical Landing pages, forms, tracking/pixels, CMS updates, gated asset delivery, QA.
- Owner: Web / Marketing Ops
- Depends on: final copy + design; gates go-live
Workstream 4 — Demand Gen & Channels Paid media, email campaigns, SEO, syndication, organic social scheduling, audience/segmentation setup.
- Owner: Demand Gen / Growth
- Depends on: creative assets + live web/tracking
Workstream 5 — Sales & Customer Enablement Sales deck, battlecards, FAQ, internal training, CS talking points, launch email to reps.
- Owner: Product Marketing / Sales Enablement
- Depends on: approved messaging; must be ready before external launch
Workstream 6 — PR, Analyst & Comms Press release, analyst briefings, exec/customer quotes, influencer outreach, internal announcement.
- Owner: Comms / PR
- Depends on: approved messaging; often runs to fixed external dates
Omit or merge any workstream not in scope, and note the omission.
Step 2: Map Dependencies
Build the dependency chain. For each deliverable, note what must finish before it can start.
- Critical path: Trace the longest chain from kickoff to launch (typically: messaging → copy → design → web build → QA → go-live)
- Blocking dependencies: Mark any deliverable that gates 2+ downstream items as a "keystone" — these get the most schedule buffer
- Parallel tracks: Identify work that can run simultaneously to compress the timeline
- Cross-team handoffs: Flag every point where one team's output feeds another's input — these are the highest slip-risk moments
Step 3: Build the Milestone Timeline (Backward from Launch)
Work backward from the launch date in phases:
- Launch day (T): Go-live, comms sent, campaign live
- T−3 days: Final QA, freeze, buffer for fixes
- T−1 week: Web/tracking live in staging, enablement delivered to sales, PR embargo set
- T−2 to 3 weeks: Creative finalized, copy approved, channels configured
- T−4 to 6 weeks: Messaging locked, creative in production, web build begins
- T−6+ weeks: Kickoff, brief alignment, messaging draft
Assign each milestone a date, an owner, and the deliverable that marks it complete. Include approval/review gates as explicit milestones — not implied.
Step 4: Assign Owners and Accountability
For each workstream and key milestone, apply a clear accountability model:
- Owner (R): The single person accountable for the deliverable
- Contributors (C): Teams that produce inputs
- Approver (A): Who signs off before it moves downstream
- Every deliverable must have exactly one Owner and one Approver — flag any deliverable missing either.
Step 5: Flag and Rank Risks
Identify the risks most likely to slip the campaign, ranked by likelihood × impact:
- Schedule risks: Compressed timelines, insufficient buffer on the critical path, dependency stacking
- Capacity risks: A team owning multiple keystone deliverables simultaneously
- Handoff risks: Cross-team dependencies with no slack
- Approval risks: Review gates without confirmed approver availability
- External risks: Fixed dates (events, embargoes), freeze windows, holidays
For each risk: state the risk, its likelihood (High/Med/Low), its impact, and a specific mitigation or contingency.
Output Format
- Structure: Workstream table → dependency map → backward-planned milestone timeline → RACI-style owner assignments → ranked risk register
- Length: 1,000–1,400 words
- Format: Structured document with tables for workstreams, timeline, and risks; bulleted dependency and owner sections
- Sections: Campaign Summary → 6 Workstreams → Dependency Map (with critical path called out) → Milestone Timeline → Owner & Approval Matrix → Ranked Risk Register
- Tone: Program manager — organized, decisive, focused on what happens next and who owns it
Quality Checklist
Before delivering output, verify:
- [ ] Every workstream in scope has a defined owner and at least one deliverable
- [ ] The critical path is explicitly identified and traced from kickoff to launch
- [ ] Every milestone in the timeline has a date, an owner, and a completion marker
- [ ] Every deliverable has exactly one Owner and one Approver — none left unassigned
- [ ] Risks are ranked by likelihood × impact and each has a specific mitigation (not "monitor closely")
- [ ] The timeline works backward from the actual launch date provided — dates are concrete, not "week 1/week 2"
Notes
- The single most common failure mode is one team owning multiple keystone deliverables at the same time — always check capacity against the dependency map, not just the calendar.
- Approval gates are the most under-planned milestones; treat every sign-off as its own dated milestone with a named approver.
- If the launch date leaves less than the critical path requires, say so directly and propose either a scope cut or a revised date — don't produce a plan that can't hold.
- Recommended workflow: generate the plan, confirm owners and approvers with each team lead, then lock the critical-path milestones before filling in parallel tracks.
How to use this skill
This file is a Claude Code skill in Anthropic's standard format — markdown with YAML frontmatter at the top.
Installing in Claude Code:
~/.claude/skills/<folder-name>/SKILL.md— auto-loads in every session anywhere on your machine (recommended for skills you'll use across multiple projects)<your-project>/.claude/skills/<folder-name>/SKILL.md— auto-loads only when working in that project (recommended for project-specific skills)
Restart Claude Code or open a new session to register.
Using in Claude.ai, ChatGPT, Gemini, or other AI tools:
- Drag this file into a new chat, or copy and paste its contents
- Send your task or request as your next message — the AI will apply the skill where it fits
For Claude Code skill details: https://docs.anthropic.com/en/docs/claude-code/skills