review-okrs
Skill1 starsChanged 3 months agoMITView on GitHub
Run an OKR check-in or end-of-cycle review — pull current values, grade each key result, assess confidence, and capture learnings to carry forward. Use mid-cycle or at cycle end. Dispatches the product-strategist with the product-analyst.
In this repository30 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- build-business-caseSkill
- build-roadmapSkill
- capture-feedbackSkill
- close-projectSkill
- coordinate-programSkill
- define-metricsSkill
- define-strategySkill
- design-dashboardSkill
- elicit-requirementsSkill
- groom-backlogSkill
- make-deliverableSkill
- manage-changeSkill
- manage-resourcesSkill
- plan-capacitySkill
- plan-launchSkill
- plan-portfolio-automationSkill
- plan-projectSkill
- plan-sprintSkill
- powerbiSkill
- prioritizeSkill
- review-portfolio-intakeSkill
- run-ceremonySkill
- run-discoverySkill
- run-gate-reviewSkill
- setup-pmoSkill
- track-financialsSkill
- track-portfolioSkill
- track-statusSkill
- write-prdSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 28
Use templates/okr.md as the structure for the graded OKR tables.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/review-okrs — Close the goals loop
When to use
Mid-cycle OKR check-in, or end-of-cycle grading before setting the next cycle's objectives.
Dispatches
product-strategist (lead) + product-analyst (pull actuals, validate metric definitions).
Inputs
knowledge/product-context.md (current OKRs), the metrics catalog/actuals, prior review notes.
Steps
- For each key result, pull the current value vs. baseline and target; update the OKR table.
- Grade each KR (e.g., 0.0–1.0) and the objective overall; set/update confidence.
- Diagnose: what's driving over/under-performance? Was the KR the right outcome measure?
- Capture learnings and decide carry-forward: keep / adjust / drop, and what changes next cycle.
- Flag any strategy implications (a missed objective may mean re-examining the bet, not just trying harder).
Methods
knowledge/methods/product-strategy.md (OKRs), knowledge/methods/metrics-and-experimentation.md.
Output
Use templates/okr.md as the structure for the graded OKR tables. Updated OKRs in
knowledge/product-context.md with grades/learnings; log the review outcome and any
strategy implications to knowledge/decision-log.md. Feeds /define-strategy for the next cycle.
Follow standards/document-standards.md.
Created by Colin Beck<br>
LinkedIn: https://www.linkedin.com/in/beckcolin/<br>
GitHub: https://github.com/link7373
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

