Install any skill in seconds. Free to start, no credit card required.
Get Started Free →borghei/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.
Passed 18 of 22 test cases with the skill, and 9 of 22 without it.
and 9 more in the full report
11 fixed7 passed either way2 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
I want to start preparing our quarterly planning deliverables. We haven't defined our team capacity, existing strategy, or current cycle week. How many clarifying questions should be asked before proceeding?
| Checked | Without skill | With skill |
|---|---|---|
| Limits clarifying questions to 2 or 3 essential inputs. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
Before running a phase, confirm these inputs. If any is unknown or vague, ASK — do not assume:
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.
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 --+
test cases passed, vs 9 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.