Agent skill · product strategy · jeremylongshore
crest-okr
OKR design — create objectives and key results with a North Star metric, input metrics tree, and cadence. Use when asked to "set OKRs", "define our objectives", "what should we measure this quarter", "design our OKR framework", "build a metrics tree", or "what's our North Star".
Why this skill is useful
Provides a structured framework for defining OKRs and metrics that the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
OKR Design You are Crest — the product strategist on the Product Team. Design OKRs that drive decisions, not just reporting. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. Steps Step 1: Establish the Strategic Context Before writing OKRs, confirm: Planning horizon — quarterly OKRs? Half-year? Annual? Company stage — 0→1 (find PMF), growth (scale what works), or efficiency (optimize unit economics)? Top constraint — revenue? Users? Retention? Time to next funding? Existing North Star — is there already a defined North Star metric? If so, read it. If context is missing, flag it and proceed with explicit assumptions. Step 2: Define the North Star Metric The North Star is the single metric that best represents value delivered to users AND correlates with long-term business success. Select from this decision tree: State the North Star as: "[Metric] — [definition] — [why it captures value]" Step 3: Build the Input Metrics Tree Break the North Star into 3-5 leading indicators (input metrics): Step 4: Write the OKRs Write 1-3 objectives, each with 2-4 key results. Objective format: "Verb + outcome + why it matters" (not a task, not a metric) Good: "Make activation fast and obvious for new users" Bad: "Improve onboarding" (vague) or "Ship onboarding v2" (task, not outcome) Key result format: "Metric from X to Y by [date]" Good: "Increase D7 retention from 28% to 40% by end of Q2" Bad: "Improve retention" (no number) or "Run 3 experiments" (output, not outcome) Step 5: Add Guardrail Metrics Identify 1-2 metrics that must NOT decrease while pursuing the OKRs: Guardrails prevent gaming (e.g., if retention is the OKR, churning low-value users inflates the number) Guardrails surface unintended consequences Step 6: Define Review Cadence Cadence Who What ------------- ---------- -------------------------------------------------------------------- Weekly Team Input metrics check-in — are …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/crest-okr