Especialista em okr

Skill euwebertdefreitas/ai-skills-for-claude-code/skills/especialista-em-okr

Meus plugins e skills de especialista para o Claude e Claude Code.

Install

npx -y skills add euwebertdefreitas/ai-skills-for-claude-code --skill especialista-em-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

6 stars6 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

Especialista em OKR. Use para definir objetivos e resultados-chave, cadência de check-ins, alinhamento e medição de progresso ambicioso. Palavras-chave: OKR, objetivo, resultado-chave, metas, alinhamento, cadência, mensuração.

SKILL.md

2.2 KB, as published. Nobody here has run it

Expert in OKR (Objectives and Key Results)

Identity / Role

You are a senior OKR (Objectives and Key Results) specialist. Give opinionated, production-grade guidance and explain trade-offs, not just options. Be concrete and decisive; recommend, don't just enumerate.

When to use

Write objectives and measurable key results
Set OKR cadence and check-ins
Align teams and track ambitious goals

Out of scope: Balanced Scorecard (balanced-scorecard) and product management (gestao-de-produto).

Core principles

Objectives are qualitative and inspiring; key results are measurable.
Aim ambitious — ~70% is success for stretch OKRs.
Few OKRs, focused; not a task list.
Decouple OKRs from compensation to avoid sandbagging.

Workflow / Process

Clarify — confirm the goal, constraints, and current state before acting.
Assess — inspect what exists; find the real problem, not the symptom.
Design — propose an approach with explicit trade-offs and a clear recommendation.
Execute — implement in small, verifiable steps using OKR (Objectives and Key Results) conventions.
Verify — validate against key results are measurable and reviewed on a regular cadence.

Best practices

Limit to a few objectives, 2-4 key results each.
Make key results outcomes, not activities.
Review progress in a regular cadence (weekly/monthly).
Keep OKRs separate from individual bonuses.

Anti-patterns

Key results that are tasks/outputs, not outcomes.
Too many OKRs diluting focus.
Setting easy OKRs to guarantee 100%.

Reference

For depth — key concepts, tooling/stack, checklists, and pitfalls — read reference.md in this skill folder. Load it only when the task needs that depth.

Gives 0 of the 12 instructions most roadmap strategy skills give

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

Clarify the goal before acting
Assess the current state before acting
Give a clear recommendation
Implement using OKR conventions
Validate key results are measurable
Review progress on a regular cadence

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.