What problem does it solve? Domain terminology drifts and design decisions get forgotten as projects grow, leaving future readers guessing why the code looks the way it does. This Skill keeps a project's domain model explicit by maintaining a canonical glossary (CONTEXT.md) and recording significant decisions as ADRs the moment they crystallize. ## Core Features & Use Cases - Glossary management: Challenges conflicting or fuzzy terminology during discussion and updates CONTEXT.md inline with canonical terms and avoided synonyms. - Architecture Decision Records: Offers to write numbered ADRs in docs/adr/ only when a decision is hard to reverse, surprising without context, and the result of a real trade-off. - Multi-context support: Handles both single-context repos (one root CONTEXT.md) and multi-context repos via a CONTEXT-MAP.md that maps bounded contexts and their relationships. - Use Case: While designing an ordering system, the user says "account" loosely; the Skill asks whether they mean Customer or User, records the resolved term in CONTEXT.md, and drafts an ADR when the team picks event-sourced writes over a CRUD model. ## Quick Start Ask the assistant to help define the domain terms for your project and record the key architectural decisions as ADRs.
