arch-domain-modeler

Define entities, invariants, relationships, and state transitions for a domain model.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/FernanSuoza/AIDD-project-bootstrap --skill arch-domain-modeler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arch-domain-modeler
Source: https://github.com/FernanSuoza/AIDD-project-bootstrap/tree/main/templates/skills/arch-domain-modeler
Command: npx skills add https://github.com/FernanSuoza/AIDD-project-bootstrap --skill arch-domain-modeler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide a clear, testable domain model by defining entities, ownership, invariants, relationships, and state transitions so teams avoid inconsistent terminology, undocumented business rules, and unclear lifecycle behaviour.

Core Features & Use Cases

  • Entity and Ownership Mapping: Identify core entities, value objects, and authoritative owners to prevent undocumented ownership and migration surprises.
  • Invariants and Lifecycle Rules: Capture testable business invariants and state transitions, including forbidden transitions and pre/post conditions.
  • Alignment and Traceability: Align models with API contracts, architecture sections, and requirements to reduce naming drift and ensure implementation fidelity.
  • Use Case: Model approval workflows and capture Draft → Pending → Approved/Rejected transitions with ownership and invariants documented for testing and migration planning.

Quick Start

Run the arch-domain-modeler skill with the project concept or architecture context and any existing API contracts to produce a domain model document listing entities, ownership, invariants, and state transitions.

Frequently Asked Questions about arch-domain-modeler

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

FAQPage Schema
How do I define domain model entities and state transitions for system design?

Defining domain model entities and state transitions involves identifying core entities, value objects, and authoritative owners to prevent undocumented ownership and capture testable business invariants for lifecycle behavior.

What is the best way to document domain model invariants and ownership?

Documenting domain model invariants and ownership requires mapping authoritative owners to core entities and capturing testable business rules to prevent migration surprises and ensure implementation fidelity.

How do I model approval workflow state transitions like Draft to Approved?

Modeling approval workflow state transitions requires capturing Draft to Pending to Approved or Rejected lifecycles while documenting ownership and forbidden transitions to ensure testable pre and post conditions.

How do I align domain models with API contracts and architecture requirements?

Aligning domain models with API contracts and architecture requirements reduces naming drift by ensuring ubiquitous language traceability and implementation fidelity across system design and behavior modeling tasks.

When do I need to capture domain model invariants and lifecycle behavior?

You need to capture domain model invariants and lifecycle behavior when a project requires clear ownership, testable business rules, documented state transitions, and migration-sensitive source-of-truth guidance.

Can I use a domain modeler for migration planning and undocumented business rules?

A domain modeler can be used for migration planning by identifying authoritative owners and capturing undocumented business rules to prevent migration surprises and clarify inconsistent terminology.