domain-extractconcepts

Name: domain-extractconcepts
Availability: InStock
Author: zhongadamwang

Extract domain concepts, entities, and relationships from requirements into JSON and Markdown.

Updated Feb 21, 2026

Search Tags:#traceability #relationships #terminology #domain-modeling #requirements-analysis #domain-concepts

Ready to run

npx skills add https://github.com/zhongadamwang/CCAGA --skill domain-extractconcepts

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: domain-extractconcepts
Source: https://github.com/zhongadamwang/CCAGA/tree/main/.github/skills/domain-extractconcepts
Command: npx skills add https://github.com/zhongadamwang/CCAGA --skill domain-extractconcepts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Requirements often include scattered mentions of domain terms, entities, and relationships, making domain modeling time-consuming and error-prone. This skill automates extraction to produce a coherent, reusable domain concept map.

Core Features & Use Cases

Extract domain-specific concepts, entities, terminology, and relationships from analyzed requirements
Generate domain-concepts.json (machine-readable) and domain-concepts.md (human-readable) with traceability
Support downstream domain modeling, glossary creation, and impact analysis

Quick Start

Ingest the requirements.json and goals.json to produce domain concepts and domain documentation.

Frequently Asked Questions about domain-extractconcepts

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

FAQPage Schema

How do I extract domain concepts and entities from requirements for domain modeling?▼

You can extract domain concepts by ingesting structured requirements and goals to identify entities, terminology, and relationships. This process produces a reusable domain concept map with traceability, enabling coherent downstream domain modeling and glossary creation.

What is the best way to generate a domain concept map from scattered requirements documentation?▼

Generating a domain concept map involves analyzing structured requirements to isolate domain-specific terms and relationships. This automated extraction prevents manual errors and outputs both machine-readable JSON and human-readable markdown documentation with provenance frontmatter.

How does traceability work when structuring domain terminology and relationships from requirements?▼

Traceability is established by linking extracted domain concepts, entities, and relationships directly back to the analyzed requirements. The generated JSON and markdown outputs include frontmatter provenance, ensuring every domain term maps to its source requirement for impact analysis.

Can I use extracted domain concepts to generate a machine-readable glossary for downstream design?▼

Yes, extracted domain concepts can generate a machine-readable glossary by outputting a structured domain-concepts.json file. This file captures entities, domain areas, and relationships, directly supporting downstream design and impact analysis.

Do I need structured requirements and goals to identify domain-specific terminology and relationships?▼

Yes, you need to ingest structured requirements.json and goals.json files to accurately identify domain-specific terminology and relationships. This structured input ensures the extracted domain concepts have reliable traceability for downstream design.

What outputs are generated when structuring domain concepts and relationships from requirements?▼

The outputs generated are a machine-readable domain-concepts.json and a human-readable domain-concepts.md file. Both contain structured entities, relationships, domain areas, and frontmatter provenance to support downstream domain modeling and documentation.