Back to Skills

setting-okrs-goals

Help users set effective OKRs and goals. Use when someone is creating quarterly objectives, defining key results, setting team goals, planning annual targets, or struggling with goal alignment across their organization.

1,097stars139forksUpdated 6/29/2026

Security Assessment

Safe(100/100)
Security Score100/100

About setting-okrs-goals

A coaching skill for setting effective OKRs and goals, drawing on frameworks and insights attributed to 55 product leaders. It is intended for situations like creating quarterly objectives, defining key results, setting team goals, planning annual targets, or untangling goal alignment across an organization. The help model is conversational: understand the user's context (company stage, team size, existing versus fresh goals), clarify the level (company, department, team, or individual), confirm a real strategy exists before goals are set, then guide the structure of inspiring objectives and measurable key results that avoid common pitfalls.

The guidance is organized around named core principles with concrete quotes. Goals should sit no more than one step from company goals to avoid cascading into oblivion; teams should build recurring default-on systems rather than fixating on one-time targets; OKRs bridge abstract strategy to concrete quarterly numbers with an end-of-quarter grading cycle. Christina Wodtke's triangulation pattern recommends three key results — a hardcore number, a squishier quality measure, and one with a dollar sign. Other principles warn that ratios and percentages can be gamed by shrinking the denominator (favoring absolute counts), that ambitious goals force working smarter rather than harder, that strategy discussions must be kept separate from OKR discussions, and that planning should consume no more than about ten percent of the execution period.

To apply these ideas the skill supplies ready-made coaching questions (for example, how a team goal connects to the company's primary goal, what specific number would change on success, and whether key results are outcomes or just a task list) and a checklist of common mistakes to flag, such as key results that are really tasks, having too many goals, vague objectives, goals set before strategy, and over-indexing on a single metric. A deep-dive reference (references/guest-insights.md) collects all 74 insights, and the doc lists related skills including writing North Star metrics, defining product vision, prioritizing roadmap, and stakeholder alignment.

FAQ

When should I use this skill?

When creating quarterly objectives, defining key results, setting team or annual goals, or working through goal alignment across an organization.

How many key results does it recommend per objective?

It cites Christina Wodtke's preference for three: one hardcore number, one squishier quality metric, and one involving a dollar sign, to balance quantitative, qualitative, and financial views.

Why does it warn against ratios and percentages?

Because ratios and percentages can be gamed by reducing the denominator. It recommends shifting to absolute numbers, such as the count of users reaching a specific state, instead of conversion rate.

Does it expect a strategy to exist before setting OKRs?

Yes. Goals should be the end of strategy, not the beginning, and it advises keeping strategy discussions separate from OKR discussions; without a real strategy, OKRs become false-precision exercises.

Where can I find the full set of expert insights?

All 74 insights from the 55 guests are collected in the references/guest-insights.md deep-dive file referenced by the skill.

All Files

2 files
references/guest-insights.md49.3 KB
View
SKILL.md5.0 KB
View

Install setting-okrs-goals

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill