Add okr-factory skill for automated OKR check-ins#91
Conversation
Resolves the user in Atlas, finds their goals, gathers evidence from GitHub PRs, Jira, Slack, and Atlas, then drafts a scored status update (on_track/at_risk/off_track) ready to post via 'ld atlas goal-update'. Registered in skills.json and README. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
Code-review follow-ups on PR #91: remove goal-update-delete references (the verb was dropped from the CLI); correct the example char-count labels (160, not 149) since the skill itself preaches counting; lower people lookup --first to 100 to stay under the server page cap. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
# Conflicts: # CHANGELOG.md # skills.json
Skill eval results
Only suites whose source actually changed since their last recorded score were re-run. Soft-failing while we stabilise the baseline. |
skills.json is generated by scripts/generate_catalog.py; the hand-edited entry diverged (stray tags, field order). Regenerated from SKILL.md frontmatter so the catalog --check passes. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
| ### OKRs & Planning | ||
|
|
||
| | Skill | Description | | ||
| |-------|-------------| | ||
| | `okr-factory` | Automate monthly/bi-weekly OKR check-ins: find your Atlas goals, gather evidence from PRs/Jira/Slack, draft a scored status update (🟢/🟠/🔴), and post it with your approval | |
There was a problem hiding this comment.
🟡 New skill category listed under installation instructions instead of the skills catalog
The "OKRs & Planning" heading is inserted as a subsection of "Install as a Claude Code Plugin" (README.md:76) instead of under the "Available Skills" section where all other skill categories live, so users scanning the skills catalog will not find it.
Impact: Readers miss the new skill when browsing the documented skill list.
Heading hierarchy creates incorrect nesting
The README heading hierarchy is:
## Available Skills(README.md:9) — contains### Feature Flags,### AgentControl,### Experiments,### Metrics## Install as a Claude Code Plugin(README.md:51) — the new### OKRs & Planning(README.md:76) falls under this h2 section## Install as a Cursor Plugin(README.md:82)
Because ### OKRs & Planning is placed after line 74 (Onboarding, which is contextually about plugin setup) and before line 82 (## Install as a Cursor Plugin), it is structurally a child of the installation section.
The CONTRIBUTING.md rule says "Update the skill list in README.md." The skill list is the ## Available Skills section. The new ### OKRs & Planning block should be moved to between line 49 (end of Metrics table) and line 51 (start of Install section) so it sits alongside Feature Flags, AgentControl, Experiments, and Metrics.
Prompt for agents
The new OKRs & Planning section (lines 76-80 in README.md) is placed as a ### heading under the ## Install as a Claude Code Plugin section. Per CONTRIBUTING.md, new skills should be added to the skill list, which is the ## Available Skills section. Move the entire block (### OKRs & Planning header + table) so it appears between the end of the Metrics table (after current line 49) and the ## Install as a Claude Code Plugin heading (current line 51). Also remove the blank lines left behind at lines 76-80 after the move.
Was this helpful? React with 👍 or 👎 to provide feedback.
|
Confirming this was the right call to close — this skill belongs in an internal repo, not the public one. It drives the private ld-tools/research CLI and references internal goals, people, and Slack. Ported to launchdarkly-labs/agent-skills (launchdarkly-internal plugin): launchdarkly-labs/agent-skills#63. |
1 participant
What
Adds the
okr-factoryskill: a one-command assistant for the monthly/bi-weekly OKR check-in that ICs are increasingly asked to do.It:
ld atlas me, or a name → AAID lookup).ld atlas tql 'owner = "<aaid>"').ld atlas goal-updateand can undo viald atlas goal-update-delete.Why
ICs are being asked to do "the paperwork of all sorts" alongside shipping. This skill turns a 45-minute, 6-tool context-switch into a 2-minute review.
Depends on
ld atlas goal-update/goal-update-delete— added in launchdarkly/research#365. (The oldld atlas updateis project-only and can't post goal scores.)Validation
Dry-run against a real IC (Dave Williams): correctly found both owned goals, pulled the right evidence (merged commercial-env tickets, 50 PRs/60d, his own Slack note on next-month focus), and produced a defensible 🟢 with risk caveats. The posting path was verified live end-to-end against a test goal (post → badge set → delete → reverted clean).
Registered in
skills.jsonand the README Available Skills table; CHANGELOG updated.🤖 Generated with Claude Code