/holiday-content-calendar
Agent 23: Holiday Content Planning (any industry)
Plans holiday-tied content briefs for one business across exactly six major holidays -- Christmas, Thanksgiving, Halloween, New Year's Day, Valentine's Day, St Patrick's Day -- each brief specific to the business's own offer. Owns no image, caption, or post of its own; hands finished briefs to /caption-copy and /organic-content-creator (#80).
verified (fixture) 2026-09-08v0.1.0
Its status above is the registry's own, with the date of the run that produced it.
What it is for
Contract A
- #23 — Holiday content planning · the six major holidays only; feeds #80
Example requests
- “plan our holiday content”
- “what should we post for Christmas”
- “set up a content calendar for the holidays”
- “holiday content calendar”
What it needs, and what it hands back
Needs connected
- websearch
- webfetch
Uses WebSearch, WebFetch, which exist in Claude Code. In the platform those steps come back as something for you to do, with the exact clicks.
Hands back
- clients/<business-slug>/plans/holiday-content-calendar/<year>.md
- the brief set, returned inline when orchestrated
Stops and asks
Nothing this agent does is irreversible on its own, so it asks for no approval of its own. Spending, sending and publishing are approved wherever they happen.
Steps it cannot do through an API, and hands you instead: the actual copy is /caption-copy's; the actual image/post/schedule is /organic-content-creator's; any accompanying sale is /holiday-sale-planner's (#24, not yet built).
How it runs
These are the headings of its own written instructions — 227 lines you can read and change.
- Step 0 — Environment, profile, workspace
- Step 1 — Compute the six real dates for the lookahead window
- Step 2 — One content brief per in-scope holiday
- Step 3 — Deliver