Team OKR Brainstorm

Brainstorm Team OKRs

by phuryn · MIT license · ★ 26,557 on GitHub · updated Sep 14

Brainstorm Team OKRs cover

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…

---
name: brainstorm-okrs
description: "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."
---

# 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*):

Overview

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.

Manual install (npx, ZIP)
Claude Codenpx skills add phuryn/pm-skills --skill brainstorm-okrs -g -a claude-code
Claude Code (degit)npx degit phuryn/pm-skills/pm-execution/skills/brainstorm-okrs#main ~/.claude/skills/brainstorm-okrs
Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md4.2 KB
Read SKILL.md here
phuryn/main1 file shown
SKILL.md
Show the full text81 lines

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
1---
2name: brainstorm-okrs
3description: "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."
4---
5 
6# Brainstorm Team OKRs
7 
8## Purpose
9 
10You 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.
11 
12## Context
13 
14OKRs 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.
15 
16## Domain Context
17 
18**OKR** (Christina Wodtke, *Radical Focus*):
19- **Objective** (Why, What, When): Qualitative, inspirational, time-bound goal. Typically quarterly. Should be SMART.
20- **Key Results** (How much): Quantitative metrics (typically 3) and their expected values.
21 
22**OKRs, KPIs, and NSM are interconnected — not alternatives.** Don't compare them in a table without explaining their relationship:
23- **Key Results** always refer to quantitative metrics, some of which might be KPIs.
24- **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.
25- **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.
26 
27OKRs 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.
28 
29## Instructions
30 
311. **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.
32 
332. **Understand the Framework**: OKRs have two components:
34 - **Objective**: A qualitative, inspirational goal describing the directional intent
35 - **Key Results**: 3 quantitative metrics (typically) measuring progress toward the objective
36 
373. **Think Step by Step**:
38 - What is the company strategy?
39 - What are the 3-5 most impactful areas the team can influence?
40 - How do team efforts ladder up to company goals?
41 - What would success look like for customers and the business?
42 
434. **Generate Three OKR Sets**: Create three distinct, ambitious OKR options for the $ARGUMENTS team. For each set:
44 - Start with a clear, inspiring Objective statement
45 - Define exactly 3 Key Results that are:
46 - Measurable (can be tracked numerically)
47 - Achievable but ambitious (60-70% confidence level)
48 - Aligned with company strategy
49 
505. **Example Format**:
51 ```
52 Objective: Delight new users with an effortless onboarding experience
53 Key Results:
54 - CSAT score >= 75% on onboarding survey
55 - 66%+ of onboardings completed within two days
56 - Average time-to-value (TTV) <= 20 minutes
57 ```
58 
596. **Structure Output**: Present all three OKR sets with equal weight. For each, include:
60 - Objective (1-2 sentences)
61 - Three Key Results (specific metrics with targets)
62 - Brief rationale (why this matters to the company and team)
63 
647. **Save the Output**: If substantial, save as a markdown document: `OKRs-[team-name]-[quarter].md`
65 
66## Notes
67 
68- Ensure each Key Result is independently measurable
69- Avoid output-focused metrics (e.g., "launch 5 features"); focus on outcomes
70- All three OKR sets should be credible, not one clearly better than others
71- Flag any assumptions about data availability
72 
73---
74 
75### Further Reading
76 
77- [Objectives and Key Results (OKRs) 101](https://www.productcompass.pm/p/okrs-101-advanced-techniques)
78- [OKR vs KPI: What's the Difference?](https://www.productcompass.pm/p/okr-vs-kpi-whats-the-difference)
79- [Business Outcomes vs Product Outcomes vs Customer Outcomes](https://www.productcompass.pm/p/business-outcomes-vs-product-outcomes)
80- [From Strategy to Objectives Masterclass](https://www.productcompass.pm/p/product-vision-strategy-objectives-course) (video course)
81 
View all files on GitHub →

Details

Updated
Sep 14, 2026
License
MIT
Stars on the repo
★ 26,557
Checked
Source
phuryn/pm-skills ↗
Creator
phuryn · 69 listings
View creator

Similar skills

See all →
AgentPhase 2: Foundation Scaffoldingmsitarzewski/agency-agents · by msitarzewski> Duration: 3-5 days | Agents: 6 | Gate Keepers: DevOps Automator + Evidence Collector★ 154k GitHub starsAgentNEXUS Network Frameworkmsitarzewski/agency-agents · by msitarzewski> NEXUS transforms The Agency's independent AI specialists into a synchronized intelligence network. This is not a prompt collection — it…★ 154k GitHub starsSkillAnsoff Matrix Generatorphuryn/pm-skills · by phurynGenerate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.★ 26.6k GitHub starsSkillArchitecture Advisorshadcn/improve · by shadcnSurvey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.★ 9.2k GitHub starsSkillCareer Skills TranslatorParamchoudhary/ResumeSkills · by ParamchoudharyTranslate skills from one industry to another, identify transferable skills★ 2.4k GitHub starsSkillMarketing Skills CollectionLeoYeAI/openclaw-marketing-skills · by LeoYeAIA collection of 37 battle-tested marketing skills for OpenClaw agents. Use when you want to install or reference any marketing skill including: CRO (page-cro, signup-flow-cro, onboarding-cro, form-cro, popup-cro, paywall-upgrade-cro), copywriting, copy-editing, cold-email, email-sequence, social-content, seo-audit, ai-seo, programmatic-seo, site-architecture, schema-markup, content-strategy, paid-ads, ad-creative, ab-test-setup, analytics-tracking, referral-program, free-tool-strategy, churn-prevention, revops, sales-enablement, launch-strategy, pricing-strategy, competitor-alternatives, marketing-ideas, marketing-psychology, lead-magnets, product-marketing-context, and data connectors (google-ads-connect, search-console-connect, meta-ads-connect, x-twitter-connect). Start with product-marketing-context to set up your product context document, then use any other skill naturally. Powered by MyClaw.ai.★ 1k GitHub stars

More from phuryn

SkillA/B Test Analyzerphuryn/pm-skills · by phurynAnalyze 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.★ 26.6k GitHub starsSkillFeature Request Prioritizerphuryn/pm-skills · by phurynAnalyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.★ 26.6k GitHub starsSkillAnsoff Matrix Generatorphuryn/pm-skills · by phurynGenerate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.★ 26.6k GitHub starsSkillAI Text Humanizerphuryn/work-humanizer · by phurynEdit AI-sounding text so it reads like a careful person wrote it, without changing what it says or commits to. Built for work writing where the wording matters: sales and marketing copy, support replies, HR and legal letters, emails, docs, release notes, posts, landing pages. Two modes. Rewrite: edit the text you are given. Interview: when a draft is AI-composed and thin, ask the writer 3-5 sharp questions and build the piece from their answers, in their words. Also writes from the writer's own notes or a voice-memo transcript. Calibrated on measured differences between human and AI writing.★ 110 GitHub starsSkillMarket Segment Identifierphuryn/pm-skills · by phurynIdentify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.★ 26.6k GitHub starsSkillProduct Experiment Designerphuryn/pm-skills · by phurynDesign experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.★ 26.6k GitHub stars