arch-domain-modeler

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.