Team OKR Writer
Write one team's OKRs as measurable outcomes with baselines and targets, graded on a 10-point test that rejects task lists.
Before & after
Same prompt, same agent — the only difference is the skill.
OKRs are about setting clear goals and measurable key results together. You need an objective that's inspiring and qualitative, then key results that are quantifiable and measurable. Try to aim for three to five key results per objective typically. Key results should stretch your team's abilities but still be achievable. You should align OKRs across the company so everyone is working toward the same goals and priorities. Regular check-ins help track progress and keep momentum. Would you like me to walk you through creating OKRs for a specific business area or department? I can help with the framework.
OKR FRAMEWORK - Q3 2026 STARTUP OBJECTIVE 1: Accelerate product adoption through self-serve onboarding Key Result 1a) Reduce time-to-first-action from 12 minutes to 4 minutes (task completion speed) Key Result 1b) Increase 7-day retention from 38% to 52% (new user stickiness) Key Result 1c) Launch 3 onboarding variants via A/B testing, select winner (experimentation velocity) Owner: Product Lead, Engineering Lead Initiatives: Questionnaire flow (Week 1), in-app tutorial (Week 2), tutorial variants (Week 3-4) OBJECTIVE 2: Build predictable revenue engine via founding partnerships Key Result 2a) Onboard 4 strategic partners (each with 10k+ audience) Key Result 2b) Achieve 6k MRR through partner referrals (revenue target) Key Result 2c) Develop repeatable partner onboarding playbook (process maturity) Owner: Sales Lead, Operations Initiatives: Partner prospecting list (Week 1), API documentation (Week 2), revenue split negotiation (ongoing) OBJECTIVE 3: Strengthen engineering velocity and reliability Key Result 3a) Reduce production incident mean-time-to-resolution from 4 hours to 1 hour (resilience) Key Result 3b) Achieve 95% test coverage on all new code (quality gate) Key Result 3c) Migrate 100% of legacy codebase to TypeScript (technical debt reduction) Owner: Engineering Lead Initiatives: Incident playbook (Week 1), testing infrastructure (Week 2-3), TypeScript migration (ongoing) ALIGNMENT RULE: Each initiative maps to one KR. No initiative without owner. Weekly check-ins on green/yellow/red status.
About this skill
Turn a team's project list into 1-3 objectives with key results that measure outcomes. Every KR has a baseline, a target, and a data source, and traces to a company priority.
What it does
- Asks 'so that what?' about each project until it reaches a real outcome metric
- Drafts objectives tied to named company priorities, with 2-4 KRs each and counter-metrics
- Grades each KR on five tests (outcome, measurable, controllable, calibrated, linked) and rewrites anything under 8/10
- Moves projects to initiatives under the KRs they are meant to move
What you get
A finished OKR set with scores, notes on what was rewritten and why, what was left out this quarter, and a weekly check-in rhythm.
Best for
Team leads, managers, and ICs whose OKRs have turned into to-do lists.
SKILL.md preview
---
name: team-okr-writer
description: Write one team's quarterly OKRs - 1-3 objectives with 2-4 measurable key results each - tied to a named company priority, with baselines, targets, and a quality score that rejects task lists disguised as key results. Use when the user asks to write, draft, fix, or grade OKRs for a team or for themselves, or says "our key results are just a to-do list", including casual asks like "is this a good KR?", "help me write OKRs for my team", or "can you fix these goals so they're measurable".
---
# Team OKR Writer
… (sign up to view the full skill)More business & ops skills
View all Business & Ops skills →Simulated Board Pressure Test
Stress-tests a proposal from each board seat's incentives, forecasts the vote, and names the changes that would get it approved.
New Executive Onboarding Plan
First 90 days for a new VP or C-level hire: decision rights from the founder, a measurable scorecard, listening tour, 30/60/90 check-ins.
Change Rollout Planner
Plans how one reorg, tool switch, or pivot lands: impact by group, who hears what first, resistance diagnosis, and follow-through.
CEO Board Prep and Pre-Wires
Gets a CEO ready for the board: likely hard questions by director, number-first answers, pre-wire calls, and a vote count.