analyzing-domain-model

Analyze domain models into structured documentation files with source links.

9|Updated Jan 15, 2026

Search Tags:#documentation #validation #domain-driven-design #code-analysis #entities #domain-model

Ready to run

npx skills add https://github.com/cliftonc/unwind --skill analyzing-domain-model

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: analyzing-domain-model
Source: https://github.com/cliftonc/unwind/tree/main/skills/analyzing-domain-model
Command: npx skills add https://github.com/cliftonc/unwind --skill analyzing-domain-model

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes domain models to extract entities, value objects, aggregates, enums, and business rules, translating them into a structured, machine-readable documentation layout for unwind.

Core Features & Use Cases

Generates a complete domain-model documentation package at docs/unwind/layers/domain-model/ including index.md and per-section files (entities.md, value-objects.md, enums.md, validation.md) for scalable codebases.
Supports incremental writes and optional aggregation by domain; for large codebases, split by aggregate to keep docs navigable.
Provides a repeatable workflow to audit and document domain rules, relationships, and state machines from source code.

Quick Start

Run the domain-model analysis to generate docs/unwind/layers/domain-model/ and begin populating index.md and section files.

Frequently Asked Questions about analyzing-domain-model

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

FAQPage Schema

How do I document domain model entities and validation rules from source code?▼

You can document domain model entities and validation rules by analyzing source code to extract structured, machine-readable documentation for entities, value objects, aggregates, and enums mapped directly from the codebase.

What is the best way to generate domain-driven design documentation for a large codebase?▼

For large codebases, generating domain-driven design documentation is handled by splitting output by aggregate to keep docs navigable, producing per-section files like entities.md and validation.md for scalable navigation.

How does domain model analysis handle incremental writes for existing documentation?▼

Domain model analysis supports incremental writes, allowing you to update and populate existing section files like index.md without regenerating the entire documentation package from scratch.

Can I map aggregates and value objects to their source links automatically?▼

Yes, mapping aggregates and value objects to their source links is supported automatically, ensuring the generated documentation includes complete coverage with direct links to the source code.

Do I need any dependencies to run domain model code analysis?▼

No external dependencies are required to run domain model code analysis, as the skill operates independently to audit and document domain rules, relationships, and state machines from source code.