SkillVaultskills Browse all 1,000+ skills

Product Management · Version 1.1.0 · Reviewed 2026-08-02

OKR Quality Reviewer

Make a product decision about outcome orientation and measurability with evidence, explicit trade-offs, and a verification plan.

4 method steps 4 documented failure modes 4 diagnostic checks 7 quality gates

Reviews objectives and key results for measurability, outcome orientation, and honest ambition.

₹199 one-time

Get this skill archive

Install in your AI coding tool

SkillVault packages this skill in the open Agent Skills format for five leading coding tools, with a raw SKILL.md fallback for every other compatible IDE or agent.

See the complete graphical installation and usage guide

What this skill helps you do

  • Outcome orientation
  • Measurability
  • Ambition calibration

How OKR Quality Reviewer works

You provide

Customer evidence, constraints, and the decision at stake

It inspects

Problem versus requested solution in outcome orientation

It decides

A measurability decision ranking assumptions by risk

You verify

Success criteria and a reversal condition fixed up front

What it checks first

OKR Quality Reviewer reviews objectives and key results for measurability, outcome orientation, and honest ambition. Use it when the work involves Outcome orientation, Measurability, Ambition calibration.

  1. Whether the request describes a solution or the underlying problem and its frequency.
  2. The strength of evidence behind each assumption, and which assumption carries the most risk.
  3. Opportunity cost, since a roadmap decision is a decision not to do something else.
  4. Whether success criteria and a review date were defined before commitment.

Failure modes it recognizes

  • Request volume used as a proxy for impact, which favors the loudest segment.
  • A prioritization score presented as objective while its inputs are estimates.
  • An experiment readout interpreted without checking sample ratio or power.
  • Scope committed before the riskiest assumption has been tested.

Answers it will reject

  • Building the requested feature rather than solving the described problem.
  • Presenting a roadmap without the trade-off that made it necessary.
  • Declaring success from a metric that moved for an unrelated reason.

Decision rules it applies

  • Separate problem from proposed solution before evaluating anything.
  • Rank assumptions by risk and test the riskiest before committing scope.
  • State the success criteria and the reversal condition at decision time.

Evidence it asks for

  • Quantify frequency, severity, and affected segment for each problem.
  • Cite the specific evidence behind each assumption and label its strength.
  • Define the leading indicator that will show progress before the lagging metric moves.

The method inside

  1. Separate the customer problem from requested solutions
  2. Inventory assumptions and strength of evidence
  3. Compare options using impact, confidence, risk, effort, and reversibility
  4. Define success, guardrails, and the decision after new evidence

Deliverables

  • Outcome orientation evidence map
  • Measurability option and risk analysis
  • Ambition calibration decision memo

Evidence requirements

  • Customer research, usage, support, and commercial evidence
  • Strategy, constraints, dependencies, and opportunity cost
  • Experiment design, roadmap options, or requirements artifact

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

Review our quarterly OKRs. The team wrote them but they feel like a project list with numbers attached.

Expected output

That instinct is correct: these are outputs, so they can all be achieved without the business changing. Rewrite each key result as a change in customer or business behavior, and confirm each is measurable with data you already collect...

Boundaries and compatibility

Ideal for

  • Outcome orientation: produce a decision or artifact grounded in supplied evidence.
  • Measurability: produce a decision or artifact grounded in supplied evidence.
  • Ambition calibration: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Using request volume as a substitute for impact
  • Presenting a prioritization score as objective truth

Agent compatibility

  • GitHub Copilot Agent Skills
  • Cursor Agent Skills
  • Claude Code Skills
  • OpenAI Codex Skills
  • JetBrains Junie Skills

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.