Skip to main content
command CX Codex

co-plan-campaign — Claude Code command: what it does, how to install

co-plan-campaign builds a structured co-marketing campaign brief covering joint messaging, target audiences, asset ownership, and governance rules.

Apache-2.0 ★ 450 updated 2026-04-03

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/co-plan-campaign.md
Open on GitHub

What co-plan-campaign does

The command orchestrates partner planning across five steps: intake, messaging alignment, channel distribution, asset tracking, and governance packet setup. It engages the partner-marketer, co-branding, and asset-manager components during execution.

Every campaign plan gets recorded as .claude/plans/plan-<timestamp>.json with dependencies, metrics, and partner roles. By default, the workflow enforces a retry limit of 2 on approval delays before escalating to leadership sponsors.

What it helps with

  • align joint value propositions and positioning across partner teams
  • map shared, owned, and paid marketing channels with explicit owners
  • establish brand compliance and legal approval checkpoints
  • generate an auditable campaign plan file in JSON format

Example prompts for the agent

  • /partner-co-marketing-orchestration:co-plan-campaign --campaign "AI Launch Tour" --partners "Acme,Northwind" --window 8weeks
  • /partner-co-marketing-orchestration:co-plan-campaign --campaign "Joint Webinar" --partners "BetaCorp" --window 3weeks --objectives "leads,ARR"

How to install co-plan-campaign

Manually: put the files in place

.claude/commands/co-plan-campaign.md

Call it with /co-plan-campaign. For all projects use ~/.claude/commands/

Questions about co-plan-campaign

How to install co-plan-campaign in Claude Code?

Save the command definition file at .claude/commands/co-plan-campaign.md.

What does co-plan-campaign do?

It generates a complete joint marketing brief, maps channel responsibilities, and tracks creative deliverables across organizations.

Where does the command store the generated campaign plan?

It writes the plan with roles, task IDs, and dependencies into .claude/plans/plan-<timestamp>.json.

Source text

co-plan-campaign.md · Apache-2.0
---
name: co-plan-campaign
description: Builds a joint marketing brief with objectives, audiences, assets, and responsibilities across partners.
usage: /partner-co-marketing-orchestration:co-plan-campaign --campaign "AI Launch Tour" --partners "Acme,Northwind" --window 8weeks
---

# Command: co-plan-campaign

## Inputs
- **campaign** – name of the joint initiative.
- **partners** – comma-separated partner org names.
- **window** – planning horizon or launch window.
- **objectives** – optional KPIs (pipeline, signups, ARR, adoption).
- **audiences** – optional personas or regions.

### GTM Agents Pattern & Plan Checklist
> Based on GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325.

- **Pattern selection**: Co-planning typically follows a **pipeline** (intake → messaging → channel → assets → governance). If channel and asset workstreams can run in parallel, log a **diamond** segment with merge gate in the plan header.
- **Plan schema**: Save `.claude/plans/plan-<timestamp>.json` capturing objectives, partner roles, task IDs, dependencies (legal/compliance, asset repos, data sharing), error handling, and success metrics (pipeline, sourced revenue, lead targets).
- **Tool hooks**: Reference `docs/gtm-essentials.md` stack—Serena for asset template diffs, Context7 for partner/brand guidelines, Sequential Thinking for steering committee checkpoints, Playwright for QA of landing pages/microsites.
- **Guardrails**: Default retry limit = 2 for approval delays or dependency blockers; escalation ladder = Partner Marketer → Partner Ops Lead → Exec Sponsors across companies.
- **Review**: Run `docs/usage-guide.md#orchestration-best-practices-puerto-parity` before execution to confirm owners, dependencies, deliverables.

## Workflow
1. **Brief Intake** – capture each partner's goals, offers, ICP, and available assets.
2. **Messaging & Offer** – align on key narrative, value props, and differentiation.
3. **Channel Plan** – map owned, shared, and paid channels with cadence + owners.
4. **Asset Requirements** – detail creative needs, content formats, localization, and compliance.
5. **Governance Packet** – document approvals, brand guidelines, legal checkpoints, and comms plan.

## Outputs
- Joint campaign brief (objectives, audience, narrative, KPIs, timeline).
- Asset + channel tracker with partner assignments and due dates.
- Risk + dependency log for cross-org coordination.
- Plan JSON entry stored/updated in `.claude/plans` for audit trail.

## Agent/Skill Invocations
- `partner-marketer` – leads agenda and stakeholder alignment.
- `co-branding` skill – enforces visual + messaging standards.
- `asset-manager` – tracks deliverables and approval workflow.

## GTM Agents Safeguards
- **Fallback agents**: note substitutes (e.g., Partner Ops covering Partner Marketer) when stakeholders unavailable.
- **Escalation triggers**: if approvals or legal checkpoints miss SLA twice or partners deviate from guardrails, escalate to governance council per GTM Agents rip-cord.
- **Plan maintenance**: update plan JSON/change log whenever objectives, owners, or compliance requirements change to keep audit parity.

---

© gtmagents · Apache-2.0 · gtmagents/gtm-agents

Similar slash commands

All slash commands for Marketing and content →

From the same set224

The whole set →
monitor-loyalty monitor-loyalty — a command to evaluate loyalty program health: tracks member engagement, churn risk, and experiment impact. Surfaces at-risk segments and growth opportunities across tiers and regions. CX Codex +1 ★ 450repo stars define-events define-events creates an analytics instrumentation specification with event schemas, owners, and QA steps. Useful when aligning tracking plans across CDPs, product analytics, and warehouses. CX Codex +1 ★ 450repo stars define-profiles The define-profiles command maps audience profile schemas, data sources, and activation needs. Use it to plan personalization across selected channels. CX Codex +1 ★ 450repo stars optimize-nurture optimize-nurture is a Claude Code command that turns nurture metrics and test results into an optimization plan. It flags weak stages and assigns follow-up work with owners and due dates. CX Codex +1 ★ 450repo stars implement-actions implement-actions is a Claude Code command that turns a prioritized customer-journey initiative into coordinated workstreams, ownership, and measurement. CX Codex +1 ★ 450repo stars prioritize-accounts The prioritize-accounts command ranks target accounts by composite intent score, identifies coverage gaps, and recommends plays for each segment. CX Codex +1 ★ 450repo stars configure-rewards configure-rewards orchestrates reward catalog setup, fulfillment workflows, and QA verification prior to a loyalty program launch. CX Codex +1 ★ 450repo stars configure-branches The configure-branches command for Claude Code generates step-by-step instructions for configuring branching, personalization, and automations in nurture campaigns. CX Codex +1 ★ 450repo stars

Project sponsors

Companies that keep this analytics open