OKR Breakdown Assistant

The Problem Is Not Writing OKRs, but Execution Drift

Teams often have an Objective but struggle with measurable Key Results, weekly execution cadence, and review checkpoints. OKR Breakdown Assistant starts from one Objective, checks scope, horizon, and baseline, then generates 3-5 measurable KRs and breaks them into weekly actions. Its focus is turning vague goals into inspectable plans, not replacing strategic judgment or performance scoring.

Core Workflow and Boundaries

The skill works in four steps:
- Clarify the objective: confirm meaning, time horizon, and baseline
- Design KRs: produce measurable and complementary results around the Objective
- Decompose tasks: map each KR to weekly actions, milestones, and dependencies
- Validate adjustments: check whether tasks can support KRs and whether resources and timing are feasible

Outputs emphasize no more than 5 KRs, avoid vague terms such as 'improve' or 'optimize,' and suggest setting stretch difficulty around a 70% confidence level. Use it with constraints in mind: it does not fetch business data, so KR values still require user confirmation. It is not suitable for KPI scoring, project scheduling, daily task assignment, or year-end reviews. If the Objective is too abstract, the baseline is missing, or the time horizon is unclear, it prompts for missing context. Teams should treat strategic goals with appropriate data minimization, since the skill only assists execution breakdown and does not judge or externally report OKR performance.