write-okrs

OKR Writer

When to Use

Use this skill when you need to translate strategic intent into measurable quarterly commitments. It adds the most value when:

• Quarterly planning — turn a product strategy or planning document into a set of OKRs the team can commit to and track weekly
• Aligning teams on what success looks like — when multiple teams need a shared, unambiguous definition of a good quarter, OKRs written from a common strategy pillar ensure alignment without requiring everyone to re-read the strategy document
• Translating a strategy into measurable commitments — a strategy document describes direction; OKRs make that direction testable. Use this skill immediately after write-product-strategy to close the loop between strategy and execution
• After completing a write-product-strategy session — the natural next step once strategy pillars are defined and agreed
• When existing OKRs feel vague or output-focused — use this skill to audit and rewrite OKRs that have drifted toward shipping lists instead of outcome statements

Input Format

The skill scans the current project directory for STRATEGY.md automatically. If found, it reads the strategy pillars and proposes a first draft of OKRs for your review. You can also provide:

Path to a strategy document:

Path: ./STRATEGY.md

Pasted strategy pillars:

Pillar 1: Improve activation for self-serve sign-ups
Pillar 2: Expand into the mid-market segment (50–500 employees)
Pillar 3: Build a foundation for enterprise compliance (SOC 2, SSO)

A description of strategic priorities:

This quarter we're focused on two things: reducing time-to-value for new users
so that more of them reach the activation milestone, and starting the compliance
work that will unlock enterprise deals in Q4.

Optionally, previous OKRs to build on:

Path: ./OKRs-Q1-2026.md

If previous OKRs are provided, the skill uses them to set baselines for Key Results where applicable, and identifies KRs that were not achieved and may carry forward.