domain-language-extraction

Extracts domain terminology from business documents into a ubiquitous language dictionary.

Updated Jul 13, 2026
One-click install
npx skills add https://github.com/eencinasq/cripto-pos --skill domain-language-extraction-eencinasq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: domain-language-extraction
Source: https://github.com/eencinasq/cripto-pos/tree/main/.kiro/skills/domain-language-extraction
Command: npx skills add https://github.com/eencinasq/cripto-pos --skill domain-language-extraction-eencinasq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Business documents contain scattered domain terminology that teams interpret inconsistently, causing misaligned domain models and ambiguous requirements. This Skill systematically extracts and structures that terminology into a single ubiquitous language dictionary. ## Core Features & Use Cases - Five Extraction Techniques: Noun phrase extraction, entity pattern recognition, acronym detection, relationship extraction, and action/command extraction applied to business text. - Structured Dictionary Output: Produces core domain entities, personas, domain events, processes, business rules, metrics, acronyms, and terms to avoid. - Confidence Scoring: Assigns 0.8–1.0 confidence scores based on term frequency and consistency, flagging ambiguous terms for clarification. - Use Case: Feed a PRD or discovery workshop notes into the Skill to seed a domain-model.md file, with unrecognized terms flagged as uncertainty factors for the team to resolve. ## Quick Start Extract the domain language from the attached business requirements document and produce a ubiquitous language dictionary.

Frequently Asked Questions about domain-language-extraction

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract domain terminology from business documents?▼

Apply the five extraction techniques: noun phrase extraction for domain nouns, entity pattern recognition for business objects and events, acronym detection, relationship extraction, and action extraction for domain verbs. Results are organized into a structured ubiquitous language dictionary.

What is a ubiquitous language dictionary in domain-driven design?▼

A ubiquitous language dictionary is a shared vocabulary of domain terms agreed upon by developers and business stakeholders. It contains entities, personas, domain events, processes, business rules, metrics, and acronyms with precise definitions used consistently across code and documentation.

How does the confidence scoring for extracted terms work?▼

Confidence is frequency-based: 1.0 for terms appearing more than 10 times consistently, 0.9 for 5–10 occurrences, 0.8 for 2–4 occurrences, and below 0.8 for ambiguous terms. Low-confidence terms are flagged as needing clarification.

Can extracted terms feed into an existing domain model?▼

Yes, extracted terms integrate directly into domain-model.md. Terms not found in the existing model are flagged as uncertainty factors, helping teams identify gaps between documentation and the current domain model.

What are the limitations of automated domain language extraction?▼

Terms appearing fewer than two times receive low confidence scores and may be missed or misclassified. Ambiguous terms with context-dependent meanings require human clarification, and vague terms are listed as terms to avoid rather than resolved automatically.