skills.rest
Haaaiawd
HaaaiawdCOMMUNITY
Explore all skills by this author →
GitHub

concept-modeler

Extract domain concepts from ambiguous requirements using Domain-Driven Design principles.

142|24|Updated Jan 19, 2026
Search Tags:#domain modeling#ddd#software architecture#requirements analysis#gap analysis#concept extraction
One-click install
npx skills add https://github.com/Haaaiawd/Antigravity-Workflow-System --skill concept-modeler
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: concept-modeler
Source: https://github.com/Haaaiawd/Antigravity-Workflow-System/tree/main/.agent/skills/concept-modeler
Command: npx skills add https://github.com/Haaaiawd/Antigravity-Workflow-System --skill concept-modeler

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and prompts (resource) components.

What problem does it solve?

This Skill transforms vague user requirements into precise domain concepts (Entities, Flows, Missing Components), preventing misunderstandings and ensuring a solid foundation for development.

Core Features & Use Cases

  • Concept Identification: Extracts key nouns (Entities) and verbs (Flows) from user descriptions.
  • Gap Analysis: Proactively identifies crucial "dark matter" components users forget to mention (e.g., error handling, persistence).
  • Use Case: A user says, "I want to sync my lists." This Skill will ask clarifying questions to define what "list" means (e.g., Wishlist, Shopping Cart) and how "sync" should work (real-time, batch, bidirectional).

Quick Start

Use the concept modeler skill to analyze the user requirement "I need a way to track user activity on the website."

Frequently Asked Questions about concept-modeler

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

FAQPage Schema
How do I extract domain entities and flows from ambiguous user requirements?▼

Domain modeling extracts key nouns as entities and verbs as flows from ambiguous user requirements, asking clarifying questions to define vague terms like "sync" and preventing misunderstandings before development begins.

What is gap analysis in domain-driven design and why is it needed?▼

Gap analysis in domain-driven design identifies unstated necessities like error handling and persistence that users forget to mention, ensuring a complete conceptual model and preventing missing components during software architecture planning.

How to perform requirements analysis when the user description is too vague?▼

Requirements analysis transforms vague descriptions into precise domain concepts by identifying system nouns and verbs, then asking targeted questions to clarify specific meanings and define missing functional components for software engineering.

Does concept modeling support the initial genesis workflow of a software project?▼

Concept modeling supports the genesis workflow by providing a clear conceptual model extracted from initial requirements, establishing a structured foundation for further specification and domain-driven design implementation.

What are the limitations of automated domain concept extraction for software architecture?▼

Automated domain concept extraction requires interactive user clarification to define ambiguous terms accurately and cannot independently resolve deep business logic gaps without human input during requirements analysis.

Related Skills

Explore More Software Engineering Skills→
aeonbridgeaeonbridge

langextract

Extract structured data from unstructured text with source grounding.

Official
Advanced
atanakaatanaka

usecase-to-sequence-v1

Generate PlantUML sequence diagrams from use-case specifications and domain models.

Community
Advanced
EnigmaWUEnigmaWU
1

define-bounded-contexts

Define bounded contexts and map integration contracts for domain-driven design.

Community
Advanced
zach-sourcezach-source

osgrep

Search codebases semantically using natural language queries with local embeddings.

Community
Intermediate