agentleFS
teachskillofskills-aiteachskillofskills-ai/DigitalMarketingPro-techshu/skills/launch-plan/SKILL.md

launch-plan

Skill0 starsChanged 9 months agoMITView on GitHub

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.

13 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use offer-builder.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • duncan-buildroomSkill

    offer-builder

    Build a Hormozi-style "Grand Slam Offer" so good people feel stupid saying no — engineered around the Value Equation (bigger dream outcome, higher belief it'll work, less time, less effort). Use this when the user says "build my offer", "make my offer irresistible", "help me package what I sell", "I don't know how to price/pitch this", "grand slam offer", "I built a product but nobody's buying", or when they have a thing to sell but no compelling way to present it. Push to run this before they try to sell anything.

    Also in 3 projects that use this

The file

Files
SKILL.md

/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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.