Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
nexu-io avatar

Team Okrs

  • 236 installs
  • 83.7k repo stars
  • Updated August 5, 2026
  • nexu-io/open-design

team-okrs is a Claude Code skill that helps engineering and product leads define quarterly team objectives and measurable key results, align owners, and document tradeoffs before execution sprints begin.

About

team-okrs is an open-design planning skill for engineering teams preparing a quarter of focused delivery. The skill structures quarterly objectives with measurable key results, assigns owners, and surfaces tradeoffs so sprint planning starts from shared priorities instead of ad hoc tickets. Engineering managers and tech leads reach for team-okrs when a new quarter begins or when roadmap drift requires resetting measurable goals before agents or developers commit to implementation work. team-okrs produces documented OKR artifacts suitable for sprint kickoffs, stakeholder reviews, and cross-team alignment sessions rather than code or infrastructure changes.

  • Objective and KR framing
  • Owner alignment
  • Measurable outcomes
  • Quarterly planning cadence

Team Okrs by the numbers

  • 236 all-time installs (skills.sh)
  • +1 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Ranked #976 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/nexu-io/open-design --skill team-okrs

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs236
repo stars83.7k
Last updatedAugust 5, 2026
Repositorynexu-io/open-design

How do you write quarterly OKRs for an engineering team?

Define quarterly team objectives and measurable key results, align owners, and document tradeoffs before execution sprints begin.

Who is it for?

Engineering managers and tech leads setting quarterly measurable goals before sprint planning or agent-driven implementation.

Skip if: Solo developers writing application code who need no team alignment artifacts or quarterly planning structure.

When should I use this skill?

The user asks to define team OKRs, quarterly objectives, key results, owner alignment, or pre-sprint goal tradeoffs.

What you get

Quarterly objectives list, measurable key results per objective, owner assignments, and tradeoff documentation.

  • Quarterly OKR document
  • Owner assignment matrix
  • Tradeoff decision log

Files

SKILL.mdMarkdownGitHub ↗

Team OKRs Skill

Produce a single-screen OKR tracker.

Workflow

1. Read DESIGN.md. 2. Layout:

  • Quarter banner: Q4 FY25, dates, overall progress chip.
  • Three objective cards. Each has:
  • Objective title + owner avatar + status pill (On track / At risk / Off track)
  • 3 key results, each a row with metric / current → target / progress bar
  • Right sidebar: at-a-glance KPIs, top movers, blockers callout.

3. Clear progress visualisation, calm palette, one accent.

Output contract

<artifact identifier="okr-q4" type="text/html" title="OKRs Q4">
<!doctype html>...</artifact>

Related skills

FAQ

What does team-okrs produce?

team-okrs produces quarterly team objectives, measurable key results with assigned owners, and documented tradeoffs so engineering sprints start from aligned, outcome-based goals.

When should engineering teams use team-okrs?

Use team-okrs at quarter start or when roadmap drift requires resetting measurable goals, before sprint planning or agent-driven implementation commits to work items.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.