Generated banner for Brainstorm Okrs
Generated logo for Brainstorm Okrs

Brainstorm Okrs

Pawel HurynCommunityCreated by Pawel Huryn

  • Skill
  • Content generator
  • Business and productivity
  • MIT
  • No issues found

From the author

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.
— the description by Pawel Huryn

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill acts as a product leadership assistant to help teams define Objectives and Key Results (OKRs). It bridges the gap between high-level company strategy and team-level execution by generating three distinct, outcome-focused OKR sets. The skill emphasizes the use of qualitative, inspirational objectives paired with three quantitative, measurable key results to ensure team efforts ladder up to broader business goals.

What it does

  • Generates three alternative sets of team-level OKRs
  • Drafts qualitative and inspirational objective statements
  • Defines three measurable, outcome-focused key results per objective
  • Provides rationale for how each OKR set aligns with company strategy
  • Offers guidance on the relationship between OKRs, KPIs, and North Star Metrics

When to use it

  • When setting quarterly goals for a product or engineering team
  • When aligning team initiatives with overarching company strategy
  • When drafting new objectives to ensure they are measurable and ambitious
  • When learning how to structure effective OKRs

Advantages

  • Encourages strategic alignment between team output and company goals
  • Focuses on outcomes rather than output-based tasks
  • Provides multiple options to spark internal team discussion
  • Ensures key results are independently measurable

Usage examples

“Brainstorm OKRs for our mobile app team for Q3.”
The agent provides three distinct OKR sets, each with an inspirational objective and three specific, measurable key results relevant to mobile app performance and user engagement.
“Help me draft OKRs for the data platform team aligned with our company goal of reducing infrastructure costs.”
The agent generates three OKR options focused on cost-efficiency and platform performance, including specific metrics for tracking progress toward the company's cost-reduction goal.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/phuryn/brainstorm-okrs/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip brainstorm-okrs.zip -d .agents/skills

Documentation by Pawel Huryn

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

Files

ATTRIBUTION.md

Attribution

This folder is an unmodified copy of the Agent Skill "brainstorm-okrs", distributed by AutoGineer (https://autogineer.com/agent-skills).

The skill's own files are unmodified copies. AutoGineer is not affiliated with or endorsed by the author or the publisher.

Files added by AutoGineer

  • ATTRIBUTION.md: this file, written by AutoGineer

  • LICENSE: copied from LICENSE

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Pawel Huryn
Publisher
Pawel Huryn (Community)
Source
phuryn/pm-skills · pm-execution/skills/brainstorm-okrs · commit 2a12295
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Pawel Huryn or Pawel Huryn.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download brainstorm-okrs.zip