What problem does it solve? Domain-driven design teams lose tactical modeling details between the strategic exploration phase and the build phase, causing aggregates, invariants, and domain events to be reinvented or drift from the canonical language. This Skill persists those decisions in a per-feature tactical-model.md file so downstream manifest generation and verification consume them directly. ## Core Features & Use Cases - Explore-to-model handoff: Persists the "Seeds for the tactical" section that the analyst glimpses during strategic exploration, which the tactical-modeler later absorbs and empties. - Consumer-driven modeling: Records aggregates, invariants (INV-n), domain events, and commands with actors, where every row must name its downstream consumer (manifest block, acceptance criterion, or read-model) or it is not written. - Ubiquitous language enforcement: Requires every term to already exist in the project-level context-map.md, preventing local renaming and language drift. - Use Case: While modeling a maintenance feature, capture the invariant "extraordinary maintenance requires an attachment" as INV-1 so the verifier later demands a test for it on the aggregate block. ## Quick Start Ask the agent to write the tactical model for the current feature, capturing its aggregates, invariants, domain events, and commands into features/<feature>/tactical-model.md.