okr-goal-setting-wasp-drone — Claude Code subagent
okr-goal-setting-wasp-drone — a subagent for writing, auditing, and scoring OKRs grounded in Grove and Doerr methodology.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install business-and-product-tools@wasp-nestWhat okr-goal-setting-wasp-drone does
okr-goal-setting-wasp-drone is an OKR methodology specialist embedded in Claude Code and Codex. It drafts Objectives (aspirational directions) and Key Results (measurable outcomes), surfaces whether ambition is missing or targets overshoot, rewrites KRs to measure outputs instead of effort—the most frequent failure mode—and grades cycles honestly.
The subagent is grounded in Andy Grove's MBO discipline at Intel and John Doerr's "Measure What Matters" framework. It separates OKRs from KPIs (leading vs. lagging signals) and from MBOs (aspirational vs. compensation-linked goals). It sets up quarterly rhythms without bureaucratic drag, adapts the framework for small teams, and orients you in tools like Lattice, 15Five, Weekdone, and Notion—but stops at company strategy and engineering roadmap ownership.
One critical feature: it runs a fit check. Many early-stage teams see more value in weekly priorities than quarterly OKR overhead. Doerr acknowledges this trade-off, and honest assessment beats forced adoption.
What it helps with
- draft aspirational Objectives and measurable Key Results for the quarter
- audit existing OKRs: separate real OKRs from KPI-washing and goal-setting theater
- rewrite input-metric KRs into output-metric KRs so you measure results, not activity
- assess whether OKRs fit your team size and stage or a lighter framework would serve better
- calibrate ambition level and launch a quarterly check-in cadence
Example prompts for the agent
- Write OKRs for Q1: our video editor team wants to triple active users and ship collaboration features
- Audit these OKRs: are they ambitious enough or are we sandbagging?
- Rewrite the Key Results: they describe work, not outcomes
How to install okr-goal-setting-wasp-drone
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install business-and-product-tools@wasp-nest2Manually: put the files in place
.claude/agents/okr-goal-setting-wasp-drone.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/okr-goal-setting-wasp-drone.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/okr-goal-setting-wasp-drone.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about okr-goal-setting-wasp-drone
How do I install okr-goal-setting-wasp-drone in Claude Code?
Run /plugin marketplace add legioncodeinc/vibe-coding-tools, then /plugin install business-and-product-tools@wasp-nest and reference .claude/agents/okr-goal-setting-wasp-drone.md. For Codex, use .codex/agents/okr-goal-setting-wasp-drone.toml.
What does okr-goal-setting-wasp-drone do?
It guides you through writing and scoring OKRs using Grove and Doerr canon, rewrites Key Results from input metrics to output metrics, calibrates the ambition-to-achievability ratio, sets up quarterly review rituals, and recommends whether OKRs reduce overhead or add it for your stage.
How do OKRs differ from KPIs, and why shouldn't I link them to salary?
OKRs track leading indicators (what you control); KPIs track lagging outcomes (market results). Compensation linkage breaks honest scoring—Grove and Doerr both warn against it. The goal is ambitious target-setting without fear of penalty.