okr-criticlisted
Install: claude install-skill RizwanZafaris/product-manager-OS
# OKR Critic: key results that could fail
An OKR sheet fails in three quiet ways: the key results are tasks, so the sheet scores 1.0 in a quarter the product went nowhere; the numbers have no baseline, so nobody can say what moved; or the team's sheet adds up to nothing the company asked for. This skill reads a draft the way a skeptical scorer will read it at period end, and fixes the lines before signature.
## Files this skill drives
- [../../templates/planning/okrs.md](../../templates/planning/okrs.md), where the accepted set lands with baselines, targets, owners, and guardrails
- [../../templates/planning/roadmap.md](../../templates/planning/roadmap.md), whose items must each name the key result they serve
- [../../templates/operate/metrics-review.md](../../templates/operate/metrics-review.md), where the period's scores are read at Gate 6
- Reads: [../../templates/planning/product-strategy.md](../../templates/planning/product-strategy.md) for the bets the objectives serve, and [../../templates/planning/north-star-metric.md](../../templates/planning/north-star-metric.md) for the tree the key results sit on
- Method background: [../../knowledge/okrs.md](../../knowledge/okrs.md) (Andy Grove, High Output Management, 1983; John Doerr, Measure What Matters, 2018); read the trap section first
## When to use
- Drafting OKRs for a quarter or a cycle, from a strategy and last period's scores
- Reviewing a team's draft before the sponsor signs it
- When the check-in log shows ev