mcpField
C
campaign-planning

campaign-planning

github.com/gtmagentsMarketing & growth43072 installsUpdated 30w ago
Repository

About campaign-planning

A marketing skill for planning multi-channel campaigns, including objectives, audiences, messaging, channels, timelines, and risks. It provides a campaign brief, RACI matrix, and Gantt timeline template for team coordination.

Key features

  1. 01Set objectives and key performance indicators
  2. 02Map audiences, personas, and offers
  3. 03Plan messaging and calls to action
  4. 04Select channels, budget, and cadence
  5. 05Build timelines with dependencies and approvals
  6. 06Assess risks and mitigations

Use cases

  1. 01Plan a multi-channel go-to-market effort
  2. 02Align stakeholders on goals and offers
  3. 03Coordinate quarterly plans or product launches

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/gtmagents/gtm-agents --skill campaign-planning

After installing, type/campaign-planningin Claude Code to confirm it loaded.

Bundled filestemplates/campaign_brief.md

Details

From the project README

Campaign Planning Skill

When to Use

  • Before launching multi-channel GTM efforts.
  • When stakeholder alignment on goals, personas, and offers is needed.
  • During quarterly planning or major product launches.

Framework

  1. Set Objectives – tie to revenue/pipeline targets, define primary KPIs.
  2. Audience & Offers – map personas, stages, ICP tiers, and value propositions.
  3. Messaging Architecture – craft key narrative, proof points, CTA hierarchy.
  4. Channel Mix – select channels, budget split, cadence, sequencing logic.
  5. Workback Plan – create timeline with dependencies, approvals, and resource allocation.
  6. Risk Assessment – identify blockers (legal, creative bandwidth, data access) and mitigations.

Templates

  • Campaign Brief: See templates/campaign_brief.md for goal, audience, and KPIs.
  • RACI matrix for decision-making.
  • Timeline Gantt template with creative/ops milestones.

Tips

  • Host a kickoff with every execution lead to walk through the brief and capture risks live.
  • Keep KPIs to one primary and two secondary to avoid diffused focus.
  • Bake review/QA milestones into the workback to prevent last-minute rework.
  • Maintain a single source-of-truth dashboard so partner teams see timing, assets, and blockers.

Comments

Markdown supported