Okr System

OKR System

What it is: Goal alignment.

Overview

Works out the smallest useful OKR System setup for the business in front of it, then builds it only when asked. The default output is a short recommendation, not a spreadsheet. Artifacts - CSV, SQL DDL, JSON Schema, Notion mapping - are produced on request, from one field list so they cannot drift apart.

Layer: Layer 4: Manage. Fits: Growth stage. Table code: n/a.

When to Use This Skill

• okr tracker
• goal setting template
• objective key result sheet
• company goals tracker

Also use it when the user says "goal alignment", or describes the same process happening in a spreadsheet, a document or someone inboxes.

Do not use it for: payroll calculation, tax filing, or legal advice. This skill produces empty templates only - it never holds or processes real employee or customer data.

How It Works

Follow the shared execution contract. The module-specific rules below define only domain fields, decisions, calculations, and safety constraints.

Step 1 - Identify intent

Read the request and pick the intent before asking anything.

• "set up" or "build" or "create" -> the user wants artifacts; go to Step 2.
• "our process is ..." or "it is in a sheet" -> the user wants to move an existing process; capture it, then Step 2.
• "is this right" or "review" or "audit" -> the user wants a check, not a build; answer from what they share.
• "how do I ..." -> advice question; answer directly and offer the build only if it helps.

Ask only if this is the highest-value missing fact; otherwise proceed without an opener:

Q: How many objectives are you setting this quarter?

Step 2 - Ask only what is missing

Skip anything the user already answered, in any earlier message. Ask the rest one at a time, and stop as soon as the remaining answers would not change the output.

• Goals - How many objectives? / Company or team first? / Who owns each?
• Shape - Key results each? / Measured how? / Ambitious or committed?
• Cadence - Weekly or monthly check-in? / Who reviews? / Public or internal?
• Current process - How do you set goals now? / Document or meeting? / Is it reviewed?
• Outcome - What do you need? / Goal setting, tracking or reporting?

Never invent an answer. If the user does not know, record it as unknown and carry on.

Step 3 - Hold the internal context

Hold the answers in this shape. It stays internal - it is not shown to the user unless they ask, and it never carries a value the user did not give.

module: okr-system
intent: null            # setup | advice | review | fix | build | convert | export
scale: null             # Starter | Growth | Scale, only if the answer changes it
areas:
  "Goals": null
  "Shape": null
  "Cadence": null
  "Current process": null
  "Outcome": null
requested_outputs: []   # csv | sql | json | notion | xlsx - requested formats only
confirmed_facts: []     # only what the user actually said
open_questions: []      # the unanswered ones, in the order worth asking

Step 4 - Recommend the smallest workflow

If an artifact was requested, build it after resolving essential missing facts. Otherwise give a short recommendation and offer the relevant artifact.

Recommended approach: Cascade company to team to person, and review progress on a fixed cadence. Three key results per objective is the practical limit.

Why this one: OKRs fail when objectives have no key results or no review date. Enforce both at creation rather than reviewing for them later.

Workflow: Objective → Key results → Owner → Progress update → Review → Close

Step 5 - Build only on request

Once the user asks for it, derive the fields from the confirmed context and emit the requested artifacts. For machine-readable text, keep prose outside the data; for files, provide a usable link. Report material validation failures or limitations separately.

A selected Notion output is rendered by notion-manual-import, so route the Notion step there. When the user selects Notion, hand that step to ](https://github.com/sickn33/agentic-awesome-skills/blob/main/skills/notion-manual-import/SKILL.md): it holds the CSV, the property mapping, the import steps and the verification checklist, and it renders the Field Reference below instead of defining a table of its own. Do not restate the mapping here and do not improvise the import steps. Manual CSV and mapping outputs need no connection. For requested workspace changes, follow the shared contract: verify actual tool access and the target before writing. A user saying "connected" is not tool evidence. Never ask for a Notion password or token.

For an Excel-compatible CSV, use UTF-8 with a byte order mark so Excel opens the text correctly. A CSV is not an .xlsx workbook; create .xlsx only when the user requests a workbook. A CSV carries no types, so after it, name the columns that need a number, date or currency format applied.

Objective,Department,End Date,KR1 Progress %,KR2 Progress %,KR3 Progress %,Key Result 1,Key Result 2,Key Result 3,Last Updated,Level,Notes,OKR ID,Owner,Parent OKR,Progress %,Quarter,Start Date,Status,Year
Make delivery predictable,Delivery,2026-09-30,75,60,40,Reduce churn to 4%,Ship 20 client sites,NPS above 50,2026-01-15,L1,Q2 closed at 60 percent; the two weakest key results were carried into the March review.,,Sneha Iyer,OKR-2026-COMPANY,60,Q1,2026-07-01,Active,2026

CREATE TABLE okr_system (
  objective VARCHAR(255),
  department VARCHAR(255),
  end_date DATE NOT NULL,
  kr1_progress_pct NUMERIC NOT NULL,
  kr2_progress_pct NUMERIC NOT NULL,
  kr3_progress_pct NUMERIC NOT NULL,
  key_result_1 VARCHAR(255),
  key_result_2 VARCHAR(255),
  key_result_3 VARCHAR(255),
  last_updated DATE NOT NULL,
  level VARCHAR(100) NOT NULL,
  notes TEXT,
  okr_id SERIAL PRIMARY KEY,
  owner VARCHAR(255),
  parent_okr VARCHAR(255),  -- relation -> target record
  progress_pct NUMERIC NOT NULL,
  quarter VARCHAR(255),
  start_date DATE NOT NULL,
  status VARCHAR(100) NOT NULL,
  year VARCHAR(255),
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);

CREATE INDEX idx_okr_system_status ON okr_system (status);

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "OKR System",
  "type": "object",
  "additionalProperties": false,
  "properties": {
      "Objective": { "type": "string" },
      "Department": { "type": "string" },
      "End Date": { "type": "string", "format": "date" },
      "KR1 Progress %": { "type": "number" },
      "KR2 Progress %": { "type": "number" },
      "KR3 Progress %": { "type": "number" },
      "Key Result 1": { "type": "string" },
      "Key Result 2": { "type": "string" },
      "Key Result 3": { "type": "string" },
      "Last Updated": { "type": "string", "format": "date" },
      "Level": { "type": "string" },
      "Notes": { "type": "string" },
      "OKR ID": { "type": "integer" },
      "Owner": { "type": "string" },
      "Parent OKR": { "type": "string" },
      "Progress %": { "type": "number" },
      "Quarter": { "type": "string" },
      "Start Date": { "type": "string", "format": "date" },
      "Status": { "type": "string" },
      "Year": { "type": "string" }
  },
  "required": [
      "End Date",
      "KR1 Progress %",
      "KR2 Progress %",
      "KR3 Progress %",
      "Last Updated",
      "Level",
      "Progress %",
      "Start Date",
      "Status"
  ]
}

| CSV column | Notion property | Set after import |
|---|---|---|
| Objective | Title | Use as the database title |
| Department | Text | Leave as Text |
| End Date | Date | Convert to Date |
| KR1 Progress % | Number | Convert to Number |
| KR2 Progress % | Number | Convert to Number |
| KR3 Progress % | Number | Convert to Number |
| Key Result 1 | Text | Leave as Text |
| Key Result 2 | Text | Leave as Text |
| Key Result 3 | Text | Leave as Text |
| Last Updated | Date | Convert to Date |
| Level | Select (add options after import) | Convert to Select, add options: "L1", "L2", "L3", "L4", "L5", "M1", "M2" |
| Notes | Text | Leave as Text |
| OKR ID | Text (preserve source ID) | Keep imported IDs as Text; optionally add a separate Unique ID property |
| Owner | Text | Leave as Text |
| Parent OKR | Relation (link to the target database) | Convert to Relation, link to the target database |
| Progress % | Number | Convert to Number |
| Quarter | Text | Leave as Text |
| Start Date | Date | Convert to Date |
| Status | Select (add options after import) | Convert to Select, add options: "Draft", "Active", "At Risk", "Closed" |
| Year | Text | Leave as Text |

The rows above are documentation examples only. Emit empty templates unless the user explicitly requests examples. Money stays currency, dates stay date, and anything pointing at another table stays relation.

Field Reference