okr-planner — Claude Code skill: OKR tables as an Excel workbook
okr-planner splits a team's goals into measurable objectives and key results, then hands back an Excel workbook with an alignment sheet and a review log.
Apache-2.0 ★ 12,746 updated 2026-10-29
npx skills add genspark-ai/genoffice --skill okr-planner -a claude-codeWhat okr-planner does
The skill takes a team direction or a heap of goals and turns them into an OKR table. It opens with three questions: which cycle, which team level, and whether a parent OKR already exists. Where a parent exists, every objective has to map onto one of its key results.
Objectives stay qualitative, 3–5 of them, with no numbers inside. Work items such as shipping a feature get pulled out of the objectives and moved into key initiatives under a KR. Each objective carries 2–4 key results with a metric, baseline, target and deadline. Ask for a baseline you cannot give and the cell says “baseline pending” rather than a made-up figure.
Output is an Excel workbook with three sheets: OKR, Alignment, and a review log for weekly check-ins. Progress is a formula over baseline and target, confidence uses a 1–10 validation list, and each key result has exactly one owner. The reply carries review notes instead of repeating the table: which KRs describe tasks, where goals collide. The cap is 5 objectives and 15 key results per team and cycle.
What it helps with
- turn a team direction into an OKR table
- test whether existing OKRs are measurable
- separate outcome KRs from delivery tasks
- map department objectives onto parent key results
- build a weekly review log for OKR check-ins
Example prompts for the agent
- Turn these team goals into this quarter's OKR table
- Check whether this set of OKRs is measurable
- Build the OKR workbook for the platform squad and list the baselines I still need to supply
How to install okr-planner
1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill okr-planner -a claude-code2Manually: put the files in place
~/.claude/skills/okr-planner/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/okr-planner/
1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill okr-planner -a codex2Manually: put the files in place
.agents/skills/okr-planner/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill okr-planner -a cursor2Manually: put the files in place
.cursor/skills/okr-planner/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install genspark-ai/genoffice skills/recommended/okr-planner2Manually: put the files in place
.github/skills/okr-planner/SKILL.md1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill okr-planner -a gemini-cli2Platform CLI
gemini skills install https://github.com/genspark-ai/genoffice --path skills/recommended/okr-plannerManually: put the files in place
.devin/skills/okr-planner/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about okr-planner
How do I install okr-planner in Claude Code?
Run npx skills add genspark-ai/genoffice --skill okr-planner -a claude-code. The skill then sits at ~/.claude/skills/okr-planner/SKILL.md.
What does okr-planner do?
It distils team goals into objectives and key results, then delivers an Excel workbook with OKR, Alignment and Review log sheets. Review comments come back in the reply.
Does it fill in baselines for me?
No. Missing baselines are marked “baseline pending”, and the skill lists the ones you still need to supply.
Source text
SKILL.md · Apache-2.0
--- name: okr-planner description: Break team goals into a measurable Objectives and Key Results table with a review note, delivered as an Excel workbook category: business scenarios: OKR setting | Quarterly goals | Goal alignment quickPrompts: Turn these team goals into this quarter's OKR table | Check whether this set of OKRs is measurable metadata: version: 1.0.0 --- You are an OKR specialist. The user gives you a team direction, annual goals or a pile of things they want to do; you deliver a structured OKR table and a review note. ## Workflow 1. Ask first about the cycle (quarter / half-year), the team level (company / department / squad), and whether a parent OKR or strategic direction already exists. When a parent OKR exists, every O must map to one of its KRs. 2. Distil the Objectives: find 3-5 directional goals in the material, each O a single ambitious qualitative sentence with no numbers. Tasks such as "build feature X" are pulled out of the Os and placed under KRs as key initiatives. 3. Break out the Key Results: 2-4 KRs per O, each with a metric + baseline + target + deadline. When the user cannot give a baseline, mark "baseline pending"; never invent numbers. 4. Separate outcome KRs (users, conversion rate, NPS) from output KRs (launch, delivery). When every KR under an O is output-type, warn the user and suggest swapping at least one for an outcome KR. 5. Build the workbook as an Excel workbook with the spreadsheet tools available here. Title it "<Team> YYYY QN OKR". 6. After delivering, give review comments in the reply: which KRs are tasks rather than results, where there are too many or conflicting goals, and what to cut or merge. ## Workbook structure - Sheet "OKR", columns: # / Objective / Key Result / Metric definition / Baseline / Target / Current / Progress / Owner / Confidence (1-10) / Updated / Key initiatives. - Progress is a formula, (Current - Baseline) / (Target - Baseline), in percentage format, never typed. - Sheet "Alignment": this level's O mapped to the parent KR, one pair per row. - Sheet "Review log": Date / KR # / Change / Risk / Next step, a five-column empty table for weekly check-ins. - O rows bold with a fill colour; the Confidence column has 1-10 data validation; the Owner column holds exactly one person per KR. ## Rules - One team, one cycle: no more than 5 Os and no more than 15 KRs in total; beyond that, suggest prioritising. - KRs never use unquantifiable words such as "improve" or "strengthen". A KR that is certain to hit 100% means the target is set too low; point that out. - Confidence is the owner's subjective score; the first draft leaves it blank or shows an example value, never filled in for the user. - Whether OKRs tie to performance reviews follows company policy; give no conclusive recommendation. - When the user's goals mix several teams, split them first and build a table per team; never stuff different teams' KRs into one O. - "Hold steady" metrics (such as 99.9% system availability) can be KRs but are labelled as guardrail rather than growth KRs. ## Output One Excel workbook (OKR / Alignment / Review log, three sheets). The reply holds the review comments and the list of baselines the user still needs to supply, not a restatement of the table.
© genspark-ai · Apache-2.0 · genspark-ai/genoffice