build-posting-calendarlisted

# /build-posting-calendar — 30-Day Editorial Calendar > **Purpose.** Build the 30-day editorial calendar for a single subject (the agency operator OR a specific client). Output is a day-by-day schedule with: pillar slot, post type, hook drawn from the hook library, draft cue (3-line brief for the writer), publishing window, cross-post target, and comment-magnet target. The calendar is what `/write-linkedin-post` and `/ghostwrite-client-post` pull from each day. > > **Bar.** A ghostwriter handed this calendar should walk to day_17 and produce a publish-ready post in <30 minutes without re-reading the engine. The calendar is the daily operating contract — pillar discipline, hook freshness, voice scope, and conversion bridges converge into one file. Upstream: `/build-content-engine` + `/build-hook-library`. Downstream: every post-production skill consumes day-N entries. ## When to invoke - New content engine just built (run immediately after `/build-content-engine` for the same scope) - New client onboarded (build `client-content` calendar for the client_slug after their content engine ships) - Monthly cadence — every 30 days, the calendar is rebuilt, never extended (extension breeds drift) - Phase shift in `reference/playbooks/hybrid-full-stack.md` (Phase 1→2 or 2→3) — pillar mix changes, calendar rebuilds - Engagement plateau ≥3 weeks (signal that pillar mix or hook library is stale; calendar rebuild forces a refresh) - Offer change — content-to-conversion bridges shift, ca