annual-planning-workflow

Orchestrate annual GTM planning cycles with approval gates and scenario modeling.

58|21|Updated May 15, 2026
One-click install
npx skills add https://github.com/t0ddc3by/claude-for-customer-success --skill annual-planning-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: annual-planning-workflow
Source: https://github.com/t0ddc3by/claude-for-customer-success/tree/main/rev-ops/skills/annual-planning-workflow
Command: npx skills add https://github.com/t0ddc3by/claude-for-customer-success --skill annual-planning-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Annual GTM planning requires coordinating forecasting, capacity, quotas, comp modeling, and communications without skipping approval steps or producing inconsistent artifacts across teams.

Core Features & Use Cases

  • Seven-phase orchestration with approval gates: Produces phase artifacts and blocks progression until explicit human confirmation is received.
  • Scenario-driven capacity and quota planning: Runs forecast scenario modeling and uses unit-of-growth capacity calculations to inform headcount needs and sensitivity analyses.
  • Comp simulation and change communication packaging: Simulates comp outcomes, saves confirmed baselines, and packages change communications for controlled distribution.
  • Use case: Use it at the start of a fiscal year to generate a complete, gate-reviewed annual plan from forecast scenarios through board-ready deliverables while enforcing HR/Finance and RevOps dual-review constraints.

Quick Start

Ask to run the annual planning workflow for next fiscal year and produce gate-ready planning artifacts with explicit approval prompts.

Frequently Asked Questions about annual-planning-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run phased GTM planning with approval gates across forecast and capacity scenarios?

Phased GTM planning with approval gates orchestrates your annual cycle across forecast scenarios, capacity modeling, quota sensitivity, and comp simulation while blocking progression until explicit human confirmation is received.

What is unit-of-growth capacity calculation in RevOps scenario modeling?

Unit-of-growth capacity calculation in RevOps scenario modeling uses structural inputs to determine headcount needs and inform sensitivity analyses during the annual planning cycle.

How do I simulate comp outcomes and package change communications for mid-year replanning?

Comp simulation and change communication packaging during mid-year replanning simulates compensation outcomes, saves confirmed baselines, and packages communications for controlled distribution.

Does annual GTM planning require dual-review constraints before finalizing comp and territory outputs?

Yes, annual GTM planning enforces HR/Finance and RevOps dual-review constraints before comp and territory outputs are finalized to ensure cross-team alignment.

Can I execute a single phase of the annual planning workflow instead of the full cycle?

Yes, the annual planning workflow supports optional single-phase execution for mid-year replan triggers while still enforcing G-code governance constraints for scenario ranges.

What planning configuration is needed to start the annual GTM planning cycle?

Starting the annual GTM planning cycle requires reading planning configuration from Claude plugin config to govern scenario ranges, capacity structural inputs, and approval gates.