← ClaudeAtlas

pm-domain-modellisted

Generate a Domain Model - domain boundaries, entity catalogue, relationships, and ERD diagrams. Optional Phase 4 higher-level companion to pm-entity-registry - gives the cross-domain ERD and boundary view above the operational entities.md register. Two-stage output - confirm entity catalogue before generating entity definitions.
ljucask/pureinn-product-development · ★ 1 · AI & Automation · score 77
Install: claude install-skill ljucask/pureinn-product-development
# PM - Domain Model ## Agent mode (`--agent`) Supports `--agent`: runs autonomously in a subagent, drafts the artifact from existing inputs, and returns a short summary + coverage note. - **No flag** → interactive (default); if inputs are heavy, offer agent mode. - **`--agent`** → obey. First check inputs are complete. Anything missing: do NOT invent it - mark `[ASSUMED - what/why]` in the output and summary. Never hallucinate to fill a gap. --- ## What this skill does Defines the conceptual data and domain structure of the product: 1. Business Domains - bounded areas of responsibility 2. Entity Catalogue - all entities with domain ownership 3. Entity Definitions - attributes, relationships, enums, events, ERD diagrams per entity Two-stage output: Claude generates the Domain Overview + Entity Catalogue first, waits for user confirmation, then generates the full Entity Definitions. This prevents building detailed specs on top of a wrong domain structure. Output is the foundation for entities.md (entity state machines), business_rules.md (business behavior), and Feature Cards (delivery). Never duplicate Domain Model content in those documents - reference it. --- ## Reconciled mode (when run by pm-reconcile) If `reconcile/reconciliation_report.md` and the reconciled `entities.md` exist, build the domain model (boundaries, entity catalogue, relationships, ERD) **from the reconciled entities** - do not re-derive from code or old docs. The entity names and structure are