phuryn/pm-skills

brainstorm-okrs

Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results.

Ver código-fonte

Como usar

  1. Copie o comando e verifique o pacote antes de instalar no seu ambiente de agente.
  2. Consulte no original as ferramentas, credenciais e ambientes necessários.
  3. Descreva os dados de entrada e a entrega esperada; confira a saída com as fontes.
npx skills add https://github.com/phuryn/pm-skills --skill brainstorm-okrs

Antes de começar

  • A instalação não inclui assinatura de modelo, franquia API ou acesso aos seus arquivos.
  • Estrelas e instalações indicam atividade, não um teste independente de qualidade ou segurança.
Documento original do Skill

Renderizado do repositório de origem, preservando títulos, exemplos, código, tabelas, links e imagens.

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.
  1. 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
  1. 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?
  1. 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
  1. 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
  1. 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)
  1. 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

Relacionados por tarefa

do mesmo repositório

Mais Skills

Todos os Skills
phuryn
Comunidade

strategy-red-team

Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.

Instalações / 1h
4
GitHub Stars
28,1 mil
Atualizado
8 de nov.
phuryn
Comunidade

ansoff-matrix

Generate 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.

Instalações / 1h
2
GitHub Stars
28 mil
Atualizado
8 de nov.
phuryn
Comunidade

grammar-check

Identify grammar, logical, and flow errors in text and suggest targeted fixes without rewriting the entire text. Use when proofreading content, checking writing quality, or reviewing a draft.

Instalações / 1h
2
GitHub Stars
28 mil
Atualizado
8 de nov.
phuryn
Comunidade

privacy-policy

Draft a detailed privacy policy covering data types, jurisdiction, GDPR and compliance considerations, and clauses needing legal review. Use when creating a privacy policy, updating data protection documentation, or preparing for compliance.

Instalações / 1h
2
GitHub Stars
28 mil
Atualizado
8 de nov.