okr-tracking
Skill1 starsChanged 5 months agoMITView on GitHub
Draft and track OKRs — objectives with measurable key results, current values, and confidence/health. Use when the user says "write OKRs", "set objectives and key results", "track our OKRs", "quarterly goals", "are we on track for our KRs", or needs to define or check progress on measurable goals.
In this repository18 other files it gives its agents.
- capacity-planningSkill
- decision-logSkill
- dependency-mappingSkill
- escalationSkill
- estimation-sizingSkill
- exec-summarySkill
- launch-readinessSkill
- postmortemSkill
- prd-reviewSkill
- program-health-dashboardSkill
- project-charterSkill
- raid-logSkill
- release-notesSkill
- retrospectiveSkill
- roadmap-planningSkill
- sprint-planningSkill
- stakeholder-comms-planSkill
- status-reportSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
Write the objective — memorable, directional, for this cycle.
- Distinctive: line 24
Write 2–4 KRs, each with metric, baseline, target, and source of truth.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
OKR Tracking
Help teams write OKRs that are ambitious and measurable, and track them honestly through the quarter.
When to use
- Drafting objectives and key results for a quarter/cycle.
- Reviewing/updating OKR progress and confidence.
Principles
- Objective = qualitative, inspiring, time-bound direction ("Become the default tool for X").
- Key Result = quantitative and verifiable — a number that moves, not a task ("Increase activation from 40%→60%"). If you can't measure it, it's not a KR.
- 1 objective : 2–4 key results. Avoid task-lists masquerading as KRs.
- KRs should be outcomes, not output/deliverables ("ship feature" is a task, not a KR).
- Set a baseline → target; stretch is healthy (≈70% attainment is often "good").
Process — drafting
- Write the objective — memorable, directional, for this cycle.
- Write 2–4 KRs, each with metric, baseline, target, and source of truth.
- Pressure-test: is each KR measurable, outcome-based, and influenceable by this team?
Process — tracking
- For each KR: current value, % to target, and a confidence (🟢 on track / 🟡 at risk / 🔴 off track).
- Note what's driving the number and the next action for at-risk KRs.
- Give the objective an overall health roll-up.
Output format
## Objective: {{O}} — Overall: 🟢/🟡/🔴
| KR | Baseline | Target | Current | % to target | Confidence | Notes / next |
| --- | --- | --- | --- | --- | --- | --- |Flag any KR that's really a task, and any objective with no measurable KR.
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.

