Product-org-os okr-writer

Document Intelligence

This skill supports three modes: Create, Update, and Find.

Mode Detection

@path/to/okrs.md

Threshold: >=85% auto-proceed | 70-84% state assumption | <70% ask user

Mode Behaviors

CREATE: Generate complete OKR set with objectives, key results, quality review, alignment map, and cadence plan using template below.

UPDATE:

1. Read existing OKR document (search if path not provided)
2. If "review" or "score" detected: run quality checklist against existing OKRs, flag issues
3. If "update" detected: preserve structure, update specific objectives or key results
4. Show diff summary: "Updated: [sections]. Unchanged: [sections]." or "Review: [N] issues found."
5. Note: Mid-quarter OKR changes should be documented with rationale

FIND:

1. Search paths below for OKR documents
2. Present results: title, team/quarter, objective count, path
3. Ask: "Update one of these, or create new?"

Search Locations for OKRs

• strategy/

• okrs/

• planning/

• product/

Gotchas

• Key Results must be outcomes, never tasks -- "Launch feature X" is a task; "Increase activation rate from X% to Y%" is a KR
• Aspirational OKRs scoring 1.0 consistently means the bar is too low -- 0.7 is the target for stretch goals
• OKRs are NOT a task list or project plan -- they define where you want to end up, not how to get there
• Avoid more than 3-5 objectives per team per quarter -- focus beats coverage

Write, review, or score OKRs (Objectives and Key Results): craft well-formed objectives (qualitative, inspirational, time-bound) and key results (quantitative, measurable, ambitious), with quality review and anti-pattern detection.

Vision to Value Phase

Phase 1: Strategic Foundation - OKRs translate strategic intent into measurable quarterly goals that align the organization around outcomes.

Prerequisites: Strategic intent or vision defined (Phase 1), or roadmap priorities set (Phase 3) Outputs used by: Phase 3 (roadmap alignment, commitment check), Phase 5 (outcome measurement against OKR targets), Phase 6 (OKR scoring feeds retrospectives)

Methodology

Objective Rules

Key Result Rules

Committed vs Aspirational OKRs

OKR Scoring (0.0 - 1.0)

Anti-Pattern Detection

Alignment Patterns

OKR Cadence

Output Structure

# OKRs: [Team or Initiative Name] -- [Quarter/Year]

**Date**: [YYYY-MM-DD]
**Owner**: [OKR owner -- typically team lead or VP]
**Period**: [Q1/Q2/Q3/Q4 YYYY]
**Team**: [Team name]
**Type**: Company / Team / Individual
**Status**: Draft / Active / Scoring / Closed

## Company Context (if applicable)

**Relevant Company Objectives**:
- [Company Objective this team's OKRs support]
- [Additional company objective, if applicable]

---

## Objective 1: [Qualitative, inspirational objective statement]

**Type**: Committed / Aspirational
**Alignment**: [Which company OKR this supports]

| # | Key Result | Baseline | Target | Score | Status |
|---|-----------|----------|--------|-------|--------|
| 1.1 | [Measurable outcome with number] | [Starting value] | [Target value] | [0.0-1.0 or TBD] | [On Track / At Risk / Behind / Scored] |
| 1.2 | [Key result] | [Baseline] | [Target] | [Score] | [Status] |
| 1.3 | [Key result] | [Baseline] | [Target] | [Score] | [Status] |

**Objective Score**: [Average of KR scores or TBD]

---

## Objective 2: [Objective statement]

**Type**: Committed / Aspirational
**Alignment**: [Company OKR]

| # | Key Result | Baseline | Target | Score | Status |
|---|-----------|----------|--------|-------|--------|
| 2.1 | [Key result] | [Baseline] | [Target] | [Score] | [Status] |
| 2.2 | [Key result] | [Baseline] | [Target] | [Score] | [Status] |

**Objective Score**: [TBD]

---

## Objective 3: [Objective statement]

**Type**: Committed / Aspirational
**Alignment**: [Company OKR]

| # | Key Result | Baseline | Target | Score | Status |
|---|-----------|----------|--------|-------|--------|
| 3.1 | [Key result] | [Baseline] | [Target] | [Score] | [Status] |
| 3.2 | [Key result] | [Baseline] | [Target] | [Score] | [Status] |
| 3.3 | [Key result] | [Baseline] | [Target] | [Score] | [Status] |

**Objective Score**: [TBD]

---

## OKR Quality Review

### Per-Objective Check

| # | Objective | Qualitative? | Inspirational? | Time-bound? | Actionable? | Concise? | Pass? |
|---|-----------|-------------|---------------|------------|------------|---------|-------|
| 1 | [Obj 1 short] | [Y/N] | [Y/N] | [Y/N] | [Y/N] | [Y/N] | [Y/N] |
| 2 | [Obj 2 short] | [Y/N] | [Y/N] | [Y/N] | [Y/N] | [Y/N] | [Y/N] |
| 3 | [Obj 3 short] | [Y/N] | [Y/N] | [Y/N] | [Y/N] | [Y/N] | [Y/N] |

### Per-KR Check

| # | Key Result | Quantitative? | Measurable? | Outcome (not task)? | Has Baseline? | Ambitious? | Pass? |
|---|-----------|--------------|------------|-------------------|-------------|-----------|-------|
| 1.1 | [KR short] | [Y/N] | [Y/N] | [Y/N] | [Y/N] | [Y/N] | [Y/N] |
| 1.2 | [KR short] | [Y/N] | [Y/N] | [Y/N] | [Y/N] | [Y/N] | [Y/N] |
| ... | ... | ... | ... | ... | ... | ... | ... |

### Anti-Patterns Detected

| # | Anti-Pattern | Location | Severity | Suggested Fix |
|---|-------------|----------|----------|---------------|
| 1 | [Pattern name] | [Which OKR/KR] | [High/Medium/Low] | [How to fix] |
| 2 | [Pattern] | [Location] | [Severity] | [Fix] |

**Overall Quality**: [Strong / Acceptable / Needs Revision]
**Issues Found**: [Count]

## Alignment Map

### Vertical Alignment (Company -> Team)

| Company Objective | Team Objective | Team KRs Contributing |
|------------------|---------------|----------------------|
| [Company Obj] | [Team Obj N] | [KR N.1, N.2] |

### Horizontal Dependencies (Cross-Team)

| This Team's KR | Depends On | Other Team | Risk Level |
|---------------|-----------|-----------|-----------|
| [KR N.N] | [What is needed] | [Team name] | [High/Medium/Low] |

## Check-In Cadence

| Week | Focus | Format |
|------|-------|--------|
| Week 1-2 | Set OKRs, align | Workshop |
| Week 3-5 | Confidence check (Red/Yellow/Green per KR) | 15-min standup |
| Week 6-7 | Mid-quarter review, adjust if needed | 1-hour review |
| Week 8-11 | Push for results, escalate blockers | 15-min standup |
| Week 12-13 | Score, reflect, feed into next quarter | Scoring session |

Instructions

1. Ask clarifying questions about the team, quarter, company OKRs (if applicable), and strategic priorities
2. Check prior context: Run

   /context-recall [team/product]

   to find related strategic bets, vision statements, and roadmap themes
3. Check feedback: Run

   /feedback-recall [goals/priorities/objectives]

   for relevant signals
4. Reference any strategy documents, roadmaps, or previous OKR cycles provided via @file syntax
5. Write objectives that are qualitative and inspirational -- push back on numeric objectives
6. Write key results that are outcomes, not tasks -- flag and rewrite any task-based KRs
7. Run the quality review checklist on every OKR set, even in CREATE mode
8. Detect and flag anti-patterns explicitly with suggested fixes
9. Include alignment mapping if company-level OKRs are provided
10. Use [TBD] for scores in new OKRs; populate baselines where possible
11. Save in okrs/, strategy/, or planning/ folder
12. Offer to create presentation version using /present

Context Integration

After generating or reviewing OKRs:

1. Offer to save: Ask "Should I save this to the context registry? (

   /context-save

   )"
2. If yes, extract and save:
   • OKR set and quality review results to context
   • Link to related strategic bets, roadmap themes, and vision statements
   • Cross-team dependencies to

     context/decisions/

     for tracking
3. Suggest using OKR targets as success criteria in

   /strategic-bet

   and

   /commitment-check

4. At quarter end, suggest

   /outcome-review

   and

   /retrospective

   to close the learning loop