Use when asked to "set OKRs", "objectives and key results", "quarterly OKR planning", "align objectives", "measure OKR progress", or "focus priorities with OKRs".
Use when asked to "set OKRs", "objectives and key results", "quarterly OKR planning", "align objectives", "measure OKR progress", or "focus priorities with OKRs".
Helps teams focus on what matters most and create a cadence of progress.
The OKR framework (originated by Andy Grove at Intel, popularized by John Doerr at Google) creates alignment, focus, and learning cycles.
Christina Wodtke's Radical Focus approach emphasizes simplicity and avoiding common pitfalls.
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Claude CodeNot declared
CursorNot declared
CodexNot declared
GitHub CopilotNot declared
WindsurfNot declared
Gemini CLINot declared
ClineNot declared
OpenCodeNot declared
Repository health
Stars20
LicenseLICENSE
Default branchmain
Open issues0
Status
Active
Package contents
Files included with this skill beyond the listing page.
skill mdSKILL.md4,820 B
docsSUMMARY.md479 B
History
First seen on skills.sh
First recorded snapshot · 49 installs
SKILL.md
OKRs (Objectives and Key Results)
What It Is
OKRs are a goal-setting framework that creates focus, alignment, and a learning cycle for teams and organizations. The core insight: set one ambitious objective per quarter with 2-3 measurable key results, then check in weekly to maintain focus.
The key shift: Move from tracking activities ("What are we doing?") to tracking outcomes ("What progress are we making toward our goals?").
OKRs are a vitamin, not a medicine. They supercharge companies that already have their fundamentals in place (strategy, empowered teams, psychological safety). They won't fix broken organizations - they'll just reveal what's broken.
Credit: Originated by Andy Grove at Intel. Popularized by John Doerr who brought it to Google. Christina Wodtke's Radical Focus provides the most practical implementation guidance.
When to Use It
Use OKRs when you need to:
Focus the team on the single most important thing for the quarter
Align the organization so everyone knows what matters most
Create accountability with measurable outcomes (not just activities)
Build a learning cycle through weekly check-ins and quarterly retrospectives
Scale leadership so founders/executives don't need to micromanage
Accelerate progress by avoiding the "peanut butter" problem of spreading effort too thin
When Not to Use It
You don't have a clear strategy (OKRs reveal missing strategy, they don't replace it)
Your company lacks psychological safety (people will sandbag or game the metrics)
You want to track ALL the work (OKRs are for priorities, not comprehensive task lists)
Teams aren't empowered to decide HOW to achieve outcomes
Patterns
Detailed examples showing how to apply OKRs correctly. Each pattern shows a common mistake and the correct approach.
Critical (get these wrong and you've wasted your time)