Skip to main content
skill Claude Code CX Codex Cursor GitHub Copilot

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.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add phuryn/pm-skills --skill brainstorm-okrs -a claude-code
Open on GitHub

What 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-code

2Manually: put the files in place

~/.claude/skills/brainstorm-okrs/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/brainstorm-okrs/

From the same set61

The whole set →
create-prd phuryn This skill builds a lean PRD from an 8-section template. Use it to define a feature, document product requirements, or review an existing PRD. Claude Code CX Codex Cursor +1 10,800installs pre-mortem phuryn Runs a pre-mortem risk assessment on PRDs and launch plans. Catches critical launch blockers, surfaces hidden team assumptions, and maps action items. Claude Code CX Codex Cursor +1 10,200installs outcome-roadmap phuryn Rewrites feature-heavy roadmaps into outcome-focused statements tied to business and customer impact. Helps teams replace rigid feature lists with measurable strategic goals. Claude Code CX Codex Cursor +1 9,900installs prioritization-frameworks phuryn Reference guide to 9 prioritization frameworks: RICE, ICE, Opportunity Score, Kano, MoSCoW and more. Helps you pick the right method, compare approaches, and rank tasks by importance. Claude Code CX Codex Cursor +1 9,900installs strategy-red-team phuryn Stress-tests PRDs, roadmaps, and strategies by attacking load-bearing assumptions before reality does, returning kill criteria and cheap tests. Claude Code CX Codex Cursor +1 9,200installs competitor-analysis phuryn This skill researches direct competitors and compares their positioning, strengths, weaknesses, and pricing. Use it to prepare a competitive brief or find ways to differentiate a product. Claude Code CX Codex Cursor +1 3,800installs business-model phuryn Skill generates a Business Model Canvas with all 9 building blocks: from key partners and activities to channels and revenue streams. Use it to create a business model, document how value flows, or analyze an existing business. Claude Code CX Codex Cursor +1 3,700installs privacy-policy phuryn Skill drafts a detailed privacy policy accounting for GDPR, CCPA, and other regulations. Use it when building a new product, updating data protection docs, or preparing for compliance audits. Claude Code CX Codex Cursor +1 3,500installs

Similar

reference-list-builder Paramchoudhary This skill structures professional reference lists and drafts briefing materials for employment background checks. Claude Code CX Codex Cursor +1 9,300installs offer-comparison-analyzer Paramchoudhary This skill compares job offers by total compensation, work conditions, career prospects, and risk. Use it when you are choosing between multiple offers. Claude Code CX Codex Cursor +1 9,300installs apple-notes Hermes Agent Lets a coding agent read, search and write Apple Notes from the terminal through the memo CLI, with everything syncing over iCloud. Claude Code CX Codex Cursor +1 381installs airtable community Ready-made curl calls for Airtable's REST API: read records, filter with formulas, write in batches, upsert on a merge field. Claude Code CX Codex Cursor +1 375installs find-skills vercel-labs Discovers and installs agent skills from skills.sh directly inside your coding assistant. Handy when you need domain-specific workflows for a project. Claude Code CX Codex Cursor +1 4,000,000installs grill-me Matt Pocock grill-me interviews you about a plan or design to expose gaps and sharpen decisions. Use it before implementation starts. Claude Code 1,424,476installs grill-with-docs Matt Pocock This skill interviews you about a plan or design and creates ADRs and a glossary along the way. Use it when decisions need sharper definition. Claude Code 1,219,756installs handoff Matt Pocock Creates a handoff document from the current conversation so another agent can continue the work. Use it when a task moves to a new session or agent. Claude Code 1,038,491installs

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

See also

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor