Skip to content
Marketing
Skill

/launch-plan

Build a three-phase launch playbook — pre-launch (T-30), an hour-by-hour launch-day runbook, and post-launch optimization (T+30) — with per-task owners and deadlines, channel activation plans, a risk register, and KPIs per phase. Triggers on

From plugin
digital-marketing-pro
819163 skills24 agents18 commands
Install
$ npx -y skills add indranilbanerjee/digital-marketing-pro --skill launch-plan --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/launch-plan

Context preview

The summary Claude sees to decide when to auto-load this skill.

Build a three-phase launch playbook — pre-launch (T-30), an hour-by-hour launch-day runbook, and post-launch optimization (T+30) — with per-task owners and deadlines, channel activation plans, a risk register, and KPIs per phase. Triggers on

SKILL.md

launch-plan.SKILL.md
name: launch-plan
description: "Build a three-phase launch playbook — pre-launch (T-30), an hour-by-hour launch-day runbook, and post-launch optimization (T+30) — with per-task owners and deadlines, channel activation plans, a risk register, and KPIs per phase. Triggers on \"/digital-marketing-pro:launch-plan\", \"plan our product launch\", \"launch playbook for the new feature\", \"what should launch week look like\", \"coordinate the rebrand rollout\". Planning only: it performs no external action itself; any playbook step handed to an execution skill such as /digital-marketing-pro:launch-campaign or /digital-marketing-pro:send-email-campaign must pass that skill's own typed-yes approval gate first. Reads the brand profile, guidelines, templates, and agency SOPs."
argument-hint: "[product-name]"
disable-model-invocation: false

/digital-marketing-pro:launch-plan

Purpose

Build a comprehensive launch playbook that coordinates all marketing activities across three phases — pre-launch, launch, and post-launch — to maximize impact and sustain momentum.

Execution gate (MANDATORY — cannot be skipped)

This skill produces a launch **playbook** — it performs no external action itself, so it runs freely. The gate governs the *handoff*: before ANY step of this playbook is executed by a downstream execution skill (`/digital-marketing-pro:launch-campaign`, `/digital-marketing-pro:launch-ad-campaign`, `/digital-marketing-pro:send-email-campaign`, etc.), that skill presents its own Execution Summary and the user must type `yes`. Never proceed on ambiguous input, never auto-execute a playbook step, and never auto-retry a failed one.

Input Required

The user must provide (or will be prompted for):

  • **What is launching**: Product, feature, service, rebrand, or event
  • **Launch date**: Target date or date range
  • **Launch goals**: Signups, revenue, coverage, awareness targets
  • **Target audience**: Primary and secondary audiences for the launch
  • **Available channels**: Which channels are active and resourced
  • **Budget**: Dedicated launch budget (if any)
  • **Assets available**: What already exists (product pages, demos, press materials, creative)
  • **Team**: Who is involved and their roles

Process

1. **Load brand context**: Read `~/.claude-marketing/brands/_active-brand.json` for the active slug, then load `~/.claude-marketing/brands/{slug}/profile.json`. Apply brand voice, compliance rules for target markets (`skills/context-engine/compliance-rules.md`), and industry context. **Also check for guidelines** at `~/.claude-marketing/brands/{slug}/guidelines/_manifest.json` — if present, load restrictions and relevant category files. Check for custom templates at `~/.claude-marketing/brands/{slug}/templates/`. Check for agency SOPs at `~/.claude-marketing/sops/`. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults. 2. Define launch tier (Tier 1 major, Tier 2 moderate, Tier 3 minor) to calibrate effort 3. **Pre-launch phase** (T-30 to T-1): Teaser content, audience building, press seeding, influencer outreach, email list warming, landing page, waitlist 4. **Launch phase** (T-0 to T+3): Coordinated announcement across all channels, press release, email blast, social blitz, paid media activation, community engagement 5. **Post-launch phase** (T+4 to T+30): Performance monitoring, user feedback collection, content follow-up, retargeting, optimization, case studies 6. Build detailed timeline with owners, deliverables, and deadlines per task 7. Define success metrics per phase and overall launch KPIs 8. Identify risks and build contingency plans

Output

A structured launch playbook containing:

  • Launch overview with tier classification and success criteria
  • Pre-launch checklist with timeline, deliverables, and owners
  • Launch day runbook with hour-by-hour coordination plan
  • Post-launch optimization plan with feedback loops
  • Channel-by-channel activation plan with specific tactics
  • Content and asset requirements list
  • Risk register with contingency actions
  • KPI dashboard with targets per phase

Agents Used

  • **marketing-strategist** — Launch architecture, phasing, goal setting, channel coordination
  • **content-creator** — Launch messaging, content assets, announcement copy
  • **pr-outreach** — Media strategy, press materials, influencer seeding
Read more
Ships withdigital-marketing-pro

Your agency just signed a 50-brand client. The previous agency left no playbook. Three brands are bleeding budget, two have stale positioning, one is launching in a regulated jurisdiction next month. Where do you start?

Get the whole plugin

Other skills on digital-marketing-pro.