
brainstorm-okrs
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.
- Installs
- 2.9K
- Last 24h
- +8
- Trending rank
- #9678
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/phuryn/pm-skills --skill brainstorm-okrs- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads brainstorm-okrs automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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
-
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.
-
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
-
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?
-
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
-
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 -
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)
-
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
FAQ
What does the brainstorm-okrs skill do?
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.
How do I install brainstorm-okrs?
Run npx skills add https://github.com/phuryn/pm-skills --skill brainstorm-okrs in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/brainstorm-okrs/ (personal) or .claude/skills/brainstorm-okrs/ (project).
Which AI agents can use brainstorm-okrs?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is brainstorm-okrs safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains brainstorm-okrs?
It is published by phuryn in phuryn/pm-skills. It has 2,906 recorded installs.
More from phuryn/pm-skills
create-prd
phuryn/pm-skills
Create a lean, decision-ready Product Requirements Document with an 8-section template: summary, contacts, background, objective, market segments, value propositions (6-part JTBD template), solution, and release. Lean by default (about one to two pages), with a fuller spec on request. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
pre-mortem
phuryn/pm-skills
Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go wrong.
prioritization-frameworks
phuryn/pm-skills
Reference guide to 9 prioritization frameworks with formulas, when-to-use guidance, and templates — RICE, ICE, Kano, MoSCoW, Opportunity Score, and more. Use when selecting a prioritization method, comparing frameworks like RICE vs ICE, or learning how different prioritization approaches work.
outcome-roadmap
phuryn/pm-skills
Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.
strategy-red-team
phuryn/pm-skills
Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.
competitor-analysis
phuryn/pm-skills
Analyze competitors with strengths, weaknesses, and differentiation opportunities. Identifies direct competitors and maps the competitive landscape. Use when doing competitive research, preparing a competitive brief, or finding differentiation opportunities.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.