Skip to main content
command CX Codex

distribute-assets — Claude Code command for campaign distribution

distribute-assets is a Claude Code command that builds a channel-by-channel publishing and promotion plan with timing, UTMs, and partner coordination. It helps campaigns set clear owners and track results.

Apache-2.0 ★ 450 updated 2026-04-03

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

What distribute-assets does

The command maps campaign assets to channels, assigning timing, calls to action, and owners. It outlines publishing preparation, including asset variants, localization, and approvals, then plans promotion across paid placements, partners, internal communications, and enablement.

It produces a distribution calendar, an amplification checklist, and a measurement and feedback plan. The command stores or updates a plan entry in .claude/plans/plan-<timestamp>.json, with stages, task IDs, channel groupings, guardrails, and success metrics. Failed publishes use a retry limit that defaults to 2. Account for that limit when planning the publishing workflow.

What it helps with

  • map campaign assets to channels and publication dates
  • coordinate partner promotion and internal communications
  • define UTM tracking and reporting checkpoints
  • record campaign stages in a JSON plan

Example prompts for the agent

  • Create a distribution plan for the “AI readiness” campaign across blog,email,linkedin with partner Acme: /content-pipeline-orchestration:distribute-assets --pillar "AI readiness" --channels "blog,email,linkedin" --partners "Acme".
  • Plan publishing dates and amplification for the “product launch” campaign across email,social,partner.
  • Add a base UTM template and paid boost parameters to the “AI readiness” campaign plan.

How to install distribute-assets

Manually: put the files in place

.claude/commands/distribute-assets.md

Call it with /distribute-assets. For all projects use ~/.claude/commands/

Questions about distribute-assets

How do I install distribute-assets in Claude Code?

Add the command file to your project at .claude/commands/distribute-assets.md.

What does distribute-assets do?

It plans how campaign assets move through selected channels, including publishing, promotion, and measurement. The plan is stored in .claude/plans as a JSON entry.

Which options can I pass to distribute-assets?

Provide a campaign or content pillar and a comma-separated channel list. Partner names, a base UTM template, and paid boost parameters are optional.

Source text

distribute-assets.md · Apache-2.0
---
name: distribute-assets
description: Creates a distribution + amplification plan with schedule, UTMs, and partner alignment.
usage: /content-pipeline-orchestration:distribute-assets --pillar "AI readiness" --channels "blog,email,linkedin" --partners "Acme"
---

# Command: distribute-assets

## Inputs
- **pillar** – content pillar or campaign name.
- **channels** – comma-separated list (blog, CMS, email, social, paid, partner, enablement).
- **partners** – optional partner/community co-marketing list.
- **utm** – optional base UTM template.
- **boosts** – optional paid boost budget or parameters.

### GTM Agents Pattern & Plan Checklist
> Mirrors GTM Agents orchestrator guidance @puerto/plugins/orchestrator/README.md#112-325.

- **Pattern selection**: Default to **pipeline** (mapping → prep → amplification → measurement → feedback). If channel prep + amplification can run in parallel, log a **diamond** with merge gate.
- **Plan schema**: Save `.claude/plans/plan-<timestamp>.json` capturing objective, stages, task IDs, channel groupings, context passing (UTMs, assets), guardrails, and success metrics (engagement, pipeline, partner reach).
- **Tool hooks**: Reference `docs/gtm-essentials.md` stack (Serena for CMS/pixel patches, Context7 for platform docs, Sequential Thinking for retro cadence, Playwright for landing/social QA).
- **Guardrails**: Set retry limit (default 2) for failed publishes; escalation ladder = Distribution Lead → Editorial Director → Marketing Director.
- **Review**: Use `docs/usage-guide.md#orchestration-best-practices-puerto-parity` checklist before execution to confirm agents, dependencies, deliverables.

## Workflow
1. **Channel Mapping** – assign assets to channels with timing, CTA, and owner.
2. **Publishing Prep** – outline CMS/social scheduler steps, asset variants, localization, and approvals.
3. **Amplification Plan** – coordinate paid boosts, influencer/partner drops, internal comms, enablement uploads.
4. **Measurement Hooks** – define UTMs, dashboards, alerting, and reporting cadence.
5. **Feedback & Recycling** – schedule retro checkpoints and repurposing opportunities.

## Outputs
- Distribution calendar with timestamps, channels, owners, UTMs, and status.
- Amplification checklist (partners, paid, internal enablement, ABM tie-ins).
- Measurement + feedback plan.
- Plan JSON entry stored/updated in `.claude/plans` for audit trail.

## Agent/Skill Invocations
- `distribution-lead` – drives publishing + amplification.
- `distribution-checklist` skill – ensures operational rigor per channel.
- `editorial-director` – confirms narrative alignment.

## GTM Agents Safeguards
- **Fallback agents**: document substitutes (e.g., Editorial Director covering Distribution Lead) when specialists unavailable.
- **Escalation triggers**: if UTMs misfire, partner SLAs slip, or alert thresholds breach twice within 48h, trigger escalation to Content + Growth leadership per GTM Agents runbook.
- **Plan maintenance**: update plan JSON + change log whenever channels, partners, or measurement hooks change to maintain GTM Agents-grade auditability.

---

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

Similar slash commands

All slash commands for Agent setup: memory, context, orchestration →

From the same set224

The whole set →
plan-pillar plan-pillar builds a content pillar plan with hero assets, derivative pieces, and a distribution schedule. Saves task dependencies and KPIs directly to JSON. CX Codex +1 ★ 450repo stars forecast-discipline forecast-discipline — a Claude Code skill that builds forecast-call methodology: commit/best case/pipeline tiers, inspection checklists, and accuracy thresholds. Runs when you prepare weekly or monthly sales forecasts. CX Codex +1 ★ 450repo stars plan-plays plan-plays builds an ABM playbook roadmap across account tiers, mapping plays, channels and timelines to a chosen campaign objective. CX Codex +1 ★ 450repo stars social-calendar-system social-calendar-system is a Claude Code skill that structures multi-channel social media calendars, approval routing, and publishing checklists. CX Codex +1 ★ 450repo stars 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

Project sponsors

Companies that keep this analytics open