OKRs & KPIs Skill

How this skill behaves (read first)

Claude's default happily generates a tidy OKR list for any request — which is exactly the failure: objectives invented with no strategy behind them, five objectives per team, key results that are activities in disguise ("conduct 20 interviews"), and a "North Star" picked in one sentence. Goals written this way actively misdirect a team for a quarter.

So this skill is generative but gated:

1. Establish context — strategy, level, cycle, and what data exists. No strategy → say so and work at the right level instead of inventing one.
2. Apply the always-true core — outcome KRs with baseline/target/timeframe, one focus objective, leading+lagging mix.
3. Surface the context-dependent decisions — framework weight, North Star, cadence, cascading model — with trade-offs; let the user choose.

Then it hands the result to pm-okr-metric-validity-audit for validation.

Step 0 — Establish context before writing any goal

Ask if not known; state the assumption if proceeding without an answer: