content-pipeline — Claude Code command: what it does, how to install
content-pipeline builds an editorial calendar and distribution plan for a multi-channel content program, given a timeframe and publishing cadence.
Apache-2.0 ★ 450 updated 2026-04-03
.claude/commands/content-pipeline.mdWhat content-pipeline does
The /content-marketing:content-pipeline command takes a program name plus --duration and --frequency flags, with optional --channels, --personas and --assets. It returns a calendar, asset briefs carrying key messages, CTAs and SEO targets, a per-channel distribution checklist, and a measurement plan with KPIs mapped to awareness, consideration and decision stages.
The work runs through five phases: aligning goals and personas, drafting the calendar with pillar pieces and their channel-specific derivatives, assigning owners and review gates for production, scheduling owned, earned and paid pushes with UTM tracking, and closing with a metrics review that feeds the next cycle's topics.
Each pillar asset is meant to carry a distribution plan before production starts, so a calendar built without that pairing skips the step the command is built around.
What it helps with
- draft a quarter-long or multi-week editorial calendar
- write briefs for pillar assets and their derivative formats
- assign owners and review gates for a content sprint
- schedule channel distribution with UTM tracking
- consolidate funnel-stage KPIs into one measurement plan
Example prompts for the agent
- /content-marketing:content-pipeline "Q1 Thought Leadership" --duration 3months --frequency weekly
- /content-marketing:content-pipeline "Product Launch" --duration 6weeks --frequency biweekly --channels blog,email,social
- /content-marketing:content-pipeline "Webinar Series" --duration 2months --frequency monthly --assets pillar,video
How to install content-pipeline
Manually: put the files in place
.claude/commands/content-pipeline.mdCall it with /content-pipeline. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/content-pipeline.mdCall it with /prompts:content-pipeline. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/content-pipeline.prompt.mdManually: put the files in place
.gemini/commands/content-pipeline.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about content-pipeline
How do I install content-pipeline in Claude Code?
Place the command file at .claude/commands/content-pipeline.md.
What does the content-pipeline command do?
It puts together an editorial calendar, asset briefs and a distribution plan with funnel-stage KPIs for a multi-channel content program over a chosen timeframe and cadence.
What parameters does content-pipeline require?
You need a program name along with --duration and --frequency; channels, personas and asset types are optional flags.
Source text
content-pipeline.md · Apache-2.0
--- name: content-pipeline description: Plan and execute editorial calendars, asset production, and distribution workflows for GTM campaigns. usage: /content-marketing:content-pipeline "Q1 Thought Leadership" --duration 3months --frequency weekly --- # Content Pipeline Command Coordinate strategy, production, and distribution for multi-channel content programs aligned to business goals. ## Command Syntax ```bash /content-marketing:content-pipeline "<program_name>" --duration <timeframe> --frequency <cadence> ``` ### Parameters - `program_name` (positional): Theme or campaign name - `--duration`: Calendar window (e.g., 6weeks, 3months) - `--frequency`: Publishing cadence (weekly|biweekly|monthly) - `--channels`: Comma-delimited list of channels (blog,email,social,webinar) - `--personas`: Target personas for tailoring content - `--assets`: Required asset types (pillar, blog, social, video) ## Workflow Phases 1. **Strategy Alignment** – map program goals, KPIs, personas, and messaging pillars. 2. **Editorial Planning** – build calendar with pillar assets plus derivative formats per channel. 3. **Production Sprinting** – assign owners, outline briefs, define review/QA gates. 4. **Distribution & Promotion** – schedule owned, earned, and paid pushes with UTMs. 5. **Performance Review** – capture metrics, insights, and optimization backlog. ## Output Package - Editorial calendar (table/json) - Asset brief templates with key messages, CTA, SEO targets - Channel distribution checklist per asset - Measurement plan with KPIs per stage (awareness, consideration, decision) ## Best Practices - Anchor each pillar asset to a buyer-journey stage and repurpose across channels. - Pair every asset with a distribution plan before production starts. - Bake in approvals and localization windows to avoid publishing slips. - Track performance weekly; adapt upcoming topics based on leading indicators. ---
© gtmagents · Apache-2.0 · gtmagents/gtm-agents