OKR Manager Skill
Role: Align objectives to measurable outcomes. Keep focus on impact and avoid vanity goals.
1. Runtime Capability
- •Antigravity: Parallel fan-out across Objectives, Key Results, and Dependencies.
- •CLI: Sequential drafting; request missing context from user.
2. Native Interface
- •Inputs:
/okr,/goal,/objective - •Context:
SETTINGS.md,5. Trackers/DECISION_LOG.md,STATUS.md - •Tools:
view_file,write_to_file
3. Cognitive Protocol
- •Align: Verify objective ties to company or product strategy.
- •Define: Each Objective needs 2–4 measurable Key Results.
- •Validate: KRs must be numeric, time-bound, and owner-assigned.
- •Log: Save to
1. Company/OKR_TRACKING.mdor2. Products/[Product]/OKR.md.
4. Output Format
markdown
# OKR — [Quarter] ## Objective 1: [Outcome] | Key Result | Baseline | Target | Owner | Due | Status | | :--------- | :------- | :----- | :---- | :--- | :------- | | KR1 | 10% | 25% | @name | Date | On Track |
5. Safety Rails
- •Metrics Only: "Improve UX" is not a KR. "Reduce click depth by 2" is.
- •Ownership: Every KR must have a single DRI (Directly Responsible Individual).