Brainstorm Okrs
Draft three alternative quarterly OKR sets that tie team objectives to company strategy before you commit to a roadmap.
Overview
Brainstorm OKRs is an agent skill most often used in Build (also Validate, Grow) that drafts three aligned quarterly OKR alternatives with measurable key results for a team scope you pass in as $ARGUMENTS.
Install
npx skills add https://github.com/phuryn/pm-skills --skill brainstorm-okrsWhat is this skill?
- Generates three alternative OKR sets to spark strategic discussion before you lock one quarter
- Frames objectives as qualitative SMART goals and key results as three quantitative targets
- Explains how OKRs, KPIs, and North Star metrics relate—not as interchangeable substitutes
- Anchors output to company-wide strategy so team OKRs ladder up to org objectives
- Veteran product-leader voice for $ARGUMENTS team or product scope
- Three alternative OKR sets generated per run
- Typically three key results per objective in the OKR model described
Adoption & trust: 1.1k installs on skills.sh; 12.3k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You know company direction loosely but lack crisp quarterly objectives and numeric key results your agent or team can execute against.
Who is it for?
Indie founders and lead builders wearing the PM hat who need quarterly OKR options anchored to stated company objectives.
Skip if: Teams that already have executive-approved OKRs locked for the quarter and only need task breakdown—use an implementation-plan skill instead.
When should I use this skill?
Setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
What do I get? / Deliverables
You leave with three comparable OKR sets, clear OKR–KPI–NSM relationships, and a chosen direction ready to paste into your roadmap or invoke a follow-on planning skill.
- Three alternative OKR sets (objectives plus key results)
- Narrative on OKR, KPI, and North Star relationships
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
OKR brainstorming is canonical PM work during build—turning strategy into measurable quarterly goals—though the same ritual applies when rescoping in validate or re-aiming metrics in grow. The pm subphase is where solo builders set objectives, key results, and alignment rituals without a dedicated product org.
Where it fits
Define measurable key results that prove your MVP hypothesis before you commit engineering weeks.
Produce three OKR variants for your solo SaaS so you can pick the quarter’s focus before writing an implementation plan.
Reframe objectives around activation or retention KPIs while keeping one clear North Star narrative.
How it compares
Use instead of generic chat OKR lists that treat KPIs and North Star metrics as unrelated alternatives.
Common Questions / FAQ
Who is brainstorm-okrs for?
Solo and indie builders, product-minded founders, and small teams who set their own quarterly goals without a full product leadership bench.
When should I use brainstorm-okrs?
Use it in Validate when scoping what success looks like before a big build, in Build pm when setting quarterly team goals, and in Grow when reframing objectives around retention or revenue metrics—you pass the team or product focus as $ARGUMENTS.
Is brainstorm-okrs safe to install?
It is procedural planning content with no shell or network requirements by default; review the Security Audits panel on this Prism page before installing from any third-party skills repo.
SKILL.md
READMESKILL.md - Brainstorm 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*): - **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 - [Objectives and Key Results (OKRs) 101](https://www.productcompass.pm/p/okrs-101-advanced-techniques) - [OKR vs KPI: What's the Differenc