What problem does it solve? Domain-driven design artifacts often drift: tactical models get reinvented at build time, ubiquitous language diverges from the strategic map, and invariants get lost between exploration and implementation. This Skill persists the tactical model as a per-feature Markdown file so every aggregate, invariant, event, and command is captured once and consumed downstream. ## Core Features & Use Cases - Per-feature tactical model file: Writes <output_dir>/features/<feature>/tactical-model.md with sections per bounded context the feature touches. - Explore-to-model handoff: Persists the analyst's "Seeds for the tactical" section so the tactical-modeler absorbs them from the file rather than from a chat message. - Consumer-driven rows: Every aggregate, invariant (INV-n), domain event, and command names its downstream consumer (manifest block, acceptance criterion, read-model, or application-service), or it is not written. - Use Case: During the mismAgent model phase, the tactical-modeler reads the seeds written during explore, expands them into aggregates with invariants and events per context, and empties the seeds section — producing the input for the building-block manifest. ## Quick Start Ask the agent to write the tactical model for the current feature into features/<feature>/tactical-model.md using the canonical names from context-map.md.
