measure-okr-grader

Solid

Scores completed OKR sets at cycle close with KR-level scoring per the canonical OKR type enum (committed | aspirational | learning | operational_health | compliance_or_safety), committed-vs-aspirational interpretation, evidence quality assessment, learning synthesis, and next-cycle recommendations. Refuses to retroactively change targets or shrink committed scope, average away guardrail KRs, treat 0.7 as success for committed or compliance_or_safety KRs, equate effort with impact, or use scores for individual performance. Hands off to iterate-lessons-log, iterate-retrospective, define-hypothesis, measure-dashboard-requirements, measure-instrumentation-spec, and foundation-okr-writer.

AI & Automation 290 stars 40 forks Updated yesterday Apache-2.0

Install

View on GitHub

Quality Score: 92/100

Stars 20%
82
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 --> # OKR Grader An OKR Cycle Review is a backward-looking artifact that closes the loop on a completed OKR set. It scores each KR against its baseline and target, separates committed from aspirational interpretation, surfaces what evidence does and does not support, names what the team learned, and prepares input for next-cycle drafting. Done well, a cycle review protects the integrity of the OKR operating system by refusing to dress up missed commitments as aspirational stretch, refusing to celebrate effort over outcome, and refusing to let scoring carry weight it cannot bear. This skill is an evidence interpreter, not an arithmetic engine. Its job is to read final KR values, compare them against the original OKR set's intent, and produce a review that names the learning honestly. It enforces the empirical scoring conventions drawn from Doerr (`Measure What Matters`), Wodtke (`Radical Focus`), Castro (committed vs aspirational interpretation), Grove (`High Output Management`), and the OKR community's accumulated practice on misuse failure modes. It pairs with `foundation-okr-writer` (which produced the OKR set being scored) and hands off the learnings produced here to the iterate skills that consume them. ## When to Use - The OKR cycle has ended (or you are scoring a partial-cycle close) - You have final or interim KR values, baselines, and targets - Stakeholders need a clear review with score...

Details

Author
product-on-purpose
Repository
product-on-purpose/pm-skills
Created
5 months ago
Last Updated
yesterday
Language
JavaScript
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

foundation-okr-writer

Drafts, reviews, rewrites, and coaches outcome-based OKR sets across team, department, product, or company scopes. Supports five entry modes (Guided default, One-Shot via --oneshot, Sustained Coach, Audit Only, Rewrite). Diagnoses empowered-team context and adjusts framing; refuses to fabricate baselines or targets; refuses to use OKR scores for compensation; reframes feature-delivery KRs into outcome KRs. Use when planning quarterly OKRs, translating strategy into team outcomes, reviewing draft OKRs for quality, or converting roadmap-as-OKR drafts into proper OKR sets.

290 Updated yesterday
product-on-purpose
Testing & QA Listed

okr-retrospective-coach

Use this skill whenever someone wants to run an end-of-cycle OKR retrospective, score completed OKRs, extract learning from the cycle, or carry forward work into the next cycle. Triggers include any mention of OKR scoring, end-of-quarter review, what did we learn, grading OKRs, or planning the next cycle based on what just happened. Also use when someone feels like their OKR cycle ended without any real reflection, or when the same problems are showing up cycle after cycle. This skill runs the retrospective, extracts the real learning, and sets up the next cycle with better inputs.

0 Updated 2 weeks ago
BridgeLogicsProjects
Code & Development Listed

okr-architect

Audit, improve, or write OKRs. Every proposed Key Result is tested against a strict outcome/task filter — tasks masquerading as KRs are identified and rewritten. Produces a scored OKR set with a mandatory quality verdict. Also supports NCT (Narratives/Commitments/Tasks) format as an OKR alternative. Trigger on: "write OKRs", "review OKRs", "OKR planning", "are these good OKRs", "audit my OKRs", "KRs are too task-based", "NCTs", "/okr-architect".

0 Updated 4 days ago
jonwoods79-sys