operating-calendar
Purpose
The Operating Calendar is the artifact that converts an organization's rhythm of decisions from "when calendars align" into a published, versioned, audited schedule. It sequences the canonical rituals named throughout the Vision to Value framework into a four-layer cadence stack so the organization stops negotiating its rhythm ad-hoc each quarter.
A calendar that lives only in individual leaders' heads is a Product Operations failure. This skill produces the calendar as an artifact: human-readable markdown for the leadership team and a structured JSON sidecar that downstream skills and integrations can consume.
Vision to Value Phase
Cross-phase — the Operating Calendar carries rituals that span Strategic Foundation through Learning Loop. It is itself a Phase 6 (Learning Loop) artifact because a calendar that does not produce reviewable decision artifacts is a calendar that has stopped serving the loop.
Prerequisites: Named ritual owners exist at the four altitudes (team / product-line / portfolio / customer). Decision Record Template (Appendix A) is in use, so the calendar can point at where each ritual writes its output.
Consumed by: /portfolio-status (pulls the next portfolio-review window), /maturity-check (assesses cadence stack against the Three Tiers + sub-Series-C lane), /cadence-adherence-telemetry (Wave 4 — measures whether scheduled rituals produced their named output artifacts). The JSON sidecar is the integration substrate; concrete calendar-system integrations (Google Calendar sync, Slack reminders, Outlook sync) are out of scope and live in personal config or Extension Teams per master plan §25 Park bucket §5.
Document Intelligence
This skill supports three modes: Create, Update, and Critique.