What problem does it solve? Teams lose track of domain terminology and architectural decisions as projects grow, leading to inconsistent naming, forgotten rationale, and misaligned code. This Skill keeps the domain model explicit by maintaining a glossary, CONTEXT.md, and ADRs as decisions are made. ## Core Features & Use Cases - Ubiquitous Language Management: Challenge fuzzy terms against the project glossary and add missing concepts to CONTEXT.md, creating the file lazily when needed. - Architectural Decision Records: Record decisions inline as ADRs with traceable short IDs (D-01, D-02, ...) so they can be linked back to implementing code. - Premortem Stress-Testing: Invoke the dylan-dog skill in Premortem mode to map failure modes against a fixed heuristic checklist instead of improvising edge cases. - Use Case: While designing a Spring Boot feature, use this Skill to align new entity names with the glossary, record the bounded-context decision as an ADR, and tag it D-07 for later traceability. ## Quick Start Use the domain-modeling skill to record this architectural decision and update CONTEXT.md with the new domain terms.
