Skip to main content

plan-a-media-release-calendar

Plan a media release calendar across production readiness, rights, channels, audiences, dependencies, promotion, and measurement. Use when multiple assets or episodes must publish in a coordinated sequence.

Source facts

Repository
protosphinx/sphinxstack
Last source activity
July 29, 2026 at 13:55
Detected SKILL.md language
English
Stars
3
Forks
0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer
2 files

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
plan-a-media-release-calendar
category
write
description
Plan a media release calendar across production readiness, rights, channels, audiences, dependencies, promotion, and measurement. Use when multiple assets or episodes must publish in a coordinated sequence.
# plan-a-media-release-calendar Schedule from evidence of readiness and audience logic, not from an arbitrary volume target. ## Procedure 1. Define series purpose, audience, channels, cadence, window, and success measures. 2. Inventory assets, owners, production stage, rights, accessibility, locales, and dependencies. 3. Map launches, events, holidays, embargoes, audience habits, and channel constraints. 4. Sequence anchors, supporting cuts, trailers, excerpts, newsletters, and follow-up. 5. Set lock, review, caption, clearance, delivery, scheduling, and promotion deadlines. 6. Add owner, status, approval, source link, version, and contingency for every release. 7. Protect production capacity and create buffers for high-risk or timely work. 8. Review conflicts, fatigue, accessibility, and rights expiry. 9. Track actual publication and outcomes, then update future cadence. ## Guardrails - Never schedule an asset as ready while rights or accessibility remain unresolved. - Do not optimize cadence at the expense of participant safety or factual review. - Keep editorial and sponsored obligations distinguishable. ## Done - A release calendar records assets, channels, dependencies, owners, and gates - Rights, accessibility, localization, timing, and contingency are verified - Published results reconcile with the planned versions and status
View on GitHub