--- name: scale-operating-calendar description: Builds the weekly, monthly, quarterly, and annual operating rhythm for the GTM AI OS, with owners and the artifact each meeting reads. Use when the user says "set the cadence", "operating rhythm", "what meetings do we need", "build the calendar", "how do we keep this going", or after scale-exec-dashboard. --- # scale-operating-calendar Produce `artifacts/scale-calendar.md`. A dashboard nobody is scheduled to read is decoration. ## Preflight (every run) 1. Confirm `GTM-AI-OS/` is accessible. If not: "I need access to your GTM-AI-OS folder. Select it in Cowork's folder picker, or run `os-install` from the core plugin." Stop until it is. 2. Read `CLAUDE.md`, `INDEX.md`, and the last 20 lines of `signals/log.md`. 3. Check the prerequisites below. For anything missing, ask the cold-start questions and offer: (a) run the earlier skill now, or (b) fast path: answer the questions and this skill writes a minimal version of the missing artifact marked `status: draft (fast path)`. 4. On finish, update the artifact row in `INDEX.md` and append one line to `signals/log.md`: ` | | | | `. ## Prerequisites - `artifacts/scale-dashboard.md` (or at minimum `context/metrics.md` at draft). Cold-start: "Which recurring revenue meetings already exist, and who runs them?" Continue. ## Step 1: Inherit, don't add List existing meetings. Attach OS artifacts to them before creating new ones. ## Step 2: The rhythm Weekly: pipeline review by motion (reads dashboard management layer); GTM sync; signal refresh (add and retire in `signal-library.md`); one rep ride-along; kill the two weakest message templates. Monthly: signal and template review; rewrite the two worst messages; territory and data hygiene; sponsor drip summary. Quarterly: full pattern analysis; ICP band refresh from win/loss (re-run `os-win-loss-extract`); motion reallocation; promotion and PIP inputs. Annually: ICP redefinition; motion architecture; team structure; re-run Module 1. For each: owner, day, artifact read, artifact updated. ## Step 3: Place it If `~~calendar` is connected and the user approves, create the recurring events with the artifact links in the description. ## Step 4: Write Write the calendar. Update `INDEX.md`. ## Hand off Say: "Decide who owns AI in the org. Run `scale-coe-charter`."