promotion-upgrade-requests – Other skill for AI agents

Promotion & Upgrade Requests

What it is: Promotion, grade upgrade, role change and salary revision requests.

Overview

Works out the smallest useful Promotion & Upgrade Requests 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 5: Develop. Fits: Growth stage. Table code: n/a.

When to Use This Skill

• promotion request
• grade upgrade tracker
• salary revision request
• internal mobility tracker

Also use it when the user says "promotion, grade upgrade, role change and salary revision requests", 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: Who can request a promotion?

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.

• Requests - ask these as separate messages, in this order when still material: who

requests; how often; whether the request includes a grade or role change. Never combine

two of them into one clarification. For an ambiguous Requests answer, clarify who may

request first, then wait.

• Criteria - Fixed criteria? / Performance score needed? / Time in role?
• Approval - Who approves? / One or two levels? / Effective date set by?
• Current process - How do you handle it now? / Email or nothing? / What gets delayed?
• Outcome - What do you need? / A request form, approvals or a record?

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: promotion-upgrade-requests
intent: null            # setup | advice | review | fix | build | convert | export
scale: null             # Starter | Growth | Scale, only if the answer changes it
areas:
  "Requests": null
  "Criteria": null
  "Approval": 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: Require a written request with evidence, route it by grade, and record the decision and effective date as one object.

Why this one: Promotion decisions drift when the request, the evidence and the decision live in different places. One record with a decision field fixes the trail.

Workflow: Request submitted → Criteria check → Approval → Decision → People and payroll update

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

@notion-manual-import: 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.

Request Title,Employee Name,Department,Request Type,Current Job Title,Current Grade,Requested Job Title,Requested Grade,Requested By,Justification,Linked Performance Review,OKR Score,Behaviour Score,Courses Completed,Time in Role (Months),Criteria Met,Current Salary,Proposed Salary,Currency,Increase %,Approver,Decision,Effective Date,Status,Upgrade ID
Promotion to L3,Example Employee,Delivery,Promotion,HR Executive,L2,Finance Analyst,L3,Example Manager,Consistent delivery over 12 months,REV-2026-Q1,0.7,4,"Advanced SQL, Workplace Safety",18,FALSE,1450000.00,1624000.00,INR,12,Example Approver,Pending,,Under Review,

CREATE TABLE promotion_upgrade_requests (
  request_title VARCHAR(255),
  employee_name VARCHAR(255),
  department VARCHAR(255),
  request_type VARCHAR(100) NOT NULL,
  current_job_title VARCHAR(255),
  current_grade VARCHAR(255),
  requested_job_title VARCHAR(255),
  requested_grade VARCHAR(255),
  requested_by VARCHAR(255),
  justification VARCHAR(255),
  linked_performance_review VARCHAR(255),  -- relation -> target record
  okr_score NUMERIC,
  behaviour_score NUMERIC,
  courses_completed VARCHAR(255),
  time_in_role_months INTEGER CHECK (time_in_role_months >= 0),
  criteria_met BOOLEAN,
  current_salary NUMERIC(14,2) CHECK (current_salary >= 0),
  proposed_salary NUMERIC(14,2) CHECK (proposed_salary >= 0),
  currency VARCHAR(255),
  increase_pct NUMERIC,
  approver VARCHAR(255),
  decision VARCHAR(255),
  effective_date DATE,
  status VARCHAR(100) NOT NULL,
  upgrade_id SERIAL PRIMARY KEY,
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);

CREATE INDEX idx_promotion_upgrade_requests_status ON promotion_upgrade_requests (status);

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Promotion & Upgrade Requests",
  "type": "object",
  "additionalProperties": false,
  "properties": {
      "Request Title": { "type": "string" },
      "Employee Name": { "type": "string" },
      "Department": { "type": "string" },
      "Request Type": { "type": "string" },
      "Current Job Title": { "type": "string" },
      "Current Grade": { "type": "string" },
      "Requested Job Title": { "type": "string" },
      "Requested Grade": { "type": "string" },
      "Requested By": { "type": "string" },
      "Justification": { "type": "string" },
      "Linked Performance Review": { "type": "string" },
      "OKR Score": { "type": ["number", "null"] },
      "Behaviour Score": { "type": ["number", "null"] },
      "Courses Completed": { "type": "string" },
      "Time in Role (Months)": { "type": ["integer", "null"], "minimum": 0 },
      "Criteria Met": { "type": "boolean" },
      "Current Salary": { "type": ["number", "null"] },
      "Proposed Salary": { "type": ["number", "null"] },
      "Currency": { "type": "string" },
      "Increase %": { "type": ["number", "null"] },
      "Approver": { "type": "string" },
      "Decision": { "type": "string" },
      "Effective Date": { "type": ["string", "null"], "format": "date" },
      "Status": { "type": "string" },
      "Upgrade ID": { "type": "integer" }
  },
  "required": [
      "Request Type",
      "Status"
  ]
}

| CSV column | Notion property | Set after import |
|---|---|---|
| Request Title | Title | Use as the database title |
| Employee Name | Text | Leave as Text |
| Department | Text | Leave as Text |
| Request Type | Select (add options after import) | Convert to Select, add options: "Promotion", "Grade Upgrade", "Role Change", "Salary Revision" |
| Current Job Title | Text | Leave as Text |
| Current Grade | Text | Leave as Text |
| Requested Job Title | Text | Leave as Te

… (full content is in the download package)