1. AssignTaskToUser
  2. CompleteTask
  3. OnboardNewUserWithSkills
  4. ProcessNewTask

Problem

In building a system that links users and tasks to relevant technical skills, we encountered a cyclic dependency in the skill extraction process:

The system needs a predefined skill dictionary to recognize and normalize extracted skills from unstructured text (e.g., task descriptions, resumes). However, this same dictionary is meant to be built and enriched over time from those unstructured inputs.

This creates a chicken-and-egg problem:

Relying on an LLM (Large Language Model) alone for extraction and normalization is brittle—it might guess wrong or inconsistently about internal naming conventions, aliases, or database schema. Moreover, any single-step AI extraction is opaque, hard to audit, and difficult to scale or maintain.


✅ Solution Overview

To break the cycle and make the system robust, we designed a Three-Stage Skill Processing Pipeline:

Raw Extraction (LLM) → Normalization (Alias Map) → Database Write (Transactional Insert)

This approach decouples the stages of identifying, standardizing, and storing skills, allowing the system to evolve its dictionary dynamically while remaining consistent and predictable.


🧠 Stage 1: Raw Skill Extraction (LLM)