Agent skill

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.

Stars 9,823
Forks 1,082

Install this agent skill to your Project

npx add-skill https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/brainstorm-okrs

SKILL.md

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

Expand your agent's capabilities with these related and highly-rated skills.

phuryn/pm-skills

ab-test-analysis

Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.

9,823 1,082
Explore
phuryn/pm-skills

cohort-analysis

Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.

9,823 1,082
Explore
phuryn/pm-skills

sql-queries

Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects. Reads database schemas from uploaded diagrams or documentation. Use when writing SQL, building data reports, exploring databases, or translating business questions into queries.

9,823 1,082
Explore
phuryn/pm-skills

swot-analysis

Perform a detailed SWOT analysis — strengths, weaknesses, opportunities, and threats with actionable recommendations. Use when doing strategic assessment, competitive analysis, or evaluating a product or business position.

9,823 1,082
Explore
phuryn/pm-skills

product-strategy

Create a comprehensive product strategy using the 9-section Product Strategy Canvas — vision, segments, costs, value propositions, trade-offs, metrics, growth, capabilities, and defensibility. Use when building a product strategy, creating a strategic plan, or defining product direction.

9,823 1,082
Explore
phuryn/pm-skills

pricing-strategy

Analyze and design pricing strategies including pricing models, competitive pricing analysis, willingness-to-pay estimation, and price elasticity. Use when setting prices, evaluating pricing models, preparing for a pricing change, or comparing freemium vs paid approaches.

9,823 1,082
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results