Structured OKR retrospective framework for classifying hit/partial/miss outcomes, tracing root causes, and feeding calibration back into the next cycle. Use when closing a cycle, capturing learning, or separating execution failure from target-setting error.
From opspal-okrsnpx claudepluginhub revpalsfdc/opspal-commercial --plugin opspal-okrsThis skill is limited to using the following tools:
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Designs, audits, and improves analytics tracking systems using Signal Quality Index for reliable, decision-ready data in marketing, product, and growth.
Enforces A/B test setup with gates for hypothesis locking, metrics definition, sample size calculation, assumptions checks, and execution readiness before implementation.
Every KR should be classified with:
hit, partial, or missUse a small set of clear root-cause buckets:
execution_gapdependency_blockerdata_quality_gaptarget_setting_errorexternal_market_changedefinition_changeDo not let “miscellaneous” become the default answer.
config/okr-outcomes.json, not just in proseA strong retrospective should answer:
config/okr-outcomes.jsonscripts/lib/okr-outcome-calibrator.jscommands/okr-history.md