plan-okrs — Claude Code command: team OKR brainstorming
plan-okrs generates three OKR sets that connect team goals to company strategy. Each OKR pairs a qualitative objective with three to five measurable key results.
MIT ★ 28,211 updated 2026-10-16
/plugin marketplace add phuryn/pm-skills
/plugin install pm-execution@pm-skillsWhat plan-okrs does
The command asks for context: which team, what time frame, what company-level goals matter, what worked or failed last quarter. It accepts strategy documents or existing OKR files as uploads.
Then it produces three OKR sets in table format—objective, baseline, target, owner—and validates each key result for measurability and resistance to gaming (e.g., favours outcome-focused metrics over shipping counters). It offers to adjust ambition levels, build a tracking dashboard, or draft a stakeholder brief.
OKRs work best when they describe outcomes, not actions: “increase activation by 20%” rather than “redesign onboarding”. Most teams stay focused with three objectives per quarter; more dilutes effort.
What it helps with
- draft team OKRs for a quarter tied to company strategy
- create key results that measure outcomes and resist manipulation
- assess OKR quality before presenting to leadership
- set up metrics for weekly progress tracking against targets
Example prompts for the agent
- Create OKRs for the growth team this quarter — company goal is 50% ARR increase
- Generate three OKRs for onboarding aligned to improving activation rate
- Score these OKRs and suggest ways to tighten the key results
How to install plan-okrs
1Plugin marketplace
/plugin marketplace add phuryn/pm-skills/plugin install pm-execution@pm-skills2Manually: put the files in place
.claude/commands/plan-okrs.mdCall it with /plan-okrs. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/plan-okrs.mdCall it with /prompts:plan-okrs. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/plan-okrs.prompt.mdManually: put the files in place
.gemini/commands/plan-okrs.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about plan-okrs
How do I install plan-okrs in Claude Code?
Run /plugin marketplace add phuryn/pm-skills, then /plugin install pm-execution@pm-skills. The command is then available as /plan-okrs.
What does plan-okrs do?
It generates three OKR sets for your team, each with a qualitative objective and three to five measurable key results. The command gathers context about your team, company strategy, and prior quarter, then builds a table with owners, baselines, and targets.
What is the difference between an objective and a key result?
An objective is a qualitative, inspiring statement that rallies the team. A key result is a specific, measurable metric with a target and a clear deadline. Together they show what success looks like and how you will know when you have achieved it.
Source text
plan-okrs.md · MIT
---
description: Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results
argument-hint: "<team, product area, or company objective>"
---
# /plan-okrs -- Team OKR Planning
Generate well-structured OKRs that connect team work to company strategy. Produces 3 OKR sets with qualitative objectives and quantitative key results.
## Invocation
```
/plan-okrs Growth team Q2 — company goal is 50% ARR increase
/plan-okrs Onboarding squad aligned to "improve activation rate"
/plan-okrs [upload company OKRs or strategy doc]
```
## Workflow
### Step 1: Gather Context
Ask the user:
- What team or product area are these OKRs for?
- What time period? (quarterly is standard, but could be annual or custom)
- What are the company-level objectives these should ladder up to?
- What happened last quarter? (hits, misses, learnings)
- Any constraints or known priorities?
Accept company OKRs or strategy documents as uploads.
### Step 2: Generate OKRs
Apply the **brainstorm-okrs** skill:
- Create 3 OKR sets (Objective + 3-5 Key Results each)
- **Objectives**: Qualitative, inspiring, ambitious but achievable, action-oriented
- **Key Results**: Quantitative, measurable, time-bound, have clear owners
- Ensure OKRs ladder to company objectives with visible connection
- Balance leading indicators (activity) with lagging indicators (outcomes)
### Step 3: Validate Quality
Check each OKR against best practices:
- Is the Objective inspiring? (Would you rally a team around it?)
- Are Key Results measurable? (Can you check completion with data, not judgment?)
- Are targets ambitious but not demoralizing? (70% achievement = well-calibrated)
- Are there 3-5 KRs per Objective? (More = unfocused)
- Do KRs avoid gaming? (e.g., "ship 5 features" incentivizes shipping junk)
Flag any issues and suggest improvements.
### Step 4: Present and Iterate
```
## Team OKRs: [Team Name] — [Period]
**Aligned to**: [Company Objective(s)]
### Objective 1: [Inspiring qualitative statement]
| # | Key Result | Baseline | Target | Owner |
|---|-----------|----------|--------|-------|
| KR1 | [measurable result] | [current] | [target] | [team/person] |
| KR2 | ... | ... | ... | ... |
| KR3 | ... | ... | ... | ... |
### Objective 2: [Inspiring qualitative statement]
[same format]
### Objective 3: [Inspiring qualitative statement]
[same format]
### Alignment Map
Company Objective → Team Objective → Key Results → Expected Impact
### Scoring Guide
- 0.0-0.3: Significant miss — investigate and learn
- 0.4-0.6: Progress made but fell short
- 0.7-0.9: Well-calibrated stretch goal — this is the target zone
- 1.0: Either nailed it or target wasn't ambitious enough
### Check-in Cadence
- **Weekly**: Quick traffic-light update on each KR
- **Mid-quarter**: Deep review, adjust targets if context changed
- **End of quarter**: Score, reflect, feed into next quarter
```
Offer:
- "Want me to **adjust ambition levels** — make them more/less aggressive?"
- "Should I **create a metrics dashboard** for tracking these?"
- "Want me to **draft a stakeholder update** introducing these OKRs?"
## Notes
- OKRs should describe outcomes, not outputs ("Increase activation by 20%" not "Ship onboarding redesign")
- If the user doesn't have company OKRs, help them derive team objectives from product strategy or business goals
- Maximum 3 objectives per team per quarter — more means less focus
- Key Results should be stretch goals — if you're certain you'll hit them, they're not ambitious enough
- Flag any KR that could be gamed and suggest a counter-metric
© Paweł Huryn · MIT · phuryn/pm-skills