usecase-to-class-v1

Convert use case outputs and domain models into a UML class diagram.

Updated Feb 19, 2026

Search Tags:#ddd #usecase #code-generation #class-diagram #uml #domain-model

Ready to run

npx skills add https://github.com/atanaka/uml-workflow-v3 --skill usecase-to-class-v1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: usecase-to-class-v1
Source: https://github.com/atanaka/uml-workflow-v3/tree/main/skills/usecase-to-class-v1
Command: npx skills add https://github.com/atanaka/uml-workflow-v3 --skill usecase-to-class-v1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill consolidates use-case outputs, domain models, and business context into a formal UML class diagram that serves as the authoritative source for downstream code generation.

Core Features & Use Cases

Consolidates use cases, inferred domain models, and original scenario information into a single, formal domain model
Produces PlantUML class diagram, Domain Model JSON, Architecture Overview, and XMI model
Supports language inheritance and bilingual output from use-case specifications

Quick Start

Generate the formal UML class diagram from the latest use-case outputs.

Frequently Asked Questions about usecase-to-class-v1

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

FAQPage Schema

How do I convert use cases into a formal UML class diagram for domain-driven design?▼

To convert use cases into a UML class diagram, you consolidate use-case outputs, inferred domain models, and original scenario information into a single authoritative formal domain model. This process generates PlantUML diagrams, Domain Model JSON, and XMI artifacts.

What is the process to consolidate use cases and domain models into a single authoritative class diagram?▼

Consolidating use cases and domain models involves applying a structured workflow that merges original scenario information with inferred domain models. The result is a single authoritative UML class diagram and supporting architecture artifacts for downstream code generation.

Can I generate PlantUML and XMI artifacts directly from my use case specifications?▼

Yes, generating PlantUML and XMI artifacts directly from use case specifications is possible. The conversion process takes use-case outputs and applies language inheritance rules to produce bilingual PlantUML class diagrams, Domain Model JSON, and XMI model outputs.

Do I need a specific JSON file as input to generate a class diagram from use cases?▼

Yes, you need the usecase-to-class-v1_usecase-output.json file as input to generate the class diagram. This specific JSON file provides the necessary use-case outputs and domain model context required to produce the formal UML artifacts.

Does the generated UML class diagram support bilingual output and language inheritance rules?▼

Yes, the generated UML class diagram supports bilingual output and language inheritance rules. It follows language inheritance rules derived from use-case specifications to determine code-facing naming conventions and produce bilingual model artifacts.

What are the limitations of using use case outputs to generate a domain model JSON and UML artifacts?▼

A limitation of generating domain model JSON and UML artifacts from use cases is the strict dependency on the input format. You must provide the exact required usecase-output.json file, and the quality of the consolidated domain model relies entirely on the completeness of the initial scenario information.