What problem does it solve? Domain terminology drifts and architectural decisions get forgotten, leaving future readers guessing why the code looks the way it does. This Skill captures the project's ubiquitous language in CONTEXT.md and records hard-to-reverse decisions as ADRs the moment they crystallize. ## Core Features & Use Cases - Ubiquitous Language Glossary: Builds and sharpens CONTEXT.md with opinionated term definitions, listing rejected synonyms under Avoid so the team speaks one language. - Architecture Decision Records: Writes minimal ADRs in docs/adr/ with sequential numbering, but only when a decision is hard to reverse, surprising without context, and the result of a real trade-off. - Multi-Context Support: Detects CONTEXT-MAP.md for repos with multiple bounded contexts and routes terms and decisions to the right context. - Use Case: While designing an ordering system, the user says "account" ambiguously; the Skill challenges the term, resolves it to Customer, updates CONTEXT.md inline, and offers an ADR when the team picks event-sourced writes over a CRUD model. ## Quick Start Ask the assistant to pin down the terminology for the current feature and record the decision we just made as an ADR.
