Agent skill · operations · github
gtm-operating-cadence
Design meeting rhythms, metric reporting, quarterly planning, and decision-making velocity for scaling companies. Use when decisions are slow, planning is broken, the company is growing but alignment is worse, or leadership meetings consume all time without producing decisions.
Why this skill is useful
Provides a structured framework for meeting rhythms and decision-making processes that are essential for scaling companies, which the AI may not generate independently.
What it needs
About 10k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
Operating Cadence The meeting structure that worked at 30 people collapses at 100. What worked at 100 collapses at 300. The failure mode is always the same: too many people in too many meetings making too few decisions. When to Use Triggers: "Our meetings don't produce decisions" "We're growing but alignment is getting worse" "How often should we meet?" "Nobody knows what's happening across functions" "Decisions take forever" "Leadership is in meetings all day" Context: Companies scaling from 20 to 300+ people Post-PMF through growth stage Distributed / remote teams Any stage where "we need to talk about this" has become the default --- Core Frameworks 1. The Five-Level Meeting Architecture The Pattern: Different meetings serve different purposes. Conflating them creates either inefficiency (too much time) or confusion (unclear decisions). Separate meetings by function, frequency, and decision authority. Level 1: Daily Standup (15 min, teams only) What we finished yesterday, what we're starting today, what's blocking us 5-10 people max. Whole-company standups are theater Anti-pattern: Status reporting (use Slack, not meetings) Anti-pattern: Strategic discussion (wrong time, wrong place) Success criteria: Finishes in 15 minutes, surfaces 1-2 blockers Level 2: Weekly Functional Reviews (60 min, function leadership) Each function gets its own weekly rhythm: Product team Friday 4pm: metrics, user feedback, roadmap blockers GTM team Tuesday 4pm: pipeline, customer updates, deal health Engineering Wednesday 4pm: velocity, bug backlog, deployment Format: Metric recap (10 min) → Wins/blockers (15 min) → One deep-dive (30 min) → Next week priorities (5 min) Anti-pattern: Trying to solve every problem in the meeting. Pick 1-2, delegate the rest to follow-ups. Level 3: Weekly All-Hands (60 min, whole company) The single most important alignment mechanism at a scaling company. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/gtm-operating-cadence