brainstorm-okrs — Claude Code skill: generate team OKRs
Skill generates three sets of ambitious quarterly OKRs for your team, aligned with company strategy. Each set includes a qualitative objective, measurable key results, and rationale for team discussion.
npx skills add phuryn/pm-skills --skill brainstorm-okrs -a claude-codeWhat brainstorm-okrs does
The skill acts as an experienced product leader who understands the difference between inspirational goals and measurable outcomes. You describe what your team works on; the skill reads company context (if you attach docs or strategy) and proposes three complete OKR sets. Each includes a qualitative objective, exactly three quantitative key results with targets, and why it matters.
The logic is grounded in OKR theory: distinguishing them from KPIs and North Star metrics without conflating them. The skill steers toward outcome-focused goals, not output (e.g., reduce time-to-value instead of ship five features). All three options are equally credible — starting points for strategy conversation, not a ranked list.
For larger outputs, the skill saves results to a markdown file named OKRs-[team-name]-[quarter].md. Use it at the start of a quarter, when aligning goals for a new team, or to clarify how local work connects to company strategy.
What it helps with
- Generate three OKR options for a team aligned with company strategy
- Distinguish a measurable key result from a vague aspiration
- Connect team goals to business metrics and North Star
- Formulate an ambitious yet achievable quarterly objective
- Discuss OKR variants with your team and decide direction
Example prompts for the agent
- Help me draft OKRs for the product team next quarter. Here's our company strategy (paste doc or summary)
- Create three OKR sets for the backend team working on API reliability. The company is prioritizing scalability and uptime
- What OKRs make sense for the newly formed analytics team? Here's our North Star metric
How to install brainstorm-okrs
1Skills CLI (Vercel)
npx skills add phuryn/pm-skills --skill brainstorm-okrs -a claude-code2Manually: put the files in place
~/.claude/skills/brainstorm-okrs/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/brainstorm-okrs/
1Skills CLI (Vercel)
npx skills add phuryn/pm-skills --skill brainstorm-okrs -a codex2Manually: put the files in place
.agents/skills/brainstorm-okrs/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add phuryn/pm-skills --skill brainstorm-okrs -a cursor2Manually: put the files in place
.cursor/skills/brainstorm-okrs/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install phuryn/pm-skills brainstorm-okrs2Manually: put the files in place
.github/skills/brainstorm-okrs/SKILL.md1Skills CLI (Vercel)
npx skills add phuryn/pm-skills --skill brainstorm-okrs -a gemini-cli2Platform CLI
gemini skills install https://github.com/phuryn/pm-skills --path pm-execution/skills/brainstorm-okrsManually: put the files in place
.devin/skills/brainstorm-okrs/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add phuryn/pm-skills --skill brainstorm-okrs -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set61
The whole set →Similar
Questions about brainstorm-okrs
How do I install brainstorm-okrs in Claude Code?
Run two commands in order: npx skills add phuryn/pm-skills --skill brainstorm-okrs -a claude-code, then open ~/.claude/skills/brainstorm-okrs/SKILL.md to verify the installation.
What does brainstorm-okrs do?
The skill generates three OKR options (objectives with key results) for your team, aligned with company strategy. Each option includes a qualitative objective, three measurable key results with targets, and rationale.
How do OKRs relate to KPIs and North Star metrics?
OKRs are quarterly goals with quantitative progress metrics. KPIs are key metrics tracked longer-term; some become key results or health metrics. North Star is a single customer-centric metric; you can set key results to track its change.
Source text
SKILL.md · MIT
---
name: brainstorm-okrs
description: "Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs."
---
# Brainstorm Team OKRs
## Purpose
You are a veteran product leader responsible for defining Objectives and Key Results (OKRs) for the team working on $ARGUMENTS. Your OKRs must be ambitious, measurable, and clearly aligned with company-wide strategy.
## Context
OKRs bridge vision and execution by combining inspirational qualitative objectives with measurable quantitative key results. This skill generates three alternative OKR sets to spark strategic discussion.
## Domain Context
**OKR** (Christina Wodtke, *Radical Focus*):
- **Objective** (Why, What, When): Qualitative, inspirational, time-bound goal. Typically quarterly. Should be SMART.
- **Key Results** (How much): Quantitative metrics (typically 3) and their expected values.
**OKRs, KPIs, and NSM are interconnected — not alternatives.** Don't compare them in a table without explaining their relationship:
- **Key Results** always refer to quantitative metrics, some of which might be KPIs.
- **KPIs** = a few key quantitative metrics tracked over a longer period. Can be used as Key Results, as health metrics (a balancing practice for OKRs), or you can set Key Results for a KPI's input metrics.
- **North Star Metric** = a single, customer-centric KPI. A leading indicator of business success. You can use Key Results to express expected change in NSM.
OKRs are fundamentally about: (1) Setting a single, inspiring goal. (2) Empowering a team to determine the optimal approach. (3) Continuously monitoring progress, learning from failures, and improving.
## Instructions
1. **Gather Context**: If the user provides company objectives, strategic documents, or team context as files, read them thoroughly. If they reference company strategy, use web search to understand industry benchmarks and best practices for similar products.
2. **Understand the Framework**: OKRs have two components:
- **Objective**: A qualitative, inspirational goal describing the directional intent
- **Key Results**: 3 quantitative metrics (typically) measuring progress toward the objective
3. **Think Step by Step**:
- What is the company strategy?
- What are the 3-5 most impactful areas the team can influence?
- How do team efforts ladder up to company goals?
- What would success look like for customers and the business?
4. **Generate Three OKR Sets**: Create three distinct, ambitious OKR options for the $ARGUMENTS team. For each set:
- Start with a clear, inspiring Objective statement
- Define exactly 3 Key Results that are:
- Measurable (can be tracked numerically)
- Achievable but ambitious (60-70% confidence level)
- Aligned with company strategy
5. **Example Format**:
```
Objective: Delight new users with an effortless onboarding experience
Key Results:
- CSAT score >= 75% on onboarding survey
- 66%+ of onboardings completed within two days
- Average time-to-value (TTV) <= 20 minutes
```
6. **Structure Output**: Present all three OKR sets with equal weight. For each, include:
- Objective (1-2 sentences)
- Three Key Results (specific metrics with targets)
- Brief rationale (why this matters to the company and team)
7. **Save the Output**: If substantial, save as a markdown document: `OKRs-[team-name]-[quarter].md`
## Notes
- Ensure each Key Result is independently measurable
- Avoid output-focused metrics (e.g., "launch 5 features"); focus on outcomes
- All three OKR sets should be credible, not one clearly better than others
- Flag any assumptions about data availability
---
### Further Reading
- [Objectives and Key Results (OKRs) 101](https://www.productcompass.pm/p/okrs-101-advanced-techniques)
- [OKR vs KPI: What's the Difference?](https://www.productcompass.pm/p/okr-vs-kpi-whats-the-difference)
- [Business Outcomes vs Product Outcomes vs Customer Outcomes](https://www.productcompass.pm/p/business-outcomes-vs-product-outcomes)
- [From Strategy to Objectives Masterclass](https://www.productcompass.pm/p/product-vision-strategy-objectives-course) (video course)
© phuryn · MIT · phuryn/pm-skills