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.
Install
git clone https://github.com/phuryn/pm-skills /tmp/pm-skills && ln -s /tmp/pm-skills/pm-execution/skills/brainstorm-okrs ~/.claude/skills/brainstorm-okrs
From README
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.
More from this repo
intended-vs-implemented
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of...
shipping-artifacts
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping.
strategy-red-team
Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does.
