What problem does it solve? Teams lose a shared domain vocabulary as features accumulate: each feature invents its own names, schemas drift, and verifiers can no longer grep canonical terms. This Skill maintains a single project-wide context-map.md so bounded contexts, relationships, and ubiquitous language stay canonical across every feature. ## Core Features & Use Cases - Strategic context mapping: Records DDD bounded contexts with role (core/supporting/generic), relationships (upstream/downstream, conformist, ACL), and per-context ubiquitous language. - Amend-never-fork discipline: Reads the existing context map on each new feature and extends it, preventing a second map that would fork canonical names. - Open spike tracking: Captures actionable unknowns as spike entries with closure criteria and owning features, later materialized as spike task nodes. - Use Case: During the mismAgent explore movement, the analyst invokes this writer to add a new bounded context and its domain terms (e.g. TipoIntervento) to the project context map, which downstream manifests, schemas, and verifiers inherit. ## Quick Start Ask the mismagent analyst to update the project context map with the bounded contexts and ubiquitous language identified for the current feature.
