content-calendar

# Content Calendar Skill Manage editorial content through 6 pipeline stages: Ideas, Outlined, Drafted, Editing, Ready, Published. All pipeline state lives in a single `content-calendar.md` file -- this is the sole source of truth, never store state elsewhere. ## Reference Loading Table | Signal | Load These Files | Why | |---|---|---| | calendar file location, template, section formats | `calendar-format.md` | Loads detailed guidance from `calendar-format.md`. | | errors, error handling | `error-handling.md` | Loads detailed guidance from `error-handling.md`. | | velocity tracking and stuck-content detection | `metrics.md` | Loads detailed guidance from `metrics.md`. | | executing view, add, move, schedule, archive operations | `operations.md` | Loads detailed guidance from `operations.md`. | | stage definitions and transition rules | `pipeline-stages.md` | Loads detailed guidance from `pipeline-stages.md`. | ## Instructions ### Phase 1: READ PIPELINE **Goal**: Load and validate the current calendar state before any mutation. Memory of pipeline state is unreliable -- always read the actual file, because assumed state leads to overwrites of changes made by other processes or manual edits. 1. Read `content-calendar.md` from the project root. Also read the repository CLAUDE.md to ensure compliance with project-specific rules. 2. Parse pipeline sections -- extract entries from Ideas, Outlined, Drafted, Editing, Ready, Published, and Historical sections. 3. Validate file s...