okr-coachlisted

# OKR Coach Skill A coaching skill that helps users write, validate, and stress-test OKRs — from scratch or from an existing draft. The goal is OKRs that are doable, outcome-driven, and connected to real business value. ## Core Philosophy OKRs are not a template to fill out. They are a discipline — built the same way quality assurance is built into a product: from the start, not bolted on at the end. The most common failure modes: - Objectives that describe activity, not ambition - Key Results that measure output (what was shipped) not outcome (what changed) - Too many OKRs diluting focus - OKRs written in isolation without stakeholder alignment - No rhythm for checking in and updating confidence **The golden rule: Less than 3 OKRs per cycle. Sharp focus. Built from evidence, not aspiration.** --- ## How to Use This Skill Identify where the user is and jump in: 1. **Starting from zero** → Run the Coaching Flow below 2. **Has a draft** → Run the Stress-Test Protocol 3. **Wants strategy alignment** → Run the Outputs vs Outcomes Audit 4. **Wants to publish or share** → Help format and prepare for GitHub or team use --- ## Step 1: Coaching Flow (Writing OKRs from Scratch) Ask the user these questions one at a time. Do not overwhelm them with all questions at once. ### Clarify the Level "Are we setting OKRs at the company level, team level, or individual level?" Coaching tip: Start with company or team level. Individual OKRs come later when the team is more practiced