OKR System

Plan aligned objectives from company to team to person with a fixed review cadence. The skill recommends up to three key results per objective. It builds empty goal-tracking templates on request.

The skill separates advice, review, conversion and build requests before producing artifacts. Advice receives a short recommendation and an offer of a relevant build. An explicit build request proceeds once essential missing facts are resolved. It asks one question at a time, reuses answers already supplied and stops when further answers would not change the deliverable. Unknown information remains unknown rather than receiving invented values.

Use it for an OKR tracker, goal-setting template, objective-and-key-result sheet or company goals register. Define owners, measurement, ambition, visibility and review timing before building.

It does not assess individual performance or connect goals to compensation. Objectives should have key results and a review date at creation rather than waiting for a later completeness review. The skill does not calculate payroll, tax, leave balances or KPIs. Automation, reminders and synchronization require an integration layer. Legal, tax and HR review is required before templates drive real decisions.

The workflow is objective, key results, owner, progress update, review and close. Inputs establish how many objectives are needed, whether the starting level is company or team, and whether goal setting, tracking or reporting is the deliverable. Its 20 fields include Objective, Department, End Date, three key-result descriptions and their individual progress percentages, Last Updated, Level, Notes, OKR ID, Owner, Parent OKR, overall Progress %, Quarter, Start Date, Status and Year. Parent OKR is the relation field used for the cascade. Level options are L1 through L5, M1 and M2; statuses are Draft, Active, At Risk and Closed.

Requested artifacts can include CSV, SQL DDL, JSON Schema, Notion property mappings or an Excel workbook. The formats derive from one field list: CSV and JSON retain matching display names, while SQL uses normalized identifiers. Dates retain date types, money retains currency types and cross-table references retain relation types. Select options are a starting set that can be renamed to match the business.

One SQL example is:

CREATE INDEX idx_okr_system_status ON okr_system (status);

Templates are empty by default. Example rows are produced only on request and remain obviously synthetic. Sensitive identifiers should not be repeated unnecessarily during a requested review. Machine-readable data stays separate from explanatory prose and any material validation failures. Excel-compatible CSV uses UTF-8 with a byte order mark and accompanying guidance about number, date and currency columns. An XLSX workbook is a separate requested output rather than a renamed CSV.

The Notion output routes to notion-manual-import for CSV, property mappings, import steps and verification. Manual mappings require no connection. Requested live workspace changes require actual tool access, a verified target and authorization. Imported columns may initially be Text and need their mapped property types applied. Relation links resolve after both relevant databases are imported. A static mapping alone does not establish a completed workspace change.