본문으로 건너뛰기
cccskills
무료GitHub에 공개

okr-writer

Write OKRs (Objectives and Key Results). Use when the user says "write OKRs", "help me set goals", "create objectives and key results", "quarterly goals", "team OKRs", "I need to define success for this quarter", "Doerr method", or wants to translate a strategic direction into measurable targets - even if they don't explicitly say "OKRs".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

실행 점수 미검증

설치 방법 보기

포함된 파일(1)

  • SKILL.md3.3 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Overview

Based on "Measure What Matters" by John Doerr, who brought OKRs from Intel to Google. Doerr's core distinction: Objectives are the "what" (inspirational, qualitative), Key Results are the "how we know" (measurable, binary at quarter end). CFRs - Conversations, Feedback, Recognition - are what make OKRs work in practice.

Two types of OKRs (Doerr):

  • Committed OKRs - Must be achieved 100%. Missing them requires explanation.
  • Aspirational OKRs - Stretch goals. 70% attainment is success. 100% means you aimed too low.

Workflow

Step 1: Identify the type

Ask: is this a committed OKR (must hit) or aspirational (stretch)? This changes how you write the Key Results.

Step 2: Write the Objective

  • Inspirational and qualitative
  • Memorable - a team should be able to recite it
  • Time-bound to the quarter
  • Answers: "What do we want to be true in 90 days?"

Doerr's test: "Does this objective make you uncomfortable in a good way?" If it's easy, it's not aspirational enough.

Step 3: Write 3-5 Key Results per Objective

Each KR must:

  • Be measurable with a specific number
  • Be outcome-based, not output-based ("30% reduction in churn" not "launch retention feature")
  • Have a baseline and a target
  • Be independently verifiable

Format: [Metric] from [baseline] to [target]

Step 4: Apply the Doerr CFR check

For each OKR set, identify:

  • Conversation: What weekly check-in question will track this?
  • Feedback: How will the team know mid-quarter if they're on track?
  • Recognition: What does hitting this KR mean for the team?

OKRs without CFRs become forgotten spreadsheets.

Step 5: Check vertical alignment

Doerr's "cascading" principle: team OKRs should visibly connect to company OKRs. Flag any team OKR that doesn't trace to a company-level objective.

Step 6: Flag missing baselines

"You'll need a baseline for this KR. Who owns this metric and can pull the current number?"

Anti-Patterns

1. Output-based Key Results Bad: "Launch new onboarding flow by March 31" Good: "Increase onboarding completion rate from 45% to 70%" Shipping is activity. Outcomes are results.

2. Treating aspirational OKRs as committed Bad: Team marks 70% attainment as failure because "we didn't hit it." Good: For aspirational OKRs, 70% = success. Recalibrate at quarter end, don't punish stretch.

3. Too many Objectives Bad: 5-7 Objectives per team. Good: 1-3 Objectives max. Doerr: "A few well-chosen OKRs send a clear message about what we say no to."

4. No baseline Bad: "Improve conversion rate to 10%" Good: "Improve conversion rate from 6% to 10%"

Quality Checklist

  • OKR type stated: committed or aspirational
  • Objective is inspirational and qualitative (not a task)
  • 3-5 Key Results per Objective
  • Each KR has baseline and target
  • KRs are outcome-based, not output-based
  • CFR check done: conversation, feedback, recognition defined
  • Team OKRs connect to company OKRs
  • Missing baselines flagged with owners

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Rate any product, feature, or experience on the 11-star scale (Brian Chesky's Airbnb thought experiment). Use when user says "rate this experience", "11-star", "star rating", "experience audit", "how good is this", "experience rating", "product audit", "quality assessment", or wants to evaluate product quality and identify improvement paths. Also trigger when user wants to benchmark a feature, assess where a product stands, or map out what "great" looks like - even if they don't explicitly say "11-star".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

qa-aman/claude-skills212026년 10월 19일 업데이트

Generate A/B copy variants grounded in Eugene Schwartz's awareness and market-sophistication stages and John Caples' tested-headline discipline. Every variant declares its angle, the awareness stage it targets, and a falsifiable hypothesis, and the skill recommends which pair to test first and what delta counts as signal. Use when the user says "A/B test this", "write variants", "give me options", "test different angles", "copy variants", "ab copy", "test this headline", "multiple versions", "which version is better", or wants to test copy before publishing. For reviewing copy that already exists, see copy-review. For sample size and stopping rules, see growth-experiment. For diagnosing a page rather than its words, see page-cro. For full paid ad sets by platform, see ad-campaign-writer.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

qa-aman/claude-skills212026년 10월 19일 업데이트

Design statistically rigorous experiments to test data science hypotheses. Use when the user says "design an A/B test", "run an experiment", "test this hypothesis", "is this difference significant", "how many samples do I need", "randomized controlled trial", "causal inference", "uplift test", "holdout group", "significance test", "power calculation", "avoid p-hacking", or needs to determine whether an observed effect is real before making a product or model decision. For lean build-measure-learn product experiments without the statistics, use experiment-design instead.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

qa-aman/claude-skills212026년 10월 19일 업데이트

Write measurable acceptance criteria for requirements or user stories. Use when the user says "write acceptance criteria", "definition of done", "how do we test this", "fit criteria", "given when then", "Gherkin scenarios", "what does done look like", "testable conditions", "how will we know this works" - even if they don't explicitly say "acceptance criteria".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

qa-aman/claude-skills212026년 10월 19일 업데이트

Build a strategic account plan for winning, retaining, or expanding a named account. Use when the user says "build an account plan", "strategic account planning", "how do I grow this account", "account expansion strategy", "whitespace analysis", "QBR prep", "key account review", "map the stakeholders in this account", "land and expand plan", "how do I break into [company]", or wants a structured strategy for a specific account.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

qa-aman/claude-skills212026년 10월 19일 업데이트

Write paid ad copy for LinkedIn, Google, Meta, and YouTube. Produces multiple variants per platform, each targeting a different Eugene Schwartz awareness level and Cialdini persuasion principle. Use when the user asks for ad copy, ad variants, "write LinkedIn ads", Google ads, Meta ads, paid social copy, ad headlines, or wants creative for a paid campaign. Reads brand voice, ICP, and positioning from knowledge/. For organic social posts, see linkedin-post or social-calendar. For the landing page the ad points at, see landing-page-writer. For testing variants, see ab-copy-writer.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

qa-aman/claude-skills212026년 10월 19일 업데이트

qa-aman의 스킬 모두 보기

이 스킬의 문제 신고