
Brainstorm Okrs
- 2k installs
- 24.9k repo stars
- Updated July 3, 2026
- phuryn/pm-skills
brainstorm-okrs is an agent skill for "Brainstorm team-level OKRs aligned with company objectives - qualitative objectives with measurable key results. Use
About
The brainstorm-okrs skill "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." It covers objective Why, What, When : Qualitative, inspirational, time-bound goal. Typically quarterly. Should be SMART.. Key workflows include key Results How much : Quantitative metrics typically 3 and their expected values.. Developers invoke brainstorm-okrs when the task matches the triggers and reference files in SKILL.md for grounded, stepwise execution. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation.
- 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.
- Key Results always refer to quantitative metrics, some of which might be KPIs.
- North Star Metric = a single, customer-centric KPI. A leading indicator of business success. You can use Key Results to
- Understand the Framework : OKRs have two components:
Brainstorm Okrs by the numbers
- 2,008 all-time installs (skills.sh)
- +82 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #237 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
brainstorm-okrs capabilities & compatibility
- Capabilities
- objective why, what, when : qualitative, inspira · key results how much : quantitative metrics typi · key results always refer to quantitative metrics · north star metric = a single, customer centric k · understand the framework : okrs have two compone
- Use cases
- documentation
npx skills add https://github.com/phuryn/pm-skills --skill brainstorm-okrsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2k |
|---|---|
| repo stars | ★ 24.9k |
| Security audit | 2 / 3 scanners passed |
| Last updated | July 3, 2026 |
| Repository | phuryn/pm-skills ↗ |
What problem does brainstorm-okrs solve for developers using the documented workflows?
"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
Who is it for?
Developers working with brainstorm-okrs patterns described in the skill documentation.
Skip if: Skip when docs are empty or the task is outside the skill documented scope.
When should I use this skill?
Use when "Brainstorm team-level OKRs aligned with company objectives - qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with compan
What you get
Actionable brainstorm-okrs guidance grounded in SKILL.md workflows and reference files.
- Three alternative OKR draft sets
By the numbers
- Generates 3 alternative team OKR sets per invocation
Files
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 minutes6. 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
Related skills
How it compares
Pick brainstorm-okrs over blank OKR templates when you need three strategic alternatives with measurable key results before quarterly commitment.
FAQ
Who is brainstorm-okrs for?
Developers and software engineers working with brainstorm-okrs patterns described in the skill documentation.
When should I use brainstorm-okrs?
When "Brainstorm team-level OKRs aligned with company objectives - qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with compan.
Is brainstorm-okrs safe to install?
Review the Security Audits panel on this page before installing in production.