NioPD ST okr

Skill 8421bit/NioPD-Skills/plugins/niopd/skills/NioPD-ST-okr

Agent Skills for AI-powered Product Management with Claude Code.

Install

npx -y skills add 8421bit/NioPD-Skills --skill NioPD-ST-okr

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Applies OKR (Objectives and Key Results) framework to define and track strategic goals. Use for quarterly planning, goal alignment, performance management, or team focus.

SKILL.md

3.1 KB, 816 tokens by cl100k_base, as published. Nobody here has run it

OKR Framework Skill

This skill applies the OKR framework to set ambitious, measurable goals and track progress systematically.

Theoretical Foundation

Origin

OKRs were developed by Andy Grove at Intel and popularized by John Doerr at Google. They're now used by leading tech companies worldwide.

OKR Structure

Objective (WHAT): Qualitative, inspirational goal
├── Key Result 1 (HOW): Quantitative measure
├── Key Result 2 (HOW): Quantitative measure
└── Key Result 3 (HOW): Quantitative measure

Component	Characteristics
Objective	Qualitative, memorable, ambitious
Key Results	Quantitative, measurable, time-bound

Good OKR Criteria

Objectives: Ambitious but achievable, inspiring, directive
Key Results: Specific, measurable, stretch (60-70% success = healthy)

OKR Types

Company OKRs: Organizational direction
Team OKRs: Departmental contribution
Individual OKRs: Personal contribution

When to Use

Quarterly planning
Annual strategy cascade
Team alignment
Performance reviews
Focus maintenance

Instructions

Step 1: Define Objectives

For each objective:

"What do we want to achieve?"
"Why does this matter?"
"Is it inspirational and memorable?"

Step 2: Define Key Results

For each objective, define 2-5 key results:

"How will we know we achieved it?"
"What number will change?"
"Is it ambitious but achievable?"

Step 3: Validate KRs

Each Key Result should be:

Step 4: Score Baseline and Targets

KR	Baseline	Target	Stretch
[KR1]	[Current]	[70% success]	[100% success]

Step 5: Create Tracking Plan

Weekly: Quick confidence check
Monthly: Detailed progress review
Quarterly: Scoring and retrospective

Step 6: Generate OKR Document

File path: 04-plans/[YYYYMMDD]-okr-[quarter]-v0.md

Format:

## Objective 1: [Objective Statement]

| Key Result | Baseline | Target | Current | Score |
|------------|----------|--------|---------|-------|
| KR1.1: [Result] | [X] | [Y] | [Z] | [0-1.0] |
| KR1.2: [Result] | [X] | [Y] | [Z] | [0-1.0] |

**Overall Score**: [Average]
**Status**: 🟢 On Track / 🟡 At Risk / 🔴 Off Track

Scoring Guide

0.0-0.3: Failed to make progress
0.4-0.6: Made progress but fell short
0.7-1.0: Delivered (1.0 may mean not ambitious enough)

Output Specifications

File Naming: [YYYYMMDD]-okr-[quarter]-v0.md
Location: 04-plans/
Template: references/okr-template.md

Related Skills

niopd-pm-kpis: KPI definition
niopd-po-north-star: North Star alignment
niopd-pd-roadmap: Execution planning
niopd-st-balanced-scorecard: Multi-dimensional goals

Gives 0 of the 12 instructions most roadmap strategy skills give in 816 tokens

Counted across 591 of the 672 authors here whose files we hold, read 2026-08-06

read product marketing context before asking questionsin 21 of 591, across 10 files
base price on perceived value, not costin 15 of 591, across 4 files
compact after finalizing a planin 14 of 591, across 9 files
differentiate tiers using features, limits, or supportin 14 of 591, across 3 files
use Van Westendorp to find acceptable price rangein 13 of 591, across 2 files
use MaxDiff to identify highly valued featuresin 13 of 591, across 2 files
map topics to buyer journey stagesin 12 of 591, across 6 files
Extract domain capabilities and classify subdomainsin 11 of 591, across 1 file
Define bounded contexts around consistency and ownershipin 11 of 591, across 1 file
Establish a ubiquitous language glossary and anti-termsin 11 of 591, across 1 file
Capture context boundaries in ADRs before implementationin 11 of 591, across 1 file
Open the strategic design template if neededin 11 of 591, across 1 file

Said here and by no other author read

Define qualitative objectives
Validate key results against specific criteria
Create a progress tracking plan
Generate the OKR document

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.