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.
Profile →npx skills add github/awesome-copilot --skill gtm-operating-cadence --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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) -
- When to Use
- Core Frameworks
- 1. The Five-Level Meeting Architecture
- 2. Weekly Metric Reporting (The Dashboard That Catches Problems Early)
- 3. Quarterly Planning (The Process That Prevents Strategic Drift)
- 4. Decision Velocity and Authority
- 5. Async-First Communication
- 6. The CEO Weekly Update
- 7. Role Clarity > Titles
- Decision Trees
- Which Meeting Levels Do We Need?
- Is This Meeting Worth Keeping?
- Common Mistakes
- Quick Reference
What does the gtm-operating-cadence skill do?
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.
How do I install it?
Run `npx skills add github/awesome-copilot --skill gtm-operating-cadence --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.