Gtm Operating Cadence
Design leadership meeting rhythms, metrics reviews, and quarterly planning so a growing team makes decisions faster instead of living in alignment meetings.
Overview
gtm-operating-cadence is an agent skill most often used in Grow (also Operate iterate, Validate scope) that designs meeting rhythms, metrics, and quarterly planning for faster decisions at scale.
Install
npx skills add https://github.com/github/awesome-copilot --skill gtm-operating-cadenceWhat is this skill?
- Five-level meeting architecture from daily standups to exec forums
- Separates decision authority, frequency, and forum purpose to cut meeting sprawl
- Quarterly planning and metric reporting patterns for 20–300+ person contexts
- Triggers for slow decisions, broken planning, and remote alignment gaps
- Core frameworks section for operating cadence at each growth breakpoint
- Daily standup capped at 15 minutes in Level 1 pattern
Adoption & trust: 1.3k installs on skills.sh; 34.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your company is growing but meetings eat the calendar and cross-functional decisions never stick.
Who is it for?
Founders and leads between roughly 20 and 300 people—or indie teams about to add GTM and eng heads—who need an explicit operating system.
Skip if: Solo builders with no team cadence problem yet, or pure technical implementation work with no org design angle.
When should I use this skill?
Decisions are slow, planning is broken, the company is growing but alignment is worse, or leadership meetings consume time without producing decisions.
What do I get? / Deliverables
You get a layered meeting and planning cadence with clear decision forums, metric rhythms, and quarterly structure your team can adopt.
- Meeting calendar architecture by level and frequency
- Quarterly planning and metric reporting outline
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Grow because the skill targets post-PMF scaling—metrics, cadence, and cross-functional alignment as usage and headcount compound. Lifecycle fits recurring customer and business rhythms (reporting, planning cycles) rather than one-off launch distribution or infra firefighting.
Where it fits
Define weekly metric reviews and monthly business reviews before adding a second sales pod.
Retune meeting levels after a reorg so exec forums stop duplicating product syncs.
Lock quarterly OKRs and forum ownership before greenlighting a major feature bet.
Slot launch war-room cadence into Level 2–3 forums without hijacking daily team standups.
How it compares
Org operating-model playbook for agents, not a marketing automation skill or a sprint planning template for a single repo.
Common Questions / FAQ
Who is gtm-operating-cadence for?
Technical founders, heads of product, and GTM leads at growing SaaS or product companies who need decision speed and alignment, including small distributed teams outgrowing informal syncs.
When should I use gtm-operating-cadence?
Use it in Grow when instituting metrics and leadership rhythms; in Operate when iterating how the company runs week to week; and in Validate scope when annual or quarterly planning must lock priorities before a big build push.
Is gtm-operating-cadence safe to install?
It is advisory process content with no automatic access to your systems; confirm license and source, and use the Security Audits panel on this Prism page for the ingested package.
SKILL.md
READMESKILL.md - Gtm Operating Cadence
# 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. - CEO update (15 min): north star progress, week focus, what's changed - Metric dashboard (10 min): same format every week (consistency enables pattern recognition) - Deep dive (20 min): one strategic topic needing team input — not a presentation, a discussion - Q&A (15 min): real questions, real answers Anti-pattern: Defensive tone. All-hands should be straightforward, not spin. Anti-pattern: Inconsistent metrics. If you change the dashboard, the team can't track progress. **Level 4: Bi-Weekly Leadership Alignment (90 min)** - North star progress (5 min) - Functional updates (30 min, 5-7 min each) - Major decisions needing resolution (30-40 min): resource conflicts, strategic pivots, customer/product decisions - Next 2 weeks planning (15 min) This is where cross-functional blockers get resolved. If functions operate independently, this meeting isn't working. **Level 5: Quarterly Strategic Planning (half-day to full-day)** - Previous quarter retrospective (90 min): What worked, what didn't, what we'd do differently - Next quarter planning (120 min): What are we optimizing for? What's the roadmap? - Function breakouts (90 min): Each function plans their quarter - Synthesis (60 min): Functions share commitments, resolve conflicts Anti-pattern: Too much "fun activity," not enough substance. Anti-pattern: No clear decisions coming out. **Scaling Adjustments:** - **<30 people**: Levels 2-3 only. Skip daily standups (you see everything). Skip bi-weekly leadership (you ARE leadership). - **30-100 people**: Add all