Health Wellness

Health & Wellness

What it is: Wellbeing tracking.

Overview

Works out the smallest useful Health & Wellness 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 6: Engage. Fits: Scale stage. Table code: n/a.

When to Use This Skill

• employee wellbeing
• health check in tracker
• wellness survey
• mental health support log

Also use it when the user says "wellbeing tracking", 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 for employees or a team?

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.

• Scope - Who is it for? / How many people? / Perks or programmes?
• Use - What is offered? / Optional or mandatory? / Any medical data?
• Privacy - Is it anonymous? / Who can see participation? / Any health details held?
• Current process - Anything offered now? / How is it communicated? / Is uptake tracked?
• Outcome - What do you need? / A benefits list, participation counts 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: health-wellness
intent: null            # setup | advice | review | fix | build | convert | export
scale: null             # Starter | Growth | Scale, only if the answer changes it
areas:
  "Scope": null
  "Use": 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: Track benefits and uptake only. Do not store any individual health information, since the benefit does not need it.

Why this one: Wellness programmes create risk the moment individual health data is held. Keep participation counts and leave the details out.

Workflow: Benefit offered → Uptake count → Anonymous feedback → Review

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.

Check-in Title,Employee Name,Anonymous,Department,Check-in Date,Wellbeing Score,Stress Level,Energy Level,Support Requested,Resource Shared,Confidential,Status,Wellness ID
Weekly wellbeing check,Aarav Sharma,FALSE,Delivery,2026-01-15,4,Low,Low,FALSE,FALSE,Internal,Completed,

CREATE TABLE health_wellness (
  check_in_title VARCHAR(255),
  employee_name VARCHAR(255),
  anonymous BOOLEAN NOT NULL,
  department VARCHAR(255),
  check_in_date DATE NOT NULL,
  wellbeing_score NUMERIC NOT NULL,
  stress_level VARCHAR(100) NOT NULL,
  energy_level VARCHAR(100) NOT NULL,
  support_requested BOOLEAN NOT NULL,
  resource_shared BOOLEAN NOT NULL,
  confidential VARCHAR(100) NOT NULL,
  status VARCHAR(100) NOT NULL,
  wellness_id SERIAL PRIMARY KEY,
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);

CREATE INDEX idx_health_wellness_status ON health_wellness (status);

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Health & Wellness",
  "type": "object",
  "additionalProperties": false,
  "properties": {
      "Check-in Title": { "type": "string" },
      "Employee Name": { "type": "string" },
      "Anonymous": { "type": "boolean" },
      "Department": { "type": "string" },
      "Check-in Date": { "type": "string", "format": "date" },
      "Wellbeing Score": { "type": "number" },
      "Stress Level": { "type": "string" },
      "Energy Level": { "type": "string" },
      "Support Requested": { "type": "boolean" },
      "Resource Shared": { "type": "boolean" },
      "Confidential": { "type": "string" },
      "Status": { "type": "string" },
      "Wellness ID": { "type": "integer" }
  },
  "required": [
      "Check-in Date",
      "Wellbeing Score",
      "Stress Level",
      "Energy Level",
      "Confidential",
      "Status"
  ]
}

| CSV column | Notion property | Set after import |
|---|---|---|
| Check-in Title | Title | Use as the database title |
| Employee Name | Text | Leave as Text |
| Anonymous | Checkbox | Convert to Checkbox |
| Department | Text | Leave as Text |
| Check-in Date | Date | Convert to Date |
| Wellbeing Score | Number | Convert to Number |
| Stress Level | Select (add options after import) | Convert to Select, add options: "Low", "Medium", "High", "Critical" |
| Energy Level | Select (add options after import) | Convert to Select, add options: "Low", "Medium", "High" |
| Support Requested | Checkbox | Convert to Checkbox |
| Resource Shared | Checkbox | Convert to Checkbox |
| Confidential | Select (add options after import) | Convert to Select, add options: "Public", "Internal", "Restricted", "Highly Restricted" |
| Status | Select (add options after import) | Convert to Select, add options: "Scheduled", "Completed", "Missed", "Follow-up Due" |
| Wellness 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