agentleFS
qyndexqyndex/claude-init/.claude/skills/okr-align/SKILL.md

okr-align

Skill2 starsChanged 5 months agoMITView on GitHub

Check that a spec or initiative aligns with a current-quarter OKR. Run automatically during /specify (Phase 2) and /initiative create. Flags work that has no KR backing.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every spec and initiative must declare which KR it serves.

    line 13
  2. Very specific:

    Read the target artifact (specs/active/<id>.md or initiatives/active/<id>.md).

    line 17
  3. Very specific:

    Read OKRs.md to enumerate current-quarter KRs.

    line 18
  4. Distinctive:

    Check the artifact's frontmatter:

    line 19
  5. Distinctive:

    Don't auto-assign a KR: Always surface for human confirmation.

    line 66
  6. Distinctive:

    Closed-KR alignment is invalid: If a spec aligned to KR-2026Q2-* that's now closed, prompt the user to either close the spec or re-align.

    line 68

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.

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

OKR Align

Every spec and initiative must declare which KR it serves. This skill is the alignment gate.

Process

  1. Read the target artifact (specs/active/<id>.md or initiatives/active/<id>.md).
  2. Read OKRs.md to enumerate current-quarter KRs.
  3. Check the artifact's frontmatter:
    • Spec: objective: KR-<QYYYY>-<NN> (required for non-trivial specs)
    • Initiative: KR linked in ## Strategic context
  4. Surface mismatches:
    • Missing field
    • KR ID doesn't exist in current quarter
    • KR is closed/superseded
  5. Recommend next action:
    • "Add objective: KR-2026Q3-04 to spec frontmatter"
    • "Propose a new KR in next quarter's cut" (if work is opportunistic but valid)
    • "Defer this spec until aligned with a future KR"

What's exempt

  • Bug fixes ≤ 20 LOC (per CLAUDE.md §VIII)
  • Security patches (always urgent; KR-tagged retroactively)
  • Compliance-driven work (use KR-COMPLIANCE synthetic tag)
  • Platform / infra work that serves multiple KRs (use KR-PLATFORM synthetic tag)

Output

OKR alignment check — spec 042
- objective: KR-2026Q3-04 ✓ (matches "Checkout failure rate 2.1% → 0.5%")
- KR owner: @alex (matches initiative 037 sponsor)
- KR status: active
- Verdict: ALIGNED

Initiative 042
- KR: KR-2026Q3-01 ✓
- KR-2026Q3-02 ✓
- KR-2026Q3-03 ✓
- Verdict: ALIGNED (3 KRs)

Mismatch example:

OKR alignment check — spec 058
- objective: missing
- Suggested KRs based on spec body:
  - KR-2026Q3-06 (tech debt) — confidence 70%
- Verdict: NEEDS-ALIGNMENT
  Recommend: edit specs/active/058-foo.md frontmatter → `objective: KR-2026Q3-06`

Hard rules

  • Don't auto-assign a KR. Always surface for human confirmation.
  • Synthetic tags (KR-COMPLIANCE, KR-PLATFORM) require a one-line rationale in the spec.
  • Closed-KR alignment is invalid. If a spec aligned to KR-2026Q2-* that's now closed, prompt the user to either close the spec or re-align.

Hook

This skill is invoked automatically by:

  • /specify (Phase 2 of 8-phase workflow) — gates spec approval
  • /initiative create (gates initiative activation)
  • /roadmap cut (validates all NOW items)

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.