Agent skill

Quarterly Planning

by borghei in borghei/Claude-Skills

Run the full quarterly planning cycle -- pre-quarter homework, kickoff, weekly Wodtke rhythm, mid-quarter check-in, and close retro -- using Radical Focus, Cagan strategy, and a fixed planning…

MITAuto-check passedProduct & Project Management

Install Quarterly Planning

skills CLI
$ npx skills add borghei/Claude-Skills --skill quarterly-planning -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install borghei/Claude-Skills quarterly-planning --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/project-management/execution/quarterly-planning .claude/skills/quarterly-planning && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
quarterly-planning
GitHub stars
886
Token cost
~1.8k tokens
SKILL.md length
797 words
Files
9 (incl. references, assets)
Skills in repo
354
Repo updated
First seen
Licence
MIT

At a glance

Run the full quarterly planning cycle -- pre-quarter homework, kickoff, weekly Wodtke rhythm, mid-quarter check-in, and close retro -- using Radical Focus, Cagan strategy, and a fixed planning…

  • Tasks that involve Product roadmapping
  • SKILL.md covers Overview, Core Capabilities, Clarify First and The Quarterly Cycle, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Tasks that involve OKRs and executive reporting

What it does

Quarterly Planning is an agent skill from borghei/Claude-Skills. Run the full quarterly planning cycle -- pre-quarter homework, kickoff, weekly Wodtke rhythm, mid-quarter check-in, and close retro -- using Radical Focus, Cagan strategy, and a fixed planning cadence around your OKRs.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including reference files and assets (for example `assets/close_retro_template.md`, `assets/kickoff_agenda_template.md` and `assets/mid_quarter_check_in_template.md`).

It sits in Product & Project Management, covering Product roadmapping and OKRs and executive reporting. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.

When your agent uses it

  • Tasks that involve Product roadmapping
  • Tasks that involve OKRs and executive reporting

Example prompts

  • “/quarterly-planning”

What it can do on your machine

Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Quarterly Planning loads about 1.8k tokens when it runs, and up to ~12k if it reads all its reference files. Until then it costs about 59 tokens; SKILL.md has 797 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~59
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~12k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 797 words, ~1,814 tokens.

Download SKILL.mdSave it as .claude/skills/quarterly-planning/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.
name
quarterly-planning
description
Run the full quarterly planning cycle -- pre-quarter homework, kickoff, weekly Wodtke rhythm, mid-quarter check-in, and close retro -- using Radical Focus, Cagan strategy, and a fixed planning cadence around your OKRs.
license
MIT + Commons Clause
metadata.version
1.0.1
metadata.author
borghei
metadata.category
project-management
metadata.domain
pm-execution
metadata.updated
2026-06-15
metadata.tech-stack
quarterly-planning, okrs, product-strategy, radical-focus

Quarterly Planning Expert

Overview

Quarterly planning is the operating cadence that turns annual strategy into quarterly outcomes. Done well, it produces aligned OKRs, a roadmap that delivers them, a capacity plan that respects reality, and a tracking ritual that catches drift before it compounds. Done poorly, it produces OKR theater -- a slide deck of objectives that nobody references after week two.

This skill is the above-OKR-writing companion to execution/brainstorm-okrs/. Where brainstorm-okrs/ covers how to write good OKRs, this skill covers the full quarterly cycle around them: pre-quarter homework, kickoff agenda, mid-quarter check-in, close-of-quarter retro, and the weekly/biweekly tracking cadence. The framework synthesizes four sources: Wodtke's Radical Focus (Monday-commit / Friday-celebrate rhythm, one OKR per quarter), a product strategy cycle (explicit upstream strategy choices), Cagan's quarterly product strategy, and the RAD ritual (Reflect-Align-Decide) used inside each meeting.

Core Capabilities

  • Pre-quarter homework -- strategy review, outcome candidate list, capacity assessment, and the 1-page kickoff brief
  • Kickoff facilitation -- the 2-3hr RAD agenda that commits OKRs, roadmap, and capacity
  • Weekly Wodtke rhythm -- Monday Commit, Friday Celebrate, biweekly KR confidence review
  • Mid-quarter check-in -- carry / kill / pivot / escalate decisions at week 6
  • Close retro -- 0.0-1.0 OKR scoring, learning extraction, and next-cycle seeding

Clarify First

Before running a phase, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • Which phase — pre-quarter/kickoff vs mid-quarter check-in vs close retro (selects the agenda and artifacts produced)
  • Position in the 13-week cycle — what week you're in (the carry/kill/pivot check belongs at ~week 6, the retro at week 13)
  • Existing OKRs & strategy — the committed Objective and the annual strategy it serves (the kickoff commits OKRs; every Objective must trace to a vision pillar)
  • Real team capacity — honest capacity after PTO/on-call (a stretch slate dressed as commitments is the #1 cadence failure)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

The Quarterly Cycle

Week -3   -1     0       1-5    6      7-12    13
  | Pre-quarter | Kickoff |  Mid-quarter  | Close
  |  homework   | (start) |   check-in    | retro
  +-Strategy/Cagan--+-- Wodtke weekly Mon/Fri rhythm --+
  • Pre-quarter (weeks -3 to -1): run the homework and kickoff to commit OKRs and roadmap.
  • Mid-quarter (~week 6): run the check-in to course-correct.
  • Close (week 13): run the retro to extract learning before the next cycle.

When to Use

  • Pre-quarter (2-3 weeks before start). Run the homework and kickoff to commit OKRs and roadmap.
  • Mid-quarter (~week 6 of 13). Run the mid-quarter check-in to course-correct.
  • Close-of-quarter (last week). Run the close retro to extract learning before next planning cycle.
  • New PM joining mid-quarter. Understand where the team is in the cycle and what is expected when.
  • Failing OKR cadence. Team has OKRs but no one references them by week 4 -- reset the ritual.
Show full SKILL.md (361 more words)Show less

References

Load the reference that matches the task -- keep this file lean and pull detail on demand:

  • references/cycle-playbook.md -- the full operational playbook: pre-quarter homework + kickoff brief template, kickoff / mid-quarter / close agendas, the weekly Wodtke rhythm scripts, anti-patterns, artifacts-produced map, troubleshooting, and success criteria. Read this when running any phase of the cycle.
  • references/quarterly-planning-guide.md -- the framework theory (Wodtke Radical Focus, Cagan product strategy, strategy cycle, RAD ritual) with a worked Reconcile Q3 example. Read this when you need the reasoning behind the rituals.
  • references/red-flags.md -- 11 quarterly-planning anti-patterns (OKR theater, capacity in story points, stretch goals as committed slate) with symptoms and fixes. Read this when reviewing a quarter's plan or diagnosing a failing cadence.

Templates live in assets/: kickoff_agenda_template.md, mid_quarter_check_in_template.md, close_retro_template.md, quarterly_review_deck_outline.md.

Scope & Limitations

In scope: pre-quarter homework (strategy, outcomes, capacity); kickoff agenda; weekly Wodtke rhythm; biweekly KR confidence review; mid-quarter check-in; close retro; carry/kill/pivot framework; quarterly review deck outline.

Out of scope: writing individual OKRs (execution/brainstorm-okrs/); roadmap construction (execution/outcome-roadmap/); sprint-level planning (scrum-master/); multi-quarter / annual strategy (c-level-advisor/); performance management (career/); portfolio management (program-manager/).

Caveats: the cycle is the system -- skipping one ritual (especially the close retro) degrades the next quarter; OKRs are a tool for focus, not control (Wodtke argues one Objective per team per quarter); the skill assumes a 13-week quarter; it works best where the company has shared OKR practice.

Integration Points

IntegrationDirectionWhat Flows
execution/brainstorm-okrs/BidirectionalQuarterly cycle uses OKRs; OKR drafting is a kickoff sub-skill
execution/outcome-roadmap/BidirectionalQuarterly OKRs become Now-horizon roadmap; roadmap themes inform candidate outcomes
execution/north-star-metric/Receives fromNSM is the long-term metric; quarterly KRs are short-term moves on it
execution/product-vision/Receives fromEvery Objective must trace to a vision pillar
execution/dependency-map/Receives fromPre-quarter dependency mapping prevents week-6 surprises
execution/status-update-generator/Feeds intoWeekly Wodtke rhythm produces input for exec status updates
execution/cycle-time-analyzer/Receives fromFlow metrics inform capacity assessment
discovery/customer-interview-script/Receives fromRecent customer signal feeds the strategy review
discovery/jtbd-workshop/Receives fromTop desired outcomes seed the outcome candidate list
scrum-master/Feeds intoQuarterly OKRs cascade into sprint capacity planning
senior-pm/Feeds intoQuarterly artifacts inform portfolio-level reporting
career/pm-onboarding/ComplementaryNew PMs use this skill in their 30-60-90 plan to ramp on team cadence

© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 8 other files (references, assets) in project-management/execution/quarterly-planning of borghei/Claude-Skills.

  • SKILL.md
  • assets/close_retro_template.md
  • assets/kickoff_agenda_template.md
  • assets/mid_quarter_check_in_template.md
  • assets/quarterly_review_deck_outline.md
  • examples/northwind-q4-planning-cycle.md
  • references/cycle-playbook.md
  • references/quarterly-planning-guide.md
  • references/red-flags.md

Open the folder on GitHubat commit 4a698e8

Compare with similar skills

Quarterly Planning next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Quarterly Planning compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Quarterly Planning this skillborghei/Claude-Skills886—~1.8kAutomated safety check: PassMIT
Product Strategistalirezarezvani/claude-skills28k2 repos~1.8kAutomated safety check: PassMIT
Roadmap Planningrampstackco/claude-skills941—~2.7kAutomated safety check: PassMIT
Roadmap Planningmanager-dot-dev/manager-skills114—~4.9kAutomated safety check: PassMIT
SEO Roadmap Prioritizationhashgraph-online/awesome-codex-plugins1.3k—~559Automated safety check: PassMIT
Prioritizemenkesu/awesome-pm-skills433—~4.6kAutomated safety check: PassCustom licence

Similar skills

  • Product Strategist

    alirezarezvani/claude-skills

    OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.

    28k GitHub starsUsed in 2 repos~1.8k tokens
    Product & Project ManagementAuto-check passed
  • Roadmap Planning

    rampstackco/claude-skills

    Build a multi-quarter roadmap from a backlog of ideas, requests, and ongoing initiatives.

    941 GitHub stars~2.7k tokensUpdated 2 days ago
    Product & Project ManagementAuto-check passed
  • Roadmap Planning

    manager-dot-dev/manager-skills

    Helps engineering managers plan roadmaps, prioritize work, and communicate priorities effectively — produces the 20% tech debt framework (and its 5 traps), a phased release pressure-test, a…

    114 GitHub stars~4.9k tokensUpdated 5 mo ago
    Product & Project ManagementAuto-check passed
  • SEO Roadmap Prioritization

    hashgraph-online/awesome-codex-plugins

    Prioritize SEO initiatives as product roadmap work with impact, effort, confidence, resourcing, executive pitch, cross-functional ownership, quarterly planning, and business KPI alignment.

    1.3k GitHub stars~559 tokensUpdated today
    Product & Project ManagementAuto-check passed
  • Prioritize

    menkesu/awesome-pm-skills

    Turns a pile of ideas, requests and goals into a confidence-scored roadmap plus a goals/OKR set the team can actually follow.

    433 GitHub stars~4.6k tokensUpdated 3 days ago
    Business, Finance & HRAuto-check passed
  • Team OKR Brainstorm

    phuryn/pm-skills

    Drafts three alternative sets of team OKRs, each with an inspiring objective and measurable key results, tied to the company strategy you provide.

    27k GitHub stars~1.1k tokensUpdated 25 days ago
    Product & Project ManagementAuto-check passed

More from borghei/Claude-Skills

All 354 skills in this repo
  • Agent Harness

    borghei/Claude-Skills

    Test and evaluation harness for AI agents — scenario suites, deterministic replay, regression diffing, cost and latency budgets.

    886 GitHub stars~3.1k tokensUpdated 2 days ago
    Auto-check passed
  • Agents In The Team

    borghei/Claude-Skills

    Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.

    886 GitHub stars~4.2k tokensUpdated 2 days ago
    Auto-check passed
  • AI Content Disclosure

    borghei/Claude-Skills

    Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.

    886 GitHub stars~3.4k tokensUpdated 2 days ago
    Auto-check passed
  • AI Prototyping

    borghei/Claude-Skills

    Idea to AI-generated prototype to customer validation to engineering handoff.

    886 GitHub stars~3.6k tokensUpdated 2 days ago
    Auto-check passed
  • Analytics Engineer

    borghei/Claude-Skills

    Analytics engineering across data modeling, dbt, transformation, and semantic layers.

    886 GitHub stars~3.4k tokensUpdated 2 days ago
    Auto-check passed
  • Ansoff Matrix

    borghei/Claude-Skills

    Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.

    886 GitHub stars~2.2k tokensUpdated 2 days ago
    Auto-check passed

Questions about Quarterly Planning

What does Quarterly Planning do?

Run the full quarterly planning cycle -- pre-quarter homework, kickoff, weekly Wodtke rhythm, mid-quarter check-in, and close retro -- using Radical Focus, Cagan strategy, and a fixed planning…. Quarterly Planning is an agent skill from borghei/Claude-Skills. Run the full quarterly planning cycle -- pre-quarter homework, kickoff, weekly Wodtke rhythm, mid-quarter check-in, and close retro -- using Radical Focus, Cagan strategy, and a fixed planning cadence around your OKRs.

When should I use Quarterly Planning?

Quarterly Planning fits situations like: tasks that involve Product roadmapping; tasks that involve OKRs and executive reporting.

How do I install Quarterly Planning in Claude Code?

Run `npx skills add borghei/Claude-Skills --skill quarterly-planning -a claude-code`. Or copy the skill folder (project-management/execution/quarterly-planning in borghei/Claude-Skills) into .claude/skills/quarterly-planning in your project. Claude Code loads it when a task matches its description.

How do I install Quarterly Planning in Codex?

Run `npx skills add borghei/Claude-Skills --skill quarterly-planning -a codex`. Or copy the skill folder (project-management/execution/quarterly-planning in borghei/Claude-Skills) into .agents/skills/quarterly-planning in your project. Codex loads it when a task matches its description.

Can I use Quarterly Planning in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill quarterly-planning -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/quarterly-planning, .gemini/skills/quarterly-planning, .github/skills/quarterly-planning and .opencode/skills/quarterly-planning in your project.

What does Quarterly Planning need to run?

SKILL.md names no scripts, command-line tools or credentials: Quarterly Planning is instructions for the agent only.

Does Quarterly Planning access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Quarterly Planning safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Quarterly Planning use?

Quarterly Planning is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Quarterly Planning use?

About 1.8k tokens (SKILL.md is roughly 7.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 10k tokens, read only when the agent opens those files.

What are the alternatives to Quarterly Planning?

Skills that share tags, products or a category with Quarterly Planning: Product Strategist (alirezarezvani/claude-skills, 28k stars), Roadmap Planning (rampstackco/claude-skills, 941 stars), Roadmap Planning (manager-dot-dev/manager-skills, 114 stars) and SEO Roadmap Prioritization (hashgraph-online/awesome-codex-plugins, 1.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Quarterly Planning?

borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 886 GitHub stars. The repository holds 354 skills in this directory. The repository was last updated on October 7, 2026.

Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.