AI Marketplaces Leaderboard

okrdev

ChatGPT plugin

OKRs as files, with a coach

View in ChatGPT directory
Featured
No

not on the featured shelf

Movement

From our daily snapshots over the last 30 days.

Rank by placement

#4931of 6,02231places up24h—7d
#4,902#4,991#5,080#5,169Sep 13Sep 19Sep 25Oct 1Oct 7Oct 12

Rank in Productivity

#1018of 1,3715places up24h—7d
#1,014#1,029#1,044#1,059Sep 13Sep 19Sep 25Oct 1Oct 7Oct 12

In its category

How this plugin compares with others in the same category. Positions are counted within the category, not across the whole directory.

Productivity1,018th of 1,371 by placement
#PluginPosition7d
1015Akinator#4926—
1016Yaps Dictation#4929—
1017Unreal Engine Skills for Codex#4930—
1018okrdevThis page#4931—
1019Career Command Center#4935—
1020Codex Cost#4937—
1021Hype Design Production#4940—

All 1,371 Productivity plugins

okrdev turns OKRs into markdown files in your own repository and puts an AI coach beside them. The coach checks new work against your key results before it starts, pre-drafts the weekly check-in from git history and merged pull requests, and parks distractions instead of letting them become this week's work.

It installs on an adoption ladder and never installs a level you did not ask for. Level 0 is a parking lot and takes ten minutes. Level 1 adds a mission, cycle objectives, check-ins and a scored retro. Level 2 adds collaboration rails for teams shipping through pull requests.

The coach never blocks. It classifies, it argues, and when you overrule it, it logs the judgment call with your reason so the next planning session has a record instead of a memory.

No MCP servers, no telemetry, no account, no network calls of its own. Everything it produces is a file in your repository, under your git history and your access control. Delete the okrdev directory and the marked block in your agent instructions file, and it never existed.

Example prompts

  • “install okrdev in this repo”

Skills

  • checkin

    Run the weekly okrdev check-in — pre-drafts the confidence table, "what moved" from git and merged PRs, the drift check, and health metrics before the humans arrive, then walks them through the parts only they can do. Use when someone says "run our check-in", "weekly check-in", "let's do the OKR check-in", "time for the checkin", when a check-in is overdue and the user agrees to catch up, or when a single DRI wants to file their async contribution to this week's check-in.

  • coach

    On-demand status and alignment check from the okrdev coach — confidence trends, drift since the last check-in, health metrics, open-PR status in plain language, and side-quest/maintenance/emergency budget usage. Use when someone asks "how are we doing", "where do we stand on the OKRs", "is this aligned?", "should I build this?", "what should I work on today?", "what's drifting", "any red flags this week", or wants a mid-week pulse without running a full check-in.

  • install

    Install, upgrade, or level-up okrdev in the current repo. Walks the adoption ladder — Level 0 parking lot, Level 1 method, Level 2 collaboration rails, optional stack module — creating okrdev/ files from templates, appending the marked coach block to the host agent's instructions file (CLAUDE.md or AGENTS.md), and merging (never overwriting) anything that already exists. Use when someone says "install okrdev", "set up okrdev", "add okrdev to this repo", "upgrade okrdev", "move us to Level 1/2", or asks how to get started with okrdev.

  • park

    Capture an idea into the okrdev parking lot in ten seconds — one line, energy, effort, done — then get back to work. Use when the user says "park this", "park that idea", "add it to the parking lot", "idea for later", "don't let me forget", or when a mid-session idea is about to turn into mid-session work.

  • plan

    Draft, pressure-test, and activate a cycle of OKRs — 1–3 objectives with measurable key results, one DRI each, and health metrics — written to okrdev/okrs/<cycle>.md. Use when someone wants to plan the next cycle or quarter, set or draft OKRs, start okrdev Level 1, restart after a finished or abandoned cycle, or asks "what should our objectives be?"

  • retro

    Score a finished OKR cycle against the rubric, challenge inflated and sandbagged scores, extract three lessons into okrdev/LESSONS.md, and close the cycle as scored (or abandoned). Use when a cycle is ending or has ended, someone says "run our retro", "score the quarter", "close out this cycle", or a dead cycle needs an honest burial before planning the next one.

  • side-quest

    Sanction a distraction on the spot — time-box it, log it in the parking lot, and note what the human is stepping away from. Use when someone wants to chase an off-OKR idea right now ("I know it's not a KR but I want to build this today"), says "side quest", asks to spend an afternoon on something off-plan, wants to extend or close a running side quest, or asks how much side-quest budget is left this week.

  • triage

    Walk every parked idea — open okrdev:parked GitHub issues plus the parking lot's Captured section — to a decision (promote, archive, or side-quest with a time-box); then check the side-quest budget. Use when the user says "triage the parking lot", "triage the parked issues", "go through my parked ideas", "clean up the ideas list", or as the parking-lot step of a weekly check-in.

Categories
Made by
Alexander Ashley Chisholm · Website
Sign-in
On Install
Capabilities
skills
Availability
Available
Version
0.8.4
Keywords
okr, objectives, key-results, goals, planning, check-ins, retrospective, prioritization, focus, project-management
Created
August 10, 2026
More info