ddd-refiner

# DDD Refiner ## What This Produces - **Output**: `.lattice/standards/ddd-principles.md` (or custom path from `.lattice/config.yaml` → `paths.ddd_principles`) - **Two modes**: - **Overlay** (`mode: overlay`): A slim document containing only sections that differ from the defaults. The domain-driven-design atom reads its embedded defaults first, then applies this document's sections on top. This is the expected common case. - **Override** (`mode: override`): A comprehensive standalone document that fully replaces the atom's embedded defaults. For teams with fundamentally different domain modeling principles. - **Default mode**: Overlay -- produces only what the user wants to change - **Config key**: `paths.ddd_principles` in `.lattice/config.yaml` - **Template**: Read `./assets/template.md` for the full document structure, default content, and interview guidance comments ## Scope Clarification This skill defines the *rules of domain crafting*, not the domain model itself. The domain model evolves through features; this document defines the guardrails. It covers DDD tactical patterns only -- not strategic DDD (no context mapping, no microservice topology, no bounded context integration). ## Before You Begin ### Check for existing documents Before starting the interview, check whether a custom document already exists: 1. Read `.lattice/config.yaml` -- does `paths.ddd_principles` point to a file? 2. If yes, read that file. Ask the user: - "You already have a custom ...