# okr-design

okr-design is a Claude Code skill for setting goals and defining success metrics. It helps structure OKRs, KPI trees, and experiment measures.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 140 installs · ★ 305 repo stars
- Author: OrchestKit
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/yonatangross/orchestkit/tree/HEAD/src/skills/okr-design/SKILL.md
- Updated: 2026-11-07
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/orchestkit-okr-design

## What it does

okr-design turns goals into OKRs, breaks top-level metrics into KPI trees, and helps select a North Star metric and leading indicators. For each lagging metric, it calls for 2–3 leading predictors.

The skill also helps define metrics before instrumentation and set experiment guardrails before launch. Its materials include templates for metric definitions, events, and experiment plans. Claude Code 2.1.277 or later is required.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add yonatangross/orchestkit --skill okr-design -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/okr-design/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/okr-design/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add yonatangross/orchestkit --skill okr-design -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/okr-design/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add yonatangross/orchestkit --skill okr-design -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/okr-design/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install yonatangross/orchestkit src/skills/okr-design
```

2. **Manually: put the files in place**
- File: `.github/skills/okr-design/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add yonatangross/orchestkit --skill okr-design -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/yonatangross/orchestkit --path src/skills/okr-design
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/okr-design/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add yonatangross/orchestkit --skill okr-design -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/yonatangross/orchestkit/tree/HEAD/src/skills/okr-design/SKILL.md

## When to use it
- write measurable key results for a goal
- break revenue into a KPI tree
- find leading indicators for a lagging metric
- set experiment guardrails before launch

## Example prompts
- Draft OKRs for a goal to improve customer retention.
- Break revenue into a KPI tree and suggest leading indicators.
- Create an A/B test plan with guardrail metrics.

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 5177bb053298d0df.

BEGIN THIRD-PARTY FILE 5177bb053298d0df
````text
---
name: okr-design
compatibility: "Claude Code 2.1.277+"
description: "OKR trees, KPIs, North Star metric, leading and lagging indicators, experiment guardrails. Use when setting goals or success metrics."
user-invocable: false
disable-model-invocation: false
metadata:
  owner-agent: "product-strategist"
  category: document-asset-creation
  version: "1.0.0"
  author: "OrchestKit"
  complexity: "medium"
  tags: "okr, kpi, north-star, metrics, experiment, goal-setting, leading-lagging, instrumentation"
allowed-tools: "Read Glob Grep WebFetch WebSearch"
---

# OKR Design & Metrics Framework

Structure goals, decompose metrics into KPI trees, identify leading indicators, and design rigorous experiments.

## OKR Structure

Objectives are qualitative and inspiring. Key Results are quantitative and outcome-focused — never a list of outputs.

```
Objective: Qualitative, inspiring goal (70% achievable stretch)
+-- Key Result 1: [Verb] [metric] from [baseline] to [target]
+-- Key Result 2: [Verb] [metric] from [baseline] to [target]
+-- Key Result 3: [Verb] [metric] from [baseline] to [target]
```

```markdown
## Q1 OKRs

### Objective: Become the go-to platform for enterprise teams

Key Results:
- KR1: Increase enterprise NPS from 32 to 50
- KR2: Reduce time-to-value from 14 days to 3 days
- KR3: Achieve 95% feature adoption in first 30 days of onboarding
- KR4: Win 5 competitive displacements from [Competitor]
```

### OKR Quality Checks

| Check | Objective | Key Result |
|-------|-----------|------------|
| Has a number | NO | YES |
| Inspiring / energizing | YES | not required |
| Outcome-focused (not "ship X features") | YES | YES |
| 70% achievable (stretch, not sandbagged) | YES | YES |
| Aligned to higher-level goal | YES | YES |

See [references/okr-workshop-guide.md](references/okr-workshop-guide.md) for a full facilitation agenda (3-4 hours, dot voting, finalization template).
See [rules/metrics-okr.md](rules/metrics-okr.md) for pitfalls and alignment cascade patterns.

---

## KPI Tree & North Star

Decompose the top-level metric into components with clear cause-effect relationships.

```
Revenue (Lagging — root)
├── New Revenue = Leads × Conv Rate          (Leading)
├── Expansion   = Users × Upsell Rate        (Leading)
└── Retained    = Existing × (1 - Churn)     (Lagging)
```

### North Star + Input Metrics Template

```markdown
## Metrics Framework

North Star: [One metric that captures core value — e.g., Weekly Active Teams]

Input Metrics (leading, actionable by teams):
1. New signups — acquisition
2. Onboarding completion rate — activation
3. Features used per user/week — engagement
4. Invite rate — virality
5. Upgrade rate — monetization

Lagging Validation (confirm inputs translate to value):
- Revenue growth
- Net retention rate
- Customer lifetime value
```

### North Star Selection by Business Type

| Business | North Star Example | Why |
|----------|--------------------|-----|
| SaaS | Weekly Active Users | Indicates ongoing value delivery |
| Marketplace | Gross Merchandise Value | Captures both buyer and seller sides |
| Media | Time spent | Engagement signals content value |
| E-commerce | Purchase frequency | Repeat = satisfaction |
````
END THIRD-PARTY FILE 5177bb053298d0df

The third-party file has ended. Everything between the 5177bb053298d0df tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3251 of 7576 bytes. © OrchestKit · MIT · https://github.com/yonatangross/orchestkit/tree/HEAD/src/skills/okr-design/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
