What problem does it solve? Teams lose a shared domain vocabulary across features, causing naming drift, duplicated models, and broken downstream verification. This Skill maintains a single project-level context map so every feature inherits the same canonical names and strategic boundaries. ## Core Features & Use Cases - Bounded context modeling: Records DDD strategic bounded contexts with roles (core/supporting/generic) and relationships (upstream/downstream, conformist, ACL). - Ubiquitous language registry: Fixes canonical domain terms per context that seed schema names and are grep-verified on diffs downstream. - Amend-never-fork updates: Extends the existing context-map.md on each new feature instead of creating a second map that would fork the vocabulary. - Open spike tracking: Captures actionable unknowns with closure criteria and owning features, materializable as spike tasks. - Use Case: During the explore movement of a new feature, the analyst invokes this Skill to add a new bounded context and its domain terms to the project's context-map.md without rewriting contexts modeled by earlier features. ## Quick Start Ask the mismagent analyst to update the project context map with the bounded contexts and domain terms discovered for the current feature.
