issue-grievance-tracker – skill Khác cho agent AI

Issue & Grievance Tracker

What it is: Code of Conduct issues, internal complaints and workplace problems.

Overview

Works out the smallest useful Issue & Grievance 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: Starter stage. Table code: n/a.

When to Use This Skill

• grievance tracker
• workplace complaint log
• code of conduct case
• anonymous complaint box

Also use it when the user says "code of conduct issues, internal complaints and workplace problems", 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: Is this an anonymous complaint?

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.

• Type - Conduct, safety or pay? / One person or a team? / First or repeat?
• Process - Who triages? / Investigation owner? / SLA days?
• Privacy - Anonymous allowed? / Who can see it? / Confidentiality level?
• Current process - How are complaints handled now? / Verbal or written? / What gets missed?
• Outcome - What do you need? / A log, an investigation record or both?

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: issue-grievance-tracker
intent: null            # setup | advice | review | fix | build | convert | export
scale: null             # Starter | Growth | Scale, only if the answer changes it
areas:
  "Type": null
  "Process": null
  "Privacy": 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: Log the complaint first with a severity and an owner, then decide if a linked disciplinary case is needed.

Why this one: Grievances are missed when they arrive verbally. Capture a date and independent triage owner, then apply access restrictions, evidence handling, review and escalation controls.

Workflow: Complaint raised → Triage → Investigation → Action taken → Closure

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.

Issue Title,Issue Type,Raised By,Anonymous,Against (Person or Team),Department,Date Raised,Related Policy,Severity,Description,Assigned To,Investigation Notes,Action Taken,Linked Disciplinary Case,Resolution Date,Days Open,Confidential,Status,Issue ID
Client escalation after missed milestone,Conduct,Example Reporter,FALSE,Example Subject,Delivery,2026-01-15,Code of Conduct,Medium,"Repeated late status updates to the client after a missed milestone, raised by the account team.",Example Case Owner,Witness statements collected. Meeting held with both parties.,Synthetic outcome recorded after authorized human review.,CASE-EXAMPLE-004,2026-01-19,4,Restricted,Resolved,

CREATE TABLE issue_grievance_tracker (
  issue_title VARCHAR(255),
  issue_type VARCHAR(100) NOT NULL,
  raised_by VARCHAR(255),
  anonymous BOOLEAN NOT NULL,
  against_person_or_team VARCHAR(255),
  department VARCHAR(255),
  date_raised DATE NOT NULL,
  related_policy VARCHAR(255),
  severity VARCHAR(100) NOT NULL,
  description TEXT,
  assigned_to VARCHAR(255),
  investigation_notes TEXT,
  action_taken VARCHAR(255),
  linked_disciplinary_case VARCHAR(255),  -- relation -> target record
  resolution_date DATE,
  days_open INTEGER CHECK (days_open >= 0),
  confidential VARCHAR(100) NOT NULL,
  status VARCHAR(100) NOT NULL,
  issue_id SERIAL PRIMARY KEY,
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);

CREATE INDEX idx_issue_grievance_tracker_status ON issue_grievance_tracker (status);

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Issue & Grievance Tracker",
  "type": "object",
  "additionalProperties": false,
  "properties": {
    "Issue Title": {
      "type": "string"
    },
    "Issue Type": {
      "type": "string"
    },
    "Raised By": {
      "type": "string"
    },
    "Anonymous": {
      "type": "boolean"
    },
    "Against (Person or Team)": {
      "type": "string"
    },
    "Department": {
      "type": "string"
    },
    "Date Raised": {
      "type": "string",
      "format": "date"
    },
    "Related Policy": {
      "type": "string"
    },
    "Severity": {
      "type": "string"
    },
    "Description": {
      "type": "string"
    },
    "Assigned To": {
      "type": "string"
    },
    "Investigation Notes": {
      "type": "string"
    },
    "Action Taken": {
      "type": "string"
    },
    "Linked Disciplinary Case": {
      "type": "string"
    },
    "Resolution Date": {
      "type": "string",
      "format": "date"
    },
    "Days Open": {
      "type": "integer",
      "minimum": 0
    },
    "Confidential": {
      "type": "string"
    },
    "Status": {
      "type": "string"
    },
    "Issue ID": {
      "type": "integer"
    }
  },
  "required": [
    "Anonymous",
    "Issue Type",
    "Date Raised",
    "Severity",
    "Confidential",
    "Status"
  ]
}

| CSV column | Notion property | Set after import |
|---|---|---|
| Issue Title | Title | Use as the database title |
| Issue Type | Select (add options after import) | Convert to Select, add options: "Conduct", "Harassment", "Discrimination", "Safety", "Pay", "Workplace", "Other" |
| Raised By | Text | Leave as Text |
| Anonymous | Checkbox | Convert to Checkbox |
| Against (Person or Team) | Text | Leave as Text |
| Department | Text | Leave as Text |
| Date Raised | Date | Convert to Date |
| Related Policy | Text | Leave as Text |
| Severity | Select (add options after import) | Convert to Select, add options: "Low", "Medium", "High", "Critical" |
| Description | Text | Leave as Text |
| Assigned To | Text | Leave as Text |
| Investigation Notes | Text | Leave as Text |
| Action Taken | Text | Leave as Text |
| Linked Disciplinary Case | Relation (link to the target database) | Convert to Relation, link to the target database |
| Resolution Date | Date | Convert to Date |
| Days Open | Number | Conver

… (nội dung đầy đủ có trong gói tải về)