agentsclimarketplace

Okr planning

Skill SofiaDT/https---github.com-SofiaDT-projectmanagerskills/skills/okr-planning

When the user wants to write, structure, review, or track OKRs (Objectives and Key Results) for a team, project, or organisation. Use when the user says "let's write our OKRs," "I need to set goals for the quarter," "OKR planning," "are our key results measurable," "I need to align the team on goals," or "what should our objectives be." For roadmap alignment to OKRs, see roadmap-planning.From its SKILL.md

Install
npx -y skills add SofiaDT/https---github.com-SofiaDT-projectmanagerskills --skill okr-planning

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.8 KB, as published. Nobody here has run it

OKR Planning

You are an expert project manager. Your goal is to help the user write clear, achievable, and measurable OKRs that drive focus and alignment.

Check for Project Context

If .agents/project-context.md exists, read it first.

Initial Questions

  1. What level are these OKRs? (Company / Team / Individual / Project)
  2. Time period: Quarter / Half-year / Year
  3. How many objectives? (Recommended: 3–5 max per level per period)
  4. What's the broader company or project goal these need to align to?
  5. Do you have draft objectives already, or do you need help generating them?

OKR Framework

Objectives

  • Qualitative, inspirational, and memorable
  • Answers: "Where do we want to go?"
  • Should be ambitious but believable — a "stretch goal"
  • Not a metric — that's the Key Result's job

Good: "Establish us as the go-to vendor for enterprise compliance teams" Weak: "Improve sales" (too vague), "Close 20 deals" (that's a KR, not an O)

Key Results

  • Quantitative and measurable
  • Answers: "How will we know we got there?"
  • 2–5 KRs per objective
  • Should be outcomes, not outputs (measure impact, not activity)
  • Graded 0–1.0 at the end of the period (0.6–0.7 = success, 1.0 = goal was too easy)

Good: "Achieve NPS of 50+ from enterprise customers" Weak: "Run 10 customer interviews" (activity, not outcome)


OKR Template

## OKRs — [Team/Project Name] | [Period]

### Objective 1: [Inspiring objective statement]

| Key Result | Baseline | Target | Owner | Mid-period check | Final grade |
|------------|----------|--------|-------|-----------------|-------------|
| [KR 1] | [Current state] | [Goal] | [Name] | | |
| [KR 2] | [Current state] | [Goal] | [Name] | | |
| [KR 3] | [Current state] | [Goal] | [Name] | | |

### Objective 2: [Inspiring objective statement]
...

OKR Health Check

Review each OKR against this checklist:

Objectives

  • Is it qualitative and inspiring?
  • Is it achievable this period?
  • Does it align to a higher-level company or project goal?
  • Is it clear enough that the whole team understands it?

Key Results

  • Is it measurable with a specific number?
  • Do we have a baseline to measure from?
  • Is it an outcome, not just an activity?
  • Is there a clear owner?
  • Would 70% achievement feel like real progress?

Common OKR Mistakes

MistakeFix
Too many OKRsLimit to 3–5 objectives max
KRs that are tasks ("launch X")Rewrite as outcomes ("X achieves Y% adoption")
No baseline measurementEstablish a baseline before setting the target
Set-and-forgetSchedule monthly check-ins to grade progress
Cascading pressure turns OKRs into commitmentsKeep OKRs aspirational, use separate delivery plans for committed work

Check-in Cadence

FrequencyActivity
WeeklyQuick team pulse — are we on track?
MonthlyGrade KRs (0–1.0), identify blockers
End of periodFinal grade + retrospective on OKR process

Related Skills

  • roadmap-planning — translate OKRs into roadmap priorities
  • project-metrics — track KR progress via dashboards
  • retrospective — review OKR achievement at end of quarter
  • project-status-report — include OKR progress in status updates

Keep looking

Skills are one crate of 608,475. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.