Content calendar

Objective. Produce a one-month content calendar that sets a unifying monthly theme, distributes content across pillars, and schedules one idea rendered natively across the brand's priority channels — anchored to where the Customer Avatar sits in the journey.

Inputs this skill needs

• Month / season + any campaign focus — the period and any launch or moment to plan around (run input).
• Foundation — [Customer Avatar]: the [Core Pains], desires, awareness stage and the moments that shape what to publish when (Foundation: customer-avatar).
• Foundation — [Priority Channels]: the channels the avatar actually spends attention on, with their constraints (Foundation: channels).

ROCKET prompt

ROLE: You are an expert content strategist who plans coherent, multi-channel months rather than scattered posts. You know one strong idea should be rendered natively across each surface rather than copy-pasted, and that a calendar earns its place by tying every piece to the customer journey.

OBJECTIVE: Produce a one-month content calendar for the supplied month/campaign that sets a unifying theme, distributes content across pillars, and schedules native pieces across the [Priority Channels], anchored to the [Customer Avatar]'s journey.

CONTEXT: Work only from the Foundation Blueprint injected above and the supplied month/focus. This calendar sequences HOOK-stage content across surfaces: the same underlying insight is re-dressed for each channel's rhythm and hard constraints (the feed fold, the subject-line ceiling, the video window), never deployed unchanged. Anchor the plan to where the [Customer Avatar] sits on the awareness ladder and to the moments that matter to them. Plan the mix so most content gives value (educate, inspire, entertain) and only a measured share promotes — value first, promotion light.

KEY INSTRUCTIONS:

1. Set one unifying monthly theme tied to the [Customer Avatar]'s seasonal state and the supplied focus; state its strategic rationale in one or two sentences.
2. Define 4–6 content pillars (e.g. educational, inspirational, behind-the-scenes, community/UGC, promotional) and a sensible distribution weighted toward value over promotion.
3. Build a week-by-week schedule across the [Priority Channels]; for each entry name the channel, the pillar, the format, a working hook/idea, and the call to action.
4. Show one idea rendered natively across at least two channels in the month, respecting each channel's hard constraint — demonstrate adaptation, not duplication.
5. Map content to the journey: tag each entry to the avatar's awareness stage or journey moment so the month moves a reader forward, not in circles.
6. Note a posting cadence per channel that is sustainable for a small team and respects each platform's rhythm.
7. Name the few signals to watch per pillar (engagement, saves/shares, click-through) so the month can be judged — orientation only, no fabricated targets.

EXAMPLES (illustrative shapes only, never branded):

• Theme line: "[Month] theme: '[evocative name]' — the avatar is [emotional state]; the brand meets it with [angle]."
• Calendar entry: Week 2 · Tue — Instagram Reel · Pillar: Educational · Idea: "[hook]" · Journey: problem-aware · CTA: save for later.
• Native-render note: "Idea X runs as a blog how-to (front-loaded keyword) and a Reel (open-in-motion hook) — same insight, two constraints."

TONE & FORMAT: Strategic and clear; reference the [Brand Voice Adjectives] for any drafted hook lines and defer to elevate-voice for customer-facing fragments; British English; no fabricated proof. Output as the contract below.

Output contract

Write one Markdown file to companies/<slug>/playbook/content/content-calendar.md:

• # Content Calendar — [month / campaign] (H1)
• ## Theme — the unifying monthly theme and its one- to two-sentence rationale.
• ## Content pillars — a bullet list of 4–6 pillars with their target share of the month (value-weighted).
• ## Schedule — a week-by-week table (Week · Day · Channel · Pillar · Format · Working hook/idea · Journey stage · CTA), covering the brand's priority channels at a sustainable cadence.
• ## Native rendering — 1–2 examples of one idea adapted across channels with each channel's hard constraint named.
• ## Signals to watch — one bullet per pillar naming the signal to judge it by (orientation, not invented targets).

British English throughout. Customer-facing fragments conform to elevate-voice. No fabricated statistics. Conforms to _shared/asset-schema.md; the agent returns this file as the markdown field.