Quarterly Planning
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 the Reforge cycle around your OKRs.
How to Use
Try in Chat
QuickPaste into any AI chat for instant expertise. Works in one conversation -- no setup needed.
Preview prompt
You are an expert Quarterly Planning (Project Management domain). 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 the Reforge cycle around your OKRs. 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 ## How to Help When the user asks for help in this domain: 1. Ask clarifying questions to understand their context 2. Apply the relevant framework or workflow from your expertise 3. Provide actionable, specific output (not generic advice) 4. Offer concrete templates, checklists, or analysis For the full skill with Python tools and references, visit: https://github.com/borghei/Claude-Skills/tree/main/quarterly-planning --- Start by asking the user what they need help with.
Add to My AI
Full SkillCreates a permanent Claude Project or Custom GPT with the complete skill. The AI will guide you through setup step by step.
Preview prompt
# Create a "Quarterly Planning" AI Skill I want you to help me set up a reusable AI skill that I can use in future conversations. Read the complete skill definition below, then help me install it. ## Complete Skill Definition # 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), Reforge's product strategy cycle, 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 +--Reforge/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. ## References Load the reference that matches the task -- keep this file lean and pull detail on demand: - **[references/cycle-playbook.md](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](references/quarterly-planning-guide.md)** -- the framework theory (Wodtke Radical Focus, Cagan product strategy, Reforge cycle, RAD ritual) with a worked Reconcile Q3 example. Read this when you need the reasoning behind the rituals. - **[references/red-flags.md](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 | Integration | Direction | What Flows | |-------------|-----------|------------| | `execution/brainstorm-okrs/` | Bidirectional | Quarterly cycle uses OKRs; OKR drafting is a kickoff sub-skill | | `execution/outcome-roadmap/` | Bidirectional | Quarterly OKRs become Now-horizon roadmap; roadmap themes inform candidate outcomes | | `execution/north-star-metric/` | Receives from | NSM is the long-term metric; quarterly KRs are short-term moves on it | | `execution/product-vision/` | Receives from | Every Objective must trace to a vision pillar | | `execution/dependency-map/` | Receives from | Pre-quarter dependency mapping prevents week-6 surprises | | `execution/status-update-generator/` | Feeds into | Weekly Wodtke rhythm produces input for exec status updates | | `execution/cycle-time-analyzer/` | Receives from | Flow metrics inform capacity assessment | | `discovery/customer-interview-script/` | Receives from | Recent customer signal feeds the strategy review | | `discovery/jtbd-workshop/` | Receives from | Top desired outcomes seed the outcome candidate list | | `scrum-master/` | Feeds into | Quarterly OKRs cascade into sprint capacity planning | | `senior-pm/` | Feeds into | Quarterly artifacts inform portfolio-level reporting | | `career/pm-onboarding/` | Complementary | New PMs use this skill in their 30-60-90 plan to ramp on team cadence | --- ## What I Need You to Do First, detect which platform I'm using (Claude.ai, ChatGPT, etc.) and follow the matching instructions below. ### If I'm on Claude.ai: Walk me through these exact steps: 1. **Create the Project:** Tell me to go to **claude.ai > Projects > Create project** and name it **"Quarterly Planning"** 2. **Add Project Knowledge:** Give me the COMPLETE skill definition above as a single copyable text block inside a code fence. Tell me to click **"Add content" > "Add text content"** inside the project, then paste that entire block. Do NOT say "paste from above" -- give me the actual text to copy right there. 3. **Set Custom Instructions:** Tell me to open project settings and paste this exact instruction: "You are an expert Quarterly Planning in the Project Management domain. Use the project knowledge as your expertise. Follow the workflows, frameworks, and templates defined there. Always provide specific, actionable output." 4. **Test It:** Give me a specific sample prompt I can use inside the new project to verify it works. Pick a real task from the skill's workflows. ### If I'm on ChatGPT: Walk me through these exact steps: 1. **Create a Custom GPT:** Tell me to go to **chatgpt.com > Explore GPTs > Create** 2. **Configure it:** - 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 the Reforge cycle around your OKRs." - Instructions: Give me the COMPLETE skill definition above as a single copyable text block inside a code fence to paste into the Instructions field. Do NOT say "paste from above." 3. **Test It:** Give me a sample prompt to verify it works. ### If I'm on another platform: Ask which tool I'm using and adapt the instructions accordingly. ## Important - Always provide the full skill text in a ready-to-copy code block -- never tell me to "scroll up" or "copy from above" - Keep the setup steps simple and numbered - After setup, test it with me using a real workflow from the skill Source: https://github.com/borghei/Claude-Skills/tree/main/project-management/execution/quarterly-planning/SKILL.md
# Add to your project
cs install project-management/execution/quarterly-planning ./
# Or copy directly
git clone https://github.com/borghei/Claude-Skills.git
cp -r Claude-Skills/project-management/execution/quarterly-planning your-project/
# The skill is available in your Codex workspace at:
.codex/skills/quarterly-planning/
# Reference the SKILL.md in your Codex instructions
# or copy it into your project:
cp -r .codex/skills/quarterly-planning your-project/
# The skill is available in your Gemini CLI workspace at:
.gemini/skills/quarterly-planning/
# Reference the SKILL.md in your Gemini instructions
# or copy it into your project:
cp -r .gemini/skills/quarterly-planning your-project/
# Add to your .cursorrules or workspace settings:
# Reference: project-management/execution/quarterly-planning/SKILL.md
# Or copy the skill folder into your project:
git clone https://github.com/borghei/Claude-Skills.git
cp -r Claude-Skills/project-management/execution/quarterly-planning your-project/
# Clone and copy
git clone https://github.com/borghei/Claude-Skills.git
cp -r Claude-Skills/project-management/execution/quarterly-planning your-project/
# Or download just this skill
curl -sL https://github.com/borghei/Claude-Skills/archive/main.tar.gz | tar xz --strip=1 Claude-Skills-main/project-management/execution/quarterly-planning