agentleFS
Sign inStart free
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/okr-builder/SKILL.md

okr-builder

Skill1 starsChanged 24 days agoMITView on GitHub

Converts strategy into quarterly objectives and key results when teams need focused goals, clear owners and a review rhythm.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 5

    Distinctive

    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
  1. Distinctive:

    Use at the start of a quarter or planning cycle, after a strategy is agreed, or when teams are busy but outcomes are unclear.

    line 9
  2. Distinctive:

    Write two to four key results per objective, each with a baseline, target and date.

    line 20
  3. Distinctive:

    Check cross-team dependencies and capacity, and cut goals that cannot be resourced.

    line 23
  4. Distinctive:

    Every key result can be measured from an existing or planned data source

    line 30
  5. Distinctive:

    Every objective links to a stated strategic priority

    line 31

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

OKR Builder

When to use it

Use at the start of a quarter or planning cycle, after a strategy is agreed, or when teams are busy but outcomes are unclear.

What Claude needs

  • client-context.md for business background
  • Agreed strategy, priorities or roadmap
  • Current performance data and baselines
  • Team structure and capacity
  • Existing goals or targets

Method

  1. Choose no more than three to five objectives that link directly to stated strategic priorities.
  2. Write two to four key results per objective, each with a baseline, target and date.
  3. Separate outcome key results from activity tasks, and move tasks into initiatives.
  4. Assign one accountable owner per objective and per key result.
  5. Check cross-team dependencies and capacity, and cut goals that cannot be resourced.
  6. Set a weekly check-in format, a mid-quarter review and an end-of-quarter scoring rule.

Output format

Provide an OKR table (objective, key result, baseline, target, owner, data source), linked initiatives, dependency notes and the review calendar.

Quality checks

  • Every key result can be measured from an existing or planned data source
  • Every objective links to a stated strategic priority
  • Total commitments fit stated team capacity

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free