okr-manager

To track Objectives and Key Results for measurable impact, define each Objective with 2-4 measurable Key Results and a clear DRI. The skill logs progress to OKR documents and integrates with STATUS.md for ongoing visibility across quarterly planning cycles.

The best way to align team OKRs with company strategy is using parallel fan-out across Objectives and Dependencies. This approach accelerates quarterly planning by structuring objectives to focus on outcomes rather than vanity metrics.

OKR tracking works with markdown files by using view_file and write_to_file tools to read and persist data. It integrates with SETTINGS.md, DECISION_LOG.md, and STATUS.md to store context, reference decisions, and maintain ongoing visibility.

Yes, you can use CLI prompts to fill missing context when drafting OKRs. The skill supports sequential drafting that prompts you for missing information, ensuring complete objectives and structured alignment before finalizing.

Yes, you need a Directly Responsible Individual (DRI) assigned to every Objective for effective OKR tracking. Assigning a DRI ensures clear ownership and accountability for achieving the 2-4 measurable Key Results defined.

You should not use a structured OKR approach for product initiatives when focusing on vanity metrics rather than outcomes. If you cannot define 2-4 measurable Key Results per Objective, the structured tracking process will not drive measurable impact.