Learning Career Development

Learning & Career Development

What it is: Learning management.

Overview

Works out the smallest useful Learning & Career Development 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

• lms tracker
• learning management
• course completion tracker
• employee training record

Also use it when the user says "learning management", 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 people are learning something right now?

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.

• Learning - Internal or external courses? / Mandatory or optional? / How many people?
• Records - Certificates tracked? / Progress visible? / Completion required?
• Process - Who approves enrolment? / Budget per person? / LMS in use?
• Current process - How do you track now? / Files or nothing? / What gets missed?
• Outcome - What do you need? / A record, dashboards or mandatory tracking?

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: learning-career-development
intent: null            # setup | advice | review | fix | build | convert | export
scale: null             # Starter | Growth | Scale, only if the answer changes it
areas:
  "Learning": null
  "Records": null
  "Process": 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 enrolment, completion and certificate per person, and only add mandatory flags if something is actually enforced.

Why this one: Learning records matter later for probation and promotion. Keep them per person with a completion date and a link to the certificate.

Workflow: Enrolment → Progress → Completion → Certificate → Record

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.

Course / Training,Certificate Earned,Completion Date,Course Category,Course URL,Delivery Method,Department,Duration (Hours),Employee Name,Course Request,LMS ID,Mandatory,Notes,Progress %,Provider,Score,Skills Gained,Start Date,Status
Advanced SQL,FALSE,2026-10-30,General,https://example.com/courses/leadership,Self-paced online,Delivery,2.5,Aarav Sharma,CRS-2026-018,,FALSE,Course completion tracked to the February cohort; one learner has not started.,60, Udemy,4,"Advanced SQL, stakeholder mapping, contract review.",2026-08-03,In Progress

CREATE TABLE learning_career_development (
  course_training VARCHAR(255),
  certificate_earned BOOLEAN NOT NULL,
  completion_date DATE NOT NULL,
  course_category VARCHAR(100) NOT NULL,
  course_url TEXT,
  delivery_method VARCHAR(255),
  department VARCHAR(255),
  duration_hours NUMERIC NOT NULL,
  employee_name VARCHAR(255),
  course_request VARCHAR(255),  -- relation -> target record
  lms_id SERIAL PRIMARY KEY,
  mandatory BOOLEAN NOT NULL,
  notes TEXT,
  progress_pct NUMERIC NOT NULL,
  provider VARCHAR(255),
  score NUMERIC NOT NULL,
  skills_gained VARCHAR(255),
  start_date DATE NOT NULL,
  status VARCHAR(100) NOT NULL,
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);

CREATE INDEX idx_learning_career_development_status ON learning_career_development (status);

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Learning & Career Development",
  "type": "object",
  "additionalProperties": false,
  "properties": {
      "Course / Training": { "type": "string" },
      "Certificate Earned": { "type": "boolean" },
      "Completion Date": { "type": "string", "format": "date" },
      "Course Category": { "type": "string" },
      "Course URL": { "type": "string", "format": "uri" },
      "Delivery Method": { "type": "string" },
      "Department": { "type": "string" },
      "Duration (Hours)": { "type": "number" },
      "Employee Name": { "type": "string" },
      "Course Request": { "type": "string" },
      "LMS ID": { "type": "integer" },
      "Mandatory": { "type": "boolean" },
      "Notes": { "type": "string" },
      "Progress %": { "type": "number" },
      "Provider": { "type": "string" },
      "Score": { "type": "number" },
      "Skills Gained": { "type": "string" },
      "Start Date": { "type": "string", "format": "date" },
      "Status": { "type": "string" }
  },
  "required": [
      "Completion Date",
      "Course Category",
      "Duration (Hours)",
      "Progress %",
      "Score",
      "Start Date",
      "Status"
  ]
}

| CSV column | Notion property | Set after import |
|---|---|---|
| Course / Training | Title | Use as the database title |
| Certificate Earned | Checkbox | Convert to Checkbox |
| Completion Date | Date | Convert to Date |
| Course Category | Select (add options after import) | Convert to Select, add options: "General", "Operations", "Finance", "People", "Compliance" |
| Course URL | URL | Convert to URL |
| Delivery Method | Text | Leave as Text |
| Department | Text | Leave as Text |
| Duration (Hours) | Number | Convert to Number |
| Employee Name | Text | Leave as Text |
| Course Request | Relation (link to the target database) | Convert to Relation, link to the target database |
| LMS ID | Text (preserve source ID) | Keep imported IDs as Text; optionally add a separate Unique ID property |
| Mandatory | Checkbox | Convert to Checkbox |
| Notes | Text | Leave as Text |
| Progress % | Number | Convert to Number |
| Provider | Text | Leave as Text |
| Score | Number | Convert to Number |
| Skills Gained | Text | Leave as Text |
| Start Date | Date | Convert to Date |
| Status | Select (add options after import) | Convert to Select, add options: "Not Started", "Enrolled", "In Progress", "Completed", "Failed", "Expired" |

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