Decompose PMContext into one qualitative Objective and three measurable Key Results.
npx skills add https://github.com/Wcof/PMSkill --skill pm-okr-wcof
Please help me install this Agent Skill. Skill: pm-okr Source: https://github.com/Wcof/PMSkill/tree/main/skills/delivery/pm-okr Command: npx skills add https://github.com/Wcof/PMSkill --skill pm-okr-wcof
This Skill helps product teams turn a messy strategy discussion or an existing PMContext into a concrete quarterly OKR set. It prevents common planning mistakes such as writing Objectives as metrics, using vague Key Results, or confusing KR with KPI and NSM.
Ask the AI to use pm-okr to turn your PMContext and company strategy into three quarterly OKR options and select the best one with measurable KRs.
High-intent search queries and answers about installing and using this skill.
To turn product strategy into quarterly OKRs, decompose your PMContext into one qualitative Objective and three measurable Key Results, validating each KR for thresholds, 60-70% confidence, and traceability to source metrics. This prevents writing Objectives as metrics or using vague KRs. It generates growth, retention, and experience-oriented OKR options to compare before selecting the best aligned set.
The difference between a Key Result, KPI, and North Star Metric (NSM) lies in their scope: KRs are quarterly targets validating 60-70% confidence, KPIs are ongoing operational metrics, and NSMs represent ultimate product value. This Skill clarifies these relationships by explicitly validating each KR against your defined KPI and NSM definitions to ensure correct strategic alignment.
To generate growth versus retention tradeoffs for quarterly planning, input your PMContext to produce three differentiated candidate OKR sets: growth-oriented, retention-oriented, and experience-oriented. The Skill compares these strategic options, analyzes the metric-driven tradeoffs, and helps you select the best aligned OKR document for your roadmap communication.
To write measurable Key Results with thresholds, extract value-validation metrics from PMContext and validate each KR against a 60-70% confidence range. This process ensures every Key Result includes a specific threshold, remains measurable, and maintains explicit traceability back to your source metrics and NSM definitions for clear roadmap communication.
Yes, you can use PMContext to create metric-driven roadmap communication by extracting user scenarios, metrics, and constraints to generate aligned quarterly OKRs. The output is a final OKR document with full traceability back to source metrics, ensuring leadership understands the strategic alignment and growth versus retention tradeoffs behind your Q3 goals.
You should not use automated OKR decomposition when your PMContext lacks extracted user scenarios, value-validation metrics, or clear constraints. The Skill requires these inputs to validate KR measurability, maintain 60-70% confidence ranges, and ensure traceability; without them, it cannot effectively clarify KR, KPI, and NSM relationships or produce a reliable OKR document.
WcofRefines candidate metrics into a validated North Star Metric framework with guardrails and Mermaid tree.
maigenticTranslate strategic inputs into an 18-month OKR-driven roadmap with milestones and resource planning.
OsirsDefine a North Star Metric and validate it against seven criteria.
baizhine999Simulate enterprise leadership negotiations for KPI and OKR target-setting during quarterly planning.
