disciplinary-pip-tracker – Coding skill for AI agents

Disciplinary & PIP Tracker

What it is: Performance issues.

Overview

Works out the smallest useful Disciplinary & PIP Tracker 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

• performance improvement plan
• pip tracker
• disciplinary record
• misconduct case log

Also use it when the user says "performance issues", 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: What triggered this conversation?

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.

• Case - What happened? / First case or pattern? / Policy broken which one?
• Process - Formal or informal? / Stages? / Who owns the case?
• Records - Who is in the loop? / Written record kept? / Evidence stored where?
• Current process - How do you handle it now? / Spreadsheet or memory? / What breaks?
• Outcome - What do you need? / A case record, a plan 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: disciplinary-pip-tracker
intent: null            # setup | advice | review | fix | build | convert | export
scale: null             # Starter | Growth | Scale, only if the answer changes it
areas:
  "Case": null
  "Process": null
  "Records": 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: Run this as a documented case with a start, review dates and an outcome, whatever stage the process is at.

Why this one: A dated timeline supports review, but fair evidence assessment and the decision process remain essential. Distinguish allegations, observed facts, employee response and authorized findings.

Workflow: Case opened → Goals and review date → Review → Outcome → Closure and appeal

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.

Case Title,Employee Name,Department,Manager,HR Owner,Case Type,Linked Performance Review,Linked Issue,Issue Summary,Improvement Goals,Start Date,Review Date,End Date,Outcome,Confidential,Status,Case ID
Missed handover on Northwind account,Aarav Sharma,Delivery,Sneha Iyer,Ananya Rao,Misconduct,REV-2026-Q1,ISS-2026-021,Client escalation raised after a missed handover milestone.,Close 5 tickets per week,2026-08-03,2026-09-14,2026-10-30,"Pending investigation; no outcome determined.",Restricted,Investigation,

CREATE TABLE disciplinary_pip_tracker (
  case_title VARCHAR(255),
  employee_name VARCHAR(255),
  department VARCHAR(255),
  manager VARCHAR(255),
  hr_owner VARCHAR(255),
  case_type VARCHAR(100) NOT NULL,
  linked_performance_review VARCHAR(255),  -- relation -> target record
  linked_issue VARCHAR(255),  -- relation -> target record
  issue_summary TEXT,
  improvement_goals VARCHAR(255),
  start_date DATE NOT NULL,
  review_date DATE NOT NULL,
  end_date DATE,
  outcome VARCHAR(255),
  confidential VARCHAR(100) NOT NULL,
  status VARCHAR(100) NOT NULL,
  case_id SERIAL PRIMARY KEY,
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);

CREATE INDEX idx_disciplinary_pip_tracker_status ON disciplinary_pip_tracker (status);

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Disciplinary & PIP Tracker",
  "type": "object",
  "additionalProperties": false,
  "properties": {
      "Case Title": { "type": "string" },
      "Employee Name": { "type": "string" },
      "Department": { "type": "string" },
      "Manager": { "type": "string" },
      "HR Owner": { "type": "string" },
      "Case Type": { "type": "string" },
      "Linked Performance Review": { "type": "string" },
      "Linked Issue": { "type": "string" },
      "Issue Summary": { "type": "string" },
      "Improvement Goals": { "type": "string" },
      "Start Date": { "type": "string", "format": "date" },
      "Review Date": { "type": "string", "format": "date" },
      "End Date": { "type": "string", "format": "date" },
      "Outcome": { "type": "string" },
      "Confidential": { "type": "string" },
      "Status": { "type": "string" },
      "Case ID": { "type": "integer" }
  },
  "required": [
      "Case Type",
      "Start Date",
      "Review Date",
      "Confidential",
      "Status"
  ]
}

| CSV column | Notion property | Set after import |
|---|---|---|
| Case Title | Title | Use as the database title |
| Employee Name | Text | Leave as Text |
| Department | Text | Leave as Text |
| Manager | Text | Leave as Text |
| HR Owner | Text | Leave as Text |
| Case Type | Select (add options after import) | Convert to Select, add options: "Misconduct", "Performance", "Attendance", "Policy Breach", "Grievance" |
| Linked Performance Review | Relation (link to the target database) | Convert to Relation, link to the target database |
| Linked Issue | Relation (link to the target database) | Convert to Relation, link to the target database |
| Issue Summary | Text | Leave as Text |
| Improvement Goals | Text | Leave as Text |
| Start Date | Date | Convert to Date |
| Review Date | Date | Convert to Date |
| End Date | Date | Convert to Date |
| Outcome | Text | Leave as Text |
| Confidential | Select (add options after import) | Convert to Select, add options: "Restricted", "Highly Restricted" |
| Status | Select (add options after import) | Convert to Select, add options: "Opened", "Investigation", "Hearings", "Decision", "Appeals", "Closed" |
| Case ID | Text (preserve source ID) | Keep imported IDs as Text; optionally add a separate Unique ID property |

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

| # | Field | Type | SQL | JSON Schema | Notion | CSV example |

|---:|---|---|---|---|---|-

… (full content is in the download package)