跳到正文
cccskills
免费在 GitHub 公开

brainstorm-okrs

Draft three alternative sets of team OKRs, pairing a qualitative goal with three measurable results. Use company strategy and team context to propose numerical targets, explain each option, and support discussions about quarterly priorities and customer or business outcomes.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

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.

查看安装方法

适用场景

  • Drafting quarterly team goals
  • Aligning team priorities with company strategy
  • Turning broad objectives into measurable results
  • Comparing three options in a goal-setting discussion

包含的文件(1)

  • SKILL.md4.2 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

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

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Analyze A/B test results to decide whether to launch a change, extend testing, stop, or investigate further. Check sample size, statistical significance, uncertainty ranges, and effects on other important metrics, then summarize the recommendation and next steps.

中文简介正在准备中。当前显示英语简介。

  • Checking whether an A/B test shows a meaningful difference
  • Reviewing sample size and test duration
  • Deciding whether to launch a tested change
phuryn/pm-skills2.7万2026年10月16日 更新

Organize customer feature requests into themes and rank the top three against product goals, customer value, effort, and risk. For each recommendation, explain the underlying need, possible alternatives, uncertain assumptions, and simple ways to test them.

中文简介正在准备中。当前显示英语简介。

  • Grouping customer requests into themes
  • Selecting the top three requests for product goals
  • Considering alternatives to requested features
phuryn/pm-skills2.7万2026年10月16日 更新

Compare growth options across existing and new products and markets using the Ansoff Matrix, a four-part planning framework. Assess opportunities, resources, competition, and risks, then develop market launch plans and a phased roadmap for priority options.

中文简介正在准备中。当前显示英语简介。

  • Comparing growth options for an existing business
  • Planning expansion into new regions or customer groups
  • Evaluating new products for current customers
phuryn/pm-skills2.7万2026年10月16日 更新

Choose the first customer segment for a product launch by comparing urgent needs, willingness to pay, achievable market share, and referral potential. Get scored recommendations, a priority segment, a 90-day acquisition plan, and expansion options.

中文简介正在准备中。当前显示英语简介。

  • Choosing the first customer segment for a new product
  • Focusing limited resources on a launch market
  • Comparing segments using interviews and customer feedback
phuryn/pm-skills2.7万2026年10月16日 更新

Plan low-effort experiments to check assumptions about an existing product before building a feature. Compare prototypes, A/B tests, and other methods, with a clear assumption, procedure, metric, and success threshold for each experiment.

中文简介正在准备中。当前显示英语简介。

  • Checking feature assumptions before implementation
  • Planning prototype usability tests
  • Defining metrics and success thresholds for A/B tests
phuryn/pm-skills2.7万2026年10月16日 更新

Turn a new product idea into a testable hypothesis and two or three simple experiments. Define target customers, expected actions, measurement methods, and success thresholds to assess demand through behavior such as sign-ups, pre-orders, or paid commitments.

中文简介正在准备中。当前显示英语简介。

  • Testing demand before building a new product
  • Planning landing page or waitlist experiments
  • Checking willingness to pay through pre-orders
phuryn/pm-skills2.7万2026年10月16日 更新

查看 phuryn 的全部技能

报告此技能的问题