| name | content-calendar |
| description | Produce a planned, on-voice content pipeline from a few content pillars — map each piece to a funnel stage + persona, atomize one core asset into many derivatives, schedule with owner/status, attach a distribution plan, and pass a quality gate. Built for steady B2B technical-content cadence (incl. data-backed seasonal series). |
| version | 1.0.0 |
| category | marketing |
| applies-to | ["hermes","claude","codex","gemini"] |
| trigger | manual |
| auto_execute | false |
| tags | ["marketing","content","calendar","linkedin","cadence","distribution","b2b"] |
Content Calendar
The PRODUCE stage of the marketing operating system (see ../INDEX.md).
Turns the campaign plan's message into a repeatable, on-voice content pipeline.
Use when
The user asks to "build a content calendar", "plan posts", "set a posting cadence",
"create a seasonal/data-backed series", or wants a steady stream of LinkedIn/newsletter
content tied to the campaign.
Goal
A scheduled pipeline where every item maps to a pillar + persona + funnel stage, a core
asset is repurposed into many derivatives, and each piece ships with a distribution plan —
not a backlog of orphan post ideas.
Inputs to gather
- The campaign plan (objective, ICP, message) from
marketing-campaign-plan.
- Content pillars — 3–6 recurring buyer problems the firm is credible on.
- Voice/brand notes and any approved-claims library (see
../_shared/claims-library.md).
- Source material for data-backed pieces (datasets, incident stats, standards, case data).
- Cadence + channels (page, personal profiles, newsletter), and the publish owner.
Method
- Set 3–6 pillars, each tied to a buyer problem and a service line.
- Pick formats by performance: document/carousel PDFs and polls reach + dwell highest;
native video next; plain text/image lowest; avoid external links in-post (put the link
in a comment or the page CTA).
- Atomize: take one core asset (a study, a calculator, a case) and derive several
posts, a carousel, a poll, a newsletter edition.
- Map every row to pillar + persona + funnel stage so the calendar serves the funnel,
not just the feed.
- Schedule with owner + status. Cadence: ~2–5 posts/week across page + personal
profiles; best windows midweek mornings local; the first ~60 minutes drive reach.
- Attach a distribution plan per piece (who reshares, employee advocacy, newsletter
push, comment-seeding). Plan roughly as much effort for distribution as creation.
- Quality gate before queueing (below).
- For data-backed series: cite the dataset, keep claims defensible, use a consistent
visual/format, and stamp the data vintage.
Output
A calendar (table: date · pillar · persona · funnel stage · format · hook · owner · status ·
distribution) plus drafted/queued items. Store in the engagement's content folder.
