Use okr-cascade

Cascade company OKRs to team-level OKRs

Cascade company OKRs to team-level OKRs — with a gap registry for objectives no team credibly owns, and a causal metric tree connecting each team KR to the north-star it's supposed to move.

Reach for it when the user wants to set or cascade OKRs, align team goals to company goals, "turn strategy into quarterly objectives", or audit existing OKRs for gaps and vanity metrics.

Install it

npx skilldrop-cli install okr-cascade                 # Claude Code, your user folder
npx skilldrop-cli install okr-cascade --project       # Claude Code, this repo
npx skilldrop-cli install okr-cascade --ide cursor    # or kiro, codex, antigravity, copilot

It is part of the Product manager pack: --pack product-manager installs it with its neighbours.

Ask for it

Say it the way you would to a colleague. Requests like these route to it:

• "Cascade our company OKRs down to team level"
• "Help me set quarterly OKRs for the platform team that align to company goals"
• "Audit our existing OKRs — which ones are vanity metrics?"
• "Leadership set five objectives; which have no team owner?"
• "Turn our strategy into Q4 objectives for the org"

Requests like these belong to a different skill, so it shouldn't answer them:

• "How do we know this feature worked? Define its success metrics"
• "Prioritize our sprint backlog for next iteration"
• "Run a SWOT on our market position"

If another skill answers instead, ask for this one by name: "use okr-cascade".

Check what you get

A good result:

• Company OKRs appear verbatim, and every restated one is marked as restated with the reason.
• Every team KR has its causal sentence naming the company KR it feeds and the mechanism. "Aligns with company goals" is not a mechanism.
• Every team KR is scorable 0.0–1.0 and measurable at the team's own scope. Binary deliverables are tasks — they can live under a KR, not as one.
• Output KRs are flagged at every level, each with the outcome it presumably serves.
• The gap registry is present and ranked — even when its honest content is "none found; here's why that's suspicious".
• The metric tree has one north-star, and every KR is attached, labeled guardrail, or explicitly cut.

Use something else when

• Measuring one feature's success — success-metrics (it declares org OKRs out of scope; this skill returns the favor)
• No strategy exists to cascade — strategy-analysis or prfaq first
• Sprint/backlog prioritization — OKRs are aims, not a work queue
• Individual performance goals — cascading OKRs to persons turns a steering tool into a rating tool, and both break

Next

• SKILL.md, the instructions the agent reads
• Its page on the site
• Related: prfaq, strategy-analysis, success-metrics

Edit this page on GitHub · View source