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
/plugin marketplace add tarunccet/pm-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add tarunccet/pm-skills --skill brainstorm-okrsgit clone --depth 1 https://github.com/tarunccet/pm-skills.git /tmp/pm-skills
mkdir -p ~/.claude/skills
cp -r /tmp/pm-skills/pm-execution/skills/brainstorm-okrs ~/.claude/skills/brainstorm-okrsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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.
Details
- Skill name
brainstorm-okrs- Repository
- tarunccet/pm-skills
- Path
pm-execution/skills/brainstorm-okrs/SKILL.md- License
- MIT
- Repo updated
- 13 November 2026
FAQ
What does the Brainstorm Okrs skill do?
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.
How do I install the Brainstorm Okrs skill?
Claude Code plugin: /plugin marketplace add tarunccet/pm-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Brainstorm Okrs popular?
It lives in tarunccet/pm-skills, which has 9 GitHub stars and 2 forks.
Related skills
Ab Test Analysis
9tarunccet/pm-skills
Analyze 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.
Adr
9tarunccet/pm-skills
Document architecture and product decisions using the Nygard ADR format — captures context, alternatives considered, and consequences so the team never asks 'why did we do it this way?' again. Use when making architecture decisions, choosing between technical approaches, selecting vendors, or any decision that will be hard to reverse.
AI Build Buy Partner
9tarunccet/pm-skills
Evaluate AI capability sourcing options across build, buy, fine-tune, and partner archetypes using a structured decision matrix. Use when deciding whether to build a custom model, use an LLM API, fine-tune a base model, or partner with an AI vendor.
Create Prd
9tarunccet/pm-skills
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
Awesome Docs
9wangyendt/wayne-skills
Use this skill whenever the user asks to record, organize, update, or maintain project documentation, including architecture overviews and decisions, technical books and derivations, API/protocol/configuration references, implementation plans, roadmaps, todos, risks, experiments, know-how, or common commands. Choose paths and naming by document purpose, preserve existing canonical locations, and check links when reorganizing. Defaults to the target project’s docs directory unless the user specifies another location. Covers reader-first technical explanations and interactive HTML documents as w
Hypothesis
9tarunccet/pm-skills
Write testable product hypotheses with clear success metrics, baselines, targets, and timeframes. Produces a structured hypothesis statement, supporting evidence, a validation plan with method and sample size, and a decision framework for what to do if validated or invalidated. Use when validating product assumptions, before running experiments, when proposing new features, or when shifting from opinion-based to evidence-based decision making.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.